• 2D shoot 'em up
SDL2 Santa game tutorial 🎅
SDL2 Shooter 3 tutorial
The Legend of Edgar 1.36
SDL2 map editor tutorial [UPDATED]
TBFTSS: The Pandoran War - Amiga OS4 Port
— Simple 2D adventure game —
There are just a few more things we need to add to our game: a title screen, an ending screen, some sound effects, and some music. These things are all quite easy to do, so this final part will be simple.
Extract the archive, run cmake CMakeLists.txt, followed by make, and then use ./adventure14 to run the code. The usual controls apply. Press SPACE to start the game, then return all 4 icons to the Dungeon Mistress. Once done so, head through the door in the main room and up the stairs to see the ending screen. Close the window or press Space, Return, or Escape to finish.
Inspecting the code
We'll start from the beginning, with the title screen. The title screen is defined in title.c. There are a few functions to be found here. We'll go through them one at a time, starting with initTitle:
Our game logo is in two pieces, to allow it to fit onto the 512x512 texture atlas; we could've increased the size of the atlas itself, but this solution is just fine. We grab both pieces of the logo, then setup a few other variables, and set our logic and draw delegates. We'll see what all these variables do as we come to the logic and draw steps, starting with logic:
We're first testing if the gotoDungeon variable is 0. If so, we want to increase the value of logoAlpha. This value will be used to fade in our logo. We're limiting it to 255; if we go above this value, we'll get some odd graphical effects, such as the logo fading back in again. We're also increasing the value of tickVal by the delta time (more on this in a bit). We then also check if the Space key has been pressed. If so, we set the gotoDungeon variable to 1.
If gotoDungeon is already 1 (true) when we enter this function, we'll start to decrease our gotoDungeonTimer. The reason that we're doing this at all is because when the player presses Space, we don't want to instantly go into the dungeon. It's a bit jarring, so we if simply clear the screen for a short period (half a second, since we're using FPS / 2), we'll offer a small transition. We then call initDungeon to begin the game proper. This was once done in main.c.
Turning to the draw function, we can see it's again rather simple:
We're testing first if we're not going to the dungeon before drawing anything. This will keep our screen blank if we are. Otherwise, we'll draw the title as normal. We're using drawRect to set the background to a dull grey, then calling drawLogo to draw our logo. We're then assigning the value of c, depending on the value of tickVal, by applying the modulo of FPS and seeing if it's less than FPS / 2. Basically, we're reducing tickVal to the range of 0-59, and then checking if it's less than 30. If it is, we're setting c to 255, otherwise 192. This is then used in our "Press Space!" draw text command. In effect, the Draw Space text will flash white and grey every half a second. The copyright display follows this.
The last function we'll look at is drawLogo:
We want to center our logo. Because it's in two parts, we need to add the widths of both parts together before we work out the value of x. After that, we set the alpha value of the logo to the value of logoAlpha. We then draw both logo1 and logo2 at the calculated x position, logo2's horizontal position being the value of x, plus the width of logo1, to set it alongside. Finally, we reset the logo's texture's alpha to 255. Because this is basically the texture atlas, we need to ensure it doesn't remain dim when we start the game; the alpha is only relevant for this function.
That's our title sequence handled. Now we can look at the ending. It's a little more complicated, and lives in ending.c. There are several functions that detail in this file, starting with initEnding:
To begin with, we're checking to see if the player exited the dungeon with the Eyeball and Red Potion. To do this, we call hasInventoryItem; just having found the items isn't enough, we want them to have been brought out with the player. Next, we calculate how long it took the player to complete the dungeon. For the minutes (mins), we're taking the dungeon time value and dividing it by FPS * FPS (so, 60 * 60, which would be the number of frames per minute). For the seconds (secs), we're dividing the dungeon time by the frames per second, then reducing it to the range of FPS, to give it a value of between 0 and 59. We're then setting up a variable called displayTimer, to a value of FPS / 2. Just like our title screen, we want a small transition when the ending starts. Finally, we're setting up the logic and draw function pointers.
We'll look at our logic step next. It's quite simple:
We're decreasing the value of displayTimer, limiting it to 0. If the value is 0, we'll test if Space, Return, or Escape has been pressed, and then exit the game. We want to make sure the ending text has been shown before allowing the player to exit, so that they don't press the keys too soon.
Our draw function is somewhat similar:
We want to make sure that displayTimer is 0 before drawing anything, leaving the screen blank for that half a second if not. Our drawCongratulations function coms next. It's pretty simple:
We're just drawing the congratulations text, centered in the screen. Nothing special. Our drawStats function is a bit more complicated:
We want to draw the various stats: the gold we found, the silver, whether we got the eyeball and potion, and the time we took. For the gold and silver, we want to draw the amount that was found and the total amount that was in the dungeon (we'll detail this in a bit). For the eyeball and red potion, we want to know the value of hasEyeball and hasRedPotion, as determined in initEnding.
We want to draw the text in green or red, depending on whether we found all of the item in question. We do this by calling a function called setStatColour, and passing over the actual and expected values, along with a reference to an SDL_Color object. With the colour determined, we then draw the appropriate text - the number found against the number available for gold and silver, and Yes or No for the eyeball and red potion. Our time stat is simply the minutes and seconds, always displayed in white.
Note that we're aligning the text around the middle of the screen, but aligning the left-hand side to the right, and the right-hand side to the left.
Our setStatColour function is quite straightforward:
Taking the actual, expected, and SDL_Color arguments, we merely check to see if the actual and expected values match. If so, we set the value of SDL_Color to be green. Otherwise, we set it to be red.
Before moving on, we'll quickly detail the tweaks we've made to the Dungeon and Prisoner structs, in structs.h:
Dungeon now holds numGold and numSilver variables (as well as complete and time, to handle the state and play time). numGold and numSilver are determined in gold.c and silver.c. For eample, in silver.c:
Whenever, we add silver coin, we'll increment Dungeon's numSilver by 1. For gold, we do a similar thing, but using the value of the gold.
We've also added a new variable to Prisoner - silverFound:
This is important for the ending stats, as we can't use the silver variable. Since we give the silver coins to the Blacksmith, our value decreases. It would therefore be impossible for us to find all the silver, since our silver value would always be less than the total in the dungeon. As such, when we collect a silver coin, we increment both the silver and silverFound variables, and test the silverFound variable at the end.
Something we also added in this final part is a set of stairs, that act as the exit point for the dungeon. They are defined in stairs.c. Our initStairs function merely grabs the appropriate texture and sets the touch function:
The touch function itself simply tests to see if the player is the thing that touched the stairs, and sets the dungeon's complete flag to 1 (true) if so:
With that in place, we needed to only update the logic function in dungeon.c:
If the dungeon's complete flag is 1 (true), then we call initEnding, to finish the game. Otherwise, the main game will proceed as normal.
Before wrapping up, we'll look at how we're using sound and music. Loading sound and music was covered in the Shooter tutorial, so we'll only talk about it briefly here. For example, we've updated the movePlayer function in player.c to play a sound (playSound) when the Prisoner moves:
Notice how we're only calling playSound if the dx and dy are not both 0. This is to ensure that the sound only plays if the Prison actually moves. At the start of the game, we center the camera over the prisoner by calling movePlayer and passing in 0, 0. In this case, we don't want a sound to play.
Another place we play sounds is when we pick up an item. In item.c, we've added a playSound to the touch function:
There are many other instances of where we play sounds, but again we won't cover them all here. For loading our sound and music, we've updated our initGameSystem function in init.c:
initSound, loadMusic, and playMusic are all defined in sound.c. initSound will load all the sounds we want to use, while loadMusic will load the music. We play the music by calling loadMusic, passing in 1 to tell the music track to loop forever.
The very last thing we want to do is show the title screen when the game starts. We'll do so in main, in main.c:
Here, instead of calling initDungeon, we've replaced it with a call to initTitle. So, when the game starts, we'll load our sound and music, and show the title screen.
And there you have it - a simple dungeon adventure game, featuring a load of quirky characters and some hidden items to find! It's not a long game, just 10 minutes to finish if you know what you're doing. But what we've done here is created a basis for making a much larger game, supporting multiple dungeons and things to do. There are a few things we'd want to do better in such a case, like putting in place a scripting system for our NPCs, so that their interactions with the player aren't hardcoded. For this game, however, it'll do.
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: