How sulkasormi/frogcomposband works
FrogComposband is a single-player roguelike game: a player starts the program, creates or loads a character, explores procedurally generated dungeons, and interacts through terminal or graphical front ends. The source tree shows distinct gameplay areas for commands and combat, magic, monsters, items, and dungeon generation, alongside persistence and shared game state. The excerpts and README establish the product and some module responsibilities, but do not expose the full gameplay loop; unverified runtime connections are therefore dashed and uncited.
Main entry points: cmd1.c Player commands · main.c Game entry · dungeon.c Dungeon generation · object2.c Object system
Components 20
Entry and display
- Game entry
src/main.c - Terminal UI
src/z-term.c - Platform drivers
src/main-sdl.c
World and combat
- Player commands
src/cmd1.c - Dungeon generation
src/dungeon.c - Room generation
src/rooms.c - Melee combat
src/melee2.c - Monster spells
src/monspell.c - Game effects
src/gf.c
Character systems
- Character creation
src/py_birth.c - Classes and races
src/classes.c - Spell systems
src/do-spell.c - Equipment
src/equip.c - Object system
src/object2.c
Shared services
- Save and load
src/save.c - Game state definitions
src/defines.h - Inventory API
src/inv.h - Document API
src/z-doc.h - Generation API
src/generate.h
Other components
- Player
Connections 20
- Player → Game entry: starts game
- Game entry → Platform drivers: selects driver
src/main.c - Player → Character creation: creates character
- Game entry → Character creation: starts session
- Character creation → Classes and races: chooses options
- Player commands → Dungeon generation: explores
- Dungeon generation → Room generation: builds rooms
- Dungeon generation → Generation API: uses API
src/dungeon.c - Player commands → Melee combat: attacks
- Melee combat → Monster spells: fights
- Player commands → Spell systems: casts spells
- Spell systems → Game effects: applies effects
- Player commands → Object system: uses items
- Object system → Inventory API: uses inventory
- Object system → Equipment: equips items
- Game entry → Terminal UI: displays game
- Player commands → Terminal UI: renders prompts
- Game entry → Save and load: loads or saves
- Player commands → Game state definitions: updates state
- Player commands → Document API: renders help