How ameerarsala/ethereal-tempest works
Main Components
a. Core Game Engine Layer:
• JMonkeyEngine integration (indicated by .j3md files and MatDefs)
• Core game states and FSM (src/etherealtempest/fsm)
• Main game context (GameContext.java)
b. Battle System:
• Combat engine (src/battle)
• Animation system (src/battle/animation)
• Battle environment (src/battle/environment)
• Participant management (src/battle/participant)
c. System:
• Layout management (src/maps/layout)
• Tile system (src/maps/layout/tile)
• Unit movement (src/maps/layout/tile/move)
• Flow control (src/maps/flow)
d. Character/Entity System:
• Character management (src/etherealtempest/characters)
• Unit system (src/fundamental/unit)
• Job class system (src/fundamental/jobclass)
• Skills and abilities (src/fundamental/skill, src/fundamental/ability)
e. Asset Management:
• Effects system (assets/Effects)
• Sprite management (assets/Sprites)
• Material system (assets/MatDefs)
• Shader system (assets/Shaders)
[User Interface Layer]
• GUI Components (src/etherealtempest/gui)
• Menus (src/general/ui/menu)
• HUD Elements
[Game Logic Layer]
• Game States
• Battle System
• Map System
• Character System
[Core Systems Layer]
• Asset Management
• Physics/Math (src/general/math)
• Input Handling (src/general/tools/input)
• Animation System
[Engine Layer]
• JMonkeyEngine Integration
• Rendering Pipeline
• Shader Management
Important Relationships
• How the map system interfaces with both the battle system and movement mechanics
• Relationship between assets and their corresponding managers
• Demonstrate how the FSM controls game state transitions
Technical Details
• Interfaces and abstract classes
• Major data structures and their relationships
• Where configuration files are loaded and processed
• Important managers and controllers