How gaurigupta1/dungeon-crawler-game works
This is a text-based dungeon RPG. A player starts the game, explores connected rooms, encounters monsters, fights in turn-based combat, collects and uses equipment or healing items, and advances toward the final-boss victory condition. The runtime is centered on Game, which owns the world and dispatches commands; Room models locations, while Player and Monster specialize the shared Character layer. The README documents capabilities beyond the sampled excerpts; links based only on that documentation are cited to it, and unsampled implementation details are not inferred.
Main entry points: Game.cpp Game controller · Room.cpp Room locations · Player.cpp Player character · Monster.cpp Monster types
Components 8
Game runtime
- Program entry
code/src/main.cpp - Game controller
code/src/Game.cpp
Dungeon world
- Room locations
code/src/Room.cpp
Characters
- Player character
code/src/Player.cpp - Character base
code/src/Character.cpp - Monster types
code/src/Monster.cpp
Items and gear
- Item types
code/src/Item.cpp
Other components
- Player
Connections 14
- Player → Program entry: starts game
README.md - Program entry → Game controller: runs
code/src/main.cpp - Game controller → Room locations: builds world
code/src/Game.cpp - Game controller → Player character: creates player
code/src/Game.cpp - Game controller → Room locations: moves through
code/src/Game.cpp - Game controller → Monster types: starts combat
code/src/Game.cpp - Game controller → Player character: resolves combat
code/src/Game.cpp - Room locations → Monster types: owns monster
- Room locations → Item types: holds items
- Player character → Item types: manages inventory
- Monster types → Item types: drops loot
code/src/Monster.cpp - Player character → Character base: inherits
README.md - Monster types → Character base: inherits
README.md - Game controller → Item types: sets starting gear
code/src/Game.cpp