Define Game's State

[AnthonyDampier]

As a Game Designer we need a game that provides an interesting Dungeon Crawling Game by defining the Prototype Game State for this application

[AnthonyDampier]

Game State Structure

1. Player State: Contains all the information related to the player.

   • Position: The player's current location in the dungeon (e.g., x, y coordinates).
   • Health: The player's current health points.
   • Inventory: Items that the player has collected, including weapons, potions, and keys.
   • Stats: Player attributes like strength, agility, and intelligence.

2. Dungeon State: Represents the dungeon layout and the visibility of its parts.

   • Tiles: A 2D array representing the dungeon, where each tile can be a wall, floor, door, etc. Each tile has properties like revealed (boolean), type (wall, floor, etc.), and content (enemy, item).
   • RevealedAreas: A subset of Tiles that the player has discovered. Initially, this might only include the tiles surrounding the player's starting position.

3. Enemy State: Information about the enemies within the dungeon.

   • Positions: The locations of all enemies within the dungeon.
   • Statuses: Each enemy's health, status effects (e.g., poisoned, stunned), and whether they are alert or idle.
   • Behaviors: Defines how enemies behave (e.g., patrolling, chasing the player, attacking) based on the player's actions and their visibility.

4. Game Progress: Tracks the overall progress of the game.

   • Level: The current dungeon level or depth the player has reached.
   • Score: Points accumulated by the player through defeating enemies and discovering treasures.
   • Objectives: Key objectives the player needs to complete to advance or win the game (e.g., defeat a certain enemy, find a specific item).

Handling Progressive Dungeon Revelation

• Visibility Algorithm: Implement an algorithm (e.g., shadow casting for field of view) that determines which tiles become visible to the player as they move through the dungeon. Update Tiles and RevealedAreas accordingly.
• OnMove Event: Each time the player moves, trigger an event that checks the player's new position, updates the visibility of nearby tiles, and checks for encounters with enemies or items.

Managing Enemy Encounters

• Enemy Activation: When a player enters a new area and reveals enemies, update the Statuses of those enemies to make them active or alert.
• Combat System: Define interactions between the player and enemies, such as initiating combat when they occupy adjacent tiles. Include mechanics for attacking, defending, and using items.
• Enemy AI: Implement AI behaviors for enemies based on their state, such as seeking out the player if alerted, wandering within a revealed area, or fleeing if severely injured.

Updating the Game State

The game state is dynamically updated in response to player actions and the unfolding game events:

• Player Actions: Moving, attacking, using items, and other actions modify the player's state and can affect the dungeon and enemy states.
• Game Events: Events like discovering a new area, encountering enemies, or completing objectives update the game progress and potentially the dungeon layout (e.g., unlocking new areas).