• 2D shoot 'em up
SDL2 turn-based strategy tutorial
Water Closet ported to PlayStation Vita
The Legend of Edgar 1.35
SDL2 Rogue tutorial
— A simple turn-based strategy game —
Now that we have control over multiple unit, it's time to update our movement logic a bit. Right now, our units can move an unlimited range. It would be better if we restricted how far they can each move. In this part, we'll configure the movement range of each wizard separately, as well as display on screen the squares that the mage can move into.
Extract the archive, run cmake CMakeLists.txt, followed by make, and then use ./sdl2TBS03 to run the code. You will see a window open like the one above, showing three wizards in a small room, surrounded by walls. Clicking on a wizard more than once will toggle displaying the movement area. Tiles that can be moved into will be displayed in blue, while the other map squares will be dark. Click on a blue square to move into it. Notice that clicking on a dark square results in no movement. Select the wizards as per the previous tutorial. When you're finished, close the window to exit.
Inspecting the code
Displaying the movement limit for our wizards is very useful to the player, rather than having them attempt to guess how far they can move. There are quite a number of changes and updates requires to support this, so let's jump right in.
Starting with defs.h:
We've added an enum to handle displaying the movement range. SHOW_RANGE_NONE will mean don't display the movement range. SHOW_RANGE_MOVE will be used to instruct the game to display the movement range. SHOW_RANGE_MAX is used to assist with state looping, as we'll see later. Also, the reason we're using an enum here, rather than a simple flag is because in a later part we'll want to display the attack range, too.
Moving on to structs.h, we've made some tweaks and additions:
The Entity struct now has a `data` field, as per past tutorials. This is to support extended data, such as the Unit struct:
The Unit struct is new and will hold all the data about the unit. Right now, it has just one field: moveRange. Later, it can be expanded to hold data such as hit points, action points, etc.
The MapTile struct has also been tweaked:
In addition to `tile`, we now have a field called inMoveRange. This is a flag that will state whether this MapTile falls within a unit's movement range.
Finally, we updated Stage:
Stage now includes a showRange field, that will make use of the SHOW_RANGE enums from defs. We'll see this in use in a little while.
Now, let's move over to units.c, where we've made several updates. Starting with initUnit:
We're now mallocing a Unit struct, memsetting it to zero all the data, and then assigning it to the entity's (`e`) `data` field. We're then returning the Unit, so that it can be tweaked further.
Next, we have a new function called updateUnitRanges:
This function is very important to our movement range calculations and display. It will be called whenever we need to update the movement (and later, attack) ranges for the currently active entity. We start by extracting the Unit data from Stage's currentEntity, and then use two for-loops to reset all MapTiles' inMoveRange to 0. In effect, we'll be marking all the squares on our map as inaccessible. With that done, we're then calling testMoveRange, passing over the current entity's `x` and `y` fields, as well as the unit's moveRange. This is where we'll calculate movement range for the current unit.
testMoveRange itself follows:
What this function is doing is using a queue to test all the squares that can fall into the unit's movement range. It is important to note that we're not using for-loops here to simply mark the squares in a radius as being reachable, asecause they might not be. There could be walls in the way, and other objects such as solid entities could block routes. Therefore, we test one square at a time, adding its neighbours to the queue if it itself is accessible.
The function takes three parameters: `x`, `y`, and `range`. `x` and `y` are the starting position, while `range` is the maximum distance from that starting position we can move. We first prepare a linked list of Nodes (the same struct used in our A*) controlled by moveRangeHead and moveRangeTail. Next, we call addMoveRangeNode, passing through our `x` and `y` (twice, since this is the starting position), and our `range`. We'll explore addMoveRangeNode fully in a bit. For now, know that it will add to our linked list if a series of conditions are right.
We then start a while-loop, that will repeat until the linked list is empty (moveRangeHead's next is NULL). We grab the next Node in our linked list (assigning to `n`) and setup two for-loops, to add all the surrounding squares to our node queue, by calling addMoveRangeNode. Finally, we remove the current node from our queue.
So, quite simple: it's just a queue that will keep processing nodes and adding new ones until it is empty.
Now, let's look at addMoveRangeNode, where we are actually adding nodes to our queue:
The function takes five arguments: `x` and `y`, the current node we're interested in. `ex` and `ey` represent the entity's starting position, while `range` is the maximum distance that a Node be.
In this function, we test to see if the position is valid to move into. To be a valid move point and a candidate for adding to our queue, the position must be inside our map, must not already be flagged as being inMoveRange, its distance from our starting location (`ex` and `ey`) must be less than or equal to `range`, and the location itself must not be otherwise blocked. With that determined, we set the relevant MapTile's inMoveRange to 1. We then malloc and memset a Node, add it to our queue, and set its `x` and `y` variables as the values of `x` and `y` that we passed into the function.
That's it! We can now determine the movement range of our unit. We can now look at how we integrate this system into the rest of our game.
First, let's turn to map.c, where we've updated drawMap:
As we can now determine the movement range, we are going to overlay this on our map tiles. After drawing the map tile, we're testing if Stage's `animation` flag is not set, and also whether we're displaying the movement range (Stage's showRange is not SHOW_RANGE_NONE). If so, we're then testing if the MapTile we're interested in has the inMoveRange flag set, and are calling blitAtlasImage, passing over an AtlasImage called moveTile. Otherwise, we're calling blitAtlasImage and passing over darkTile, causing the rest of the map to be dimmed.
Finally, let's look at loadTiles:
Now, as well as loading the regular map tiles and the routeTile, we're also loading in our darkTile and moveTile.
That's it for the updates to our map. We now head over to player.c, where we've tweaked doSelectUnit:
Before, when evaluating the entity had been clicked on, we would swap to a new one if it wasn't NULL. Now, we are checking to see if the entity clicked on is the same as the current one. If so, we're incrementing Stage's showRange, and wrapping the value around if it is equal to or greater than SHOW_RANGE_MAX. In effect, this means that if we click on the same unit multiple times, we will cycle between displaying the movement range and showing just the map itself. If the entity is a different one, we will now swap to it, and call updateUnitRanges. This is important, as we want the allowed movement map tiles to be based on the unit we have now selected. Otherwise, we would retain the data from the previous unit.
doMoveUnit has also been updated:
Previously, we would make a call to createAStarRoute regardless of where on the map the player clicked. Now, we're extracting the MapTile pointed to by Stage's selectedTile (assigned to a variable called `t`) and testing to see whether the inMoveRange flag is set. This means that the player units will now only move if the destination is within their move range.
addPlayerUnits has also seen a minor update:
At the end of the function, we're calling updateUnitRanges. This is to ensure the ranges are set for the very first unit, when the game begins. If we didn't do this, the player would need to change units before they could control any of the mages.
We're almost done! We need just update mages.c, and stage.c. Let's look at mages.c first, starting with a tweak to initMage:
As part of this function, we're now calling initUnit, passing over the entity (`e`) for which it is being created. We're then returning the created unit, so that it can be further modified by the calling function (without the need to extract it from the entity's `data` field).
We can see this in action in initAndyMage:
We're now assigning the result of initMage to a variable called `u`. We're then setting the unit's moveRange as 10. We have also updated initDannyMage with the same:
Danny, however, had a moveRange of 9, so he can't move quite as far. Finally, initIzzyMage has been adjusted:
Izzy has a move range of 12, as she's a bit more nimble on her feet, compared to the boys.
That's it for mages.c. The last thing we need to update is the `logic` function in stage.c:
We've added in a new variable called wasAnimating, and assigning it the current value of Stage's animating flag. At the end of the function, we're testing to see if at the start of the function we were animating but are now not. In other words, our animation state has changed. If we're done animating, we're calling updateUnitRanges, as the currently active unit has finished moving or attack or taking another action, and so we can update our ranges once again. Since we know that actions result in various animation playing our, doing this check here allows us to centralize the logic.
Part 3 is done! We can now swap between our units, and have a system in place where we can limit how far they can move.
What needs to come next is action point handling, so we can limit how many actions a unit may take per turn. This will also incorporate some simple turn handling (as expected, since this is a turn-based strategy game, after all!).
The source code for all parts of this tutorial (including assets) is available for purchase:
It is also available as part of the SDL2 tutorial bundle:
If you do not wish to create an itch.io account, you can also purchase the tutorial bundle using PayPal, and then download the tutorials directly from the main tutorials page.