Cave Explorer is Brian Xiao's implementation of Adriel Luo's Design Document for game1 in 15-466-f17.
The only asset is used is an atlas/spritesheet courtesy of Kenney.nl.
Because I only use 10 sprites from the spritesheet, and each sprite is 16x16 and lined up, I hardcode the uv-coordinates for each sprite. The SpriteInfo objects are loaded before the game loop is entered.
I implemented the map as a 2D-array of tile types. Unfortunately, these are hard-coded as I felt randomly generating a map would be too difficult. I also have a corresponding 'lit' 2D-array that determines whether or not the tile has been stepped on and therefore lit. Otherwise, these tiles are rendered as a "dirt wall" tile.
There are a number of states that the minecart (player) can take. These are horizontal stationary; moving left; moving right; vertical stationary; moving up; moving down; and all of those but with gold.
Input takes in only left, right, up, down, and space and only does anything in stationary states. Space will check for gold surrounding the player and attempt to 'mine' the gold. If the gold is actually gold, then the player wins; otherwise, the gold bars turn into logs. (This is done by probability: 1/#-of-gold-left)
The game state is checked each iteration to see if the player should still be moving on a track or if the player should stop. When the player is stopped, it will check if gold is in the surrounding blocks, and if so, reveal it.
If I were doing it again, I would make the game more difficult and add randomization as well as different mechanics.
The design document was clear on mostly everything except the map/grid layout. I had to make some amenities and stretch things out (making walls actual tiles so the map was 2x as big as in the design document).
This game is based on Base1, starter code for game1 in the 15-466-f17 course. It was developed by Jim McCann, and is released into the public domain.
- modern C++ compiler
- glm
- libSDL2
- libpng
On Linux or OSX these requirements should be available from your package manager without too much hassle.
This code has been set up to be built with FT jam.
For more information on Jam, see the Jam Documentation page at Perforce, which includes both reference documentation and a getting started guide.
On unixish OSs, Jam is available from your package manager:
brew install ftjam #on OSX
apt get ftjam #on Debian-ish Linux
On Windows, you can get a binary from sourceforge,
and put it somewhere in your %PATH%.
(Possibly: also set the JAM_TOOLSET variable to VISUALC.)
Open a terminal (on windows, a Visual Studio Command Prompt), change to this directory, and type:
jam
Depending on your OSX, clone kit-libs-linux, kit-libs-osx, or kit-libs-win as a subdirectory of the current directory.
The Jamfile sets up library and header search paths such that local libraries will be preferred over system libraries.