How zlaper/onedayrpg works
Main Components (Top Level)
a. Core Game Systems (Blue Rectangle)
• MainControl (Central Controller)
• SaveDataManager (Data Persistence)
• SoundControl (Audio Management)
b. Game Logic Layer (Green Rectangle)
• Battle System
• Hero Management
• Entity Generation
• Progress System
c. UI Layer (Orange Rectangle)
• Screen Management
• Hero Selection UI
• Battle UI
• Result Screen
Detailed Component Breakdown
a. Battle System (Purple Sub-section)
• BattleFlow
• BattlePhases
• Start Phase
• Hero Phase
• Enemy Phase
• End Check Phase
• BattleField
• Heroes (3 slots)
• Enemy (1 slot)
b. Entity System (Green Sub-section)
• Entity Framework
• Base Entity
• Hero Entity
• Enemy Entity
• Entity Generator
c. Data Management (Yellow Sub-section)
• SaveDataManager
• Hero Collection
• Battle Progress
• Player Stats
• Screen States
• Hero Selection
• Battle
• Results
• Hero Selection → Battle Initiation → Turn System → Battle Resolution → Results
Key Integration Points
• How SaveDataManager connects to all persistent data points
• Event system flow between UI and game logic
• Demonstrate animation system integration with battle actions
Technical Details
• Unity Scene structure
• DOTween integration points
• Sound system connections
• UI element hierarchy
• ◆ Core Systems
• ● UI Elements
• ■ Data Structures
• → Direct Communication
• ⇢ Event Flow
• ↔ Two-way Data Flow
The save system's integration points
Keep the abstraction level high enough to show system relationships but detailed enough to illustrate the game's core mechanics and data flow. Use the namespace structure (zg.gramrpg) as shown in the file tree to organize the components logically.
Remember to highlight critical paths like:
• Hero selection → Battle initialization
• Battle action → Animation → State update → UI refresh
• Victory/Defeat → Experience gain → Level up system
• Data persistence flow
This will provide a clear understanding of both the architecture and the game flow while maintaining technical accuracy.