Project: Maze Runner
We want you to practice composing multiple classes and files into one larger, functional piece
of software. For that, we ask you to implement a small game in Java.
Game Idea
The core idea of the game is navigating a character through a maze, overcoming various
challenges to reach the exit. The maze contains multiple different elements like traps, enemies,
and keys that the player must interact with or evade to escape. The game unfolds in a maze
enclosed by walls on all sides, featuring an entry point where the player starts and an exit to
reach for completing the game. Within the maze, the player will encounter an intricate
network of interior walls that create not only a challenging path but also various dead-ends.
Randomly scattered throughout the maze are traps and enemies that the player must avoid
or overcome, as well as keys that must be collected to unlock the exit.
Game Logic
Your game must implement the following mechanics:
Walls and Paths
The game world is designed as a maze, consisting of traversable paths and walls. Each maze
has exactly one entrance and at least one, potentially multiple exits. The exit points are
exclusively situated on the outer border of the maze, which is otherwise completely enclosed
by walls without any gaps. The entrance can be anywhere in or on the border of the maze.
When playing the game, it's crucial that the entrance and exit are clearly distinguishable from
walls and each other. The entrance should be uniquely identifiable, as should the exit, but in
a distinct manner.
In this context, 'paths' refer to the free space within the maze. The density of the maze can
vary significantly, ranging from sparse layouts with abundant open space and fewer walls, to
dense configurations characterized by numerous walls and limited walkable paths.
Character
The main character must be able to move through the maze in four directions (up, down, left,
right). Generally, the character can only walk in free spaces; they cannot walk through walls.
The character must have a number of lives. If the character loses all their lives before reaching
and opening the exit (see below), it's game over.
Obstacles
The maze contains at least two kinds of obstacles. Essentially, an obstacle is an additional
object on an otherwise free path within the maze that causes the character to lose a life when
contact occurs. Like the character, obstacles can only exist within free paths and cannot pass
through walls.
The two required kinds of obstacles are:
Traps: Obstacles with a fixed position within the maze.
Enemies: Obstacles that are dynamic. This means their position within the maze changes
regularly in short intervals. For minimal requirements, they must move randomly throughout
the maze but never leave it; however, for bonus points, they can exhibit more intelligent
behavior (see below).
Keys
The ultimate goal for the main character is to exit the maze. However, to open the exit, they
must have collected a key. There will be at least one, but potentially multiple keys in each
maze. The character must collect at least one key to use the exit of the maze. Attempting to
exit without the key should result in the path being blocked (think: the exit behaves like a wall
until you have a key).
HUD
The game must have at least a small, basic HUD that is visible to the player at all times while
navigating the maze. It must at least display the following information:
- Amount of lives remaining
- Whether a key has been collected
Game Menu
There must be a game menu displayed at the launch of the game and any time a player
presses the Esc key during gameplay. If a player presses Esc to access the menu, the game
itself must be paused (i.e., the main characters and all enemies stop moving). In this menu,
players must at least be able to:
- continue the game (if coming from Esc)
- load a new map file and start a new game
- exit the game
ALL UI and MENUS must be libGDX based. No JavaFX or something.
Victory and Game Over
If the player can leave the maze without losing all lives, they achieve a victory. In this case,
display that the user has won, and stop the gameplay.
If the player loses all lives, the game is over. In this case, display that the game is over, and
stop the gameplay.
In both cases, allow to go back to the main menu.
Technical Requirements
Maze files
You should not generate or define a maze yourself within your program code. Instead, your
program must be able to run any arbitrary maze stored in a Java properties file. If the player
chooses the "load map" option in your game menu, your program must open a File Chooser
and allow them to select the file. Then, your program should read the file and start the game
based on the maze defined in this file.
Properties files are a very simple way to store data in files in Java. Essentially, they just store
key-value pairs of Strings; think of it as a Map