Responsible for finding a valid path between two tile locations on the level, while avoiding invalid tiles.

Requirements:

Tile Locations: The AI Pathfinding feature must be given two tile locations on the level.

Invalid Tiles: The AI Pathfinding feature must be given a list of invalid tiles that should be avoided.

Pathfinding Algorithm: The AI Pathfinding feature must use a pathfinding algorithm to find a valid path between the two tile locations.

Valid Path: The AI Pathfinding feature must return a valid path that avoids invalid tiles.

This system is responsible for rendering the generated level by placing defined tiles from the LevelGenerator class. It should take predefined tile prefabs and build the dungeon using the grid of Tile classes.

Requirements:

• Place Tile Prefabs to match the defined grid from Level Generation

Make sure we attribute FMOD somewhere in the game per their attribution guidlines.
Additionally we need to update the readme with setup guidlines on FMOD to build the game.

https://www.fmod.com/attribution

Responsible for allowing players to draw cards from a pile that contain information about monsters or changes to the dungeon. The Card System should have methods exposed that allow players to Draw, Shuffle and burn cards from the pile.

Requirements:

Card Pile: The Card System must have a pile of cards that can be drawn from.

Draw Method: The Card System must have a Draw method that allows players to draw a card from the pile.

Shuffle Method: The Card System must have a Shuffle method that allows players to shuffle the pile of cards.

Burn Method: The Card System must have a Burn method that allows players to burn a card from the pile.

Card Information: Each card drawn from the pile must contain information about a monster or change to the dungeon.

Interface to start a new game, load a saved game, view game options and exit the game.

Requirements:

New Game: The Main Menu UI must have a button that allows players to start a new game.

Load Game: The Main Menu UI must have a button that allows players to load a saved game.

Game Options: The Main Menu UI must have a button that allows players to view and change game options such as sound and graphics settings.

Exit Game: The Main Menu UI must have a button that allows players to exit the game.

User Interface: The Main Menu UI must have an intuitive and easy-to-use interface that is accessible to all players.

This is to upgrade the spawning system to be able to have different spawning schemes such as grid allocation and entity targeted spawning.

Requirements:

• Heros should spawn from a 'door' entity placed on a wall in the level.
• Monsters should spawn randomly within the grids allocated in the level array.
• Level Generation should be updated to have a decoration tile layer and an improvated decoration spawning algorithm.

This system needs to handle highlighting of tiles as mouse is hovered over as well as triggering placement/instancing of monsters & traps.

Requirements:

• Highlight current tile under mouse cursor
• Drag and drop behaviour for placeable entities
• Needs to update a map class that handles current board state

Level generation feature is a critical component of the dungeon game. It is responsible for creating new levels based on a seed value that is generated randomly. The levels are based around tile maps, which are used to create the layout of the level.

Requirements:

Random Seed Generation: The level generation feature must be able to generate the level from random seed values that can be used to create new levels.

Tile Map Creation: The level generation feature must be able to assemble the level through a combination of tilemaps.

Variety: The level generation feature must be able to create levels that are varied and interesting, with different layouts, and items.

Scalability: The level generation feature must be scalable, so that it can generate levels of different sizes and complexities.

Performance: The level generation feature must be performant, so that it can generate levels quickly and efficiently.

Responsible for handling all aspects of the gameplay loop and scoring. The system should handle events such as the turn completed and keep track of stats such as heroes defeated, days survived etc.

Requirements:

Gameplay Loop: The Scoring/Gameplay System must handle all aspects of the gameplay loop, including turn-based events.

Scoring: The Scoring/Gameplay System must keep track of stats such as heroes defeated, days survived etc.

Events: The Scoring/Gameplay System must handle events such as the turn completed and other in-game events.

Make sure your credits are in the readme! This will need some better details about the game and how to setup and play.

This class will need to handle level generation based upon the GameManager class.

Requirements:
- New class to handle level generation
- Have method for showing 2d map as well as placing objects
- Trigger new generation upon new day if requested by GameManager

Responsible for handling all on-board entities, including heroes and monsters. The system should have stats such as health and strength, as well as methods to handle interacting with each other such as attacking.

Requirements:

Entity Creation: The Hero/Monster Entity System must be able to create entities such as heroes and monsters.

Stats: The Hero/Monster Entity System must have stats such as health and strength that can be used to determine the outcome of battles.

Attacking: The Hero/Monster Entity System must have methods to handle attacking between entities.

Movement: The Hero/Monster Entity System must have methods to handle movement of entities around the board.

AI: The Hero/Monster Entity System will be able to call to another AI-Pathfinding system to determine route across the board to goal. (These will be just boilerplate methods, essentially will ask for a square to move to and aniother system will plot the path through the tiles?)