How empi-empi/python-game works
Daemon Monsters is a Pygame creature-collecting RPG. The player explores tiled maps, interacts with characters, encounters wild monsters or challenges trainers, fights turn-based battles, reviews the party, and can trigger evolutions. The sampled Game class is the runtime coordinator; entity movement, battle logic, rendering sprites, and shared game data provide supporting layers. README content is absent, and excerpts are partial, so links for unsampled subsystems are limited to what the tree and visible code support.
Main entry points: main.py Game coordinator · battle.py Turn-based battle · support.py Asset import helpers · monster_index.py Monster index
Components 17
Game runtime
- Game coordinator
code/main.py - Asset import helpers
code/support.py - Game settings
code/settings.py
World exploration
- Player and characters
code/entities.py - Tiled maps
data/maps - World and battle sprites
code/sprites.py - Sprite groups
code/groups.py - Dialog system
code/dialog.py
Monster systems
- Turn-based battle
code/battle.py - Monster model
code/monster.py - Monster index
code/monster_index.py - Evolution sequence
code/evolution.py - Game definitions
code/game_data.py
Game resources
- Visual assets
graphics - Sound assets
audio - Map tilesets
data/tilesets
Other components
- Player
Connections 21
- Player → Game coordinator: provides input
- Game coordinator → Asset import helpers: loads assets
- Asset import helpers → Visual assets: imports images
- Asset import helpers → Sound assets: imports sounds
- Game coordinator → Tiled maps: loads maps
- Tiled maps → Map tilesets: references tiles
- Game coordinator → Player and characters: creates actors
- Game coordinator → World and battle sprites: creates sprites
- Game coordinator → Sprite groups: updates and draws
- Player and characters → Game coordinator: requests dialog
- Game coordinator → Dialog system: creates dialog
- Game coordinator → Turn-based battle: starts battle
- Turn-based battle → Game coordinator: ends battle
- Game coordinator → Monster index: opens index
- Game coordinator → Evolution sequence: starts evolution
- Turn-based battle → Monster model: updates combat state
- Monster index → Monster model: reads party
- Monster model → Game definitions: uses species data
- Turn-based battle → Game definitions: uses attack data
- Monster index → Game definitions: reads species data
- Game coordinator → Game settings: uses configuration