How psalant726/pac-go works
• Configuration → Game Engine (game settings)
• Input/Output → Game Engine (player commands)
• Game Engine → Input/Output (render updates)
• Game Engine ↔ Game Entities (state updates)
• Initialization flow
• Event handling paths
Important Details
• Player lives
• Pill duration
• Frame rate
• Scoring system
• config.json/config_noemoji.json
• maze01.txt
Technical Specifications
• Go source files (ghost.go, player.go, maze.go, etc.)
• Configuration files (JSON)
• Resource files (maze definitions)
• User input/output channels
Architecture Notes
Annotations showing:
• Terminal-based UI architecture
• Game state management
• Entity interaction system
• Collision detection system
• Score tracking mechanism
• The event-driven nature of the game
• The separation between game logic and rendering
• The configuration system's flexibility
• The entity management system
• The maze rendering and collision detection systems
Keep the abstraction level focused on the main architectural components while showing enough detail to understand the game's operation. Use a clean, organized layout with clear separation between different subsystems.