How david-vanderhaar/rogue_engine works
Main System Components
a) Core Engine Layer:
• Game Engine (Central coordinator)
• Entity System
• Action System
• System
• Input/Keymap System
b) Game Content Layer:
• Modes (Different game variations)
• Screens (UI states)
• Characters
• Items
• Status Effects
c) Resource Layer:
• Assets (sounds, fonts)
• Maps
• Constants
Component Relationships
a) Core Flow:
User Input → Keymap → Actions → Engine → Display
b) Entity Composition:
Entity Base
• Behaviors (AI)
• Actions
• Components (Acting, Attacking, etc.)
c) Game State Management:
Game
• Engine
• Current Mode
• Active Screen
• Entity Manager
Specific Implementation Details
Specialized components:
a) Mode System:
• Hidden Leaf
• Jacinto
• Tall Grass
• Development
b) Screen Flow:
Title → Character Select → Level → Win/Lose
Key Architectural Patterns to Highlight
a) Component-Based Entity System:
• How entities are composed of multiple behaviors
• Demonstrate inheritance and composition patterns
b) Action System:
• Action hierarchy
• Relationship between KeyActions and base Actions
c) Resource Management:
• Asset loading and management
• Sound system integration
Technical Details
• React.js integration points
• Konva.js rendering system
• File structure organization
• State management flow
Top Level:
[User Interface Layer]
• ↕
[Game Logic Layer]
• ↕
[Engine Core Layer]
• ↕
[Resource Management Layer]
• The modular nature of the engine
• Clear separation of concerns
• Component-based architecture
• Game state flow
• Resource management
Implementation Notes
• Use different line styles for different types of relationships
• Notes for key architectural decisions
• Scaling considerations