How latify/gamearchitecture works
Main System Components
A. Manager Layer (Top Level)
• GameManager (Central Controller)
• UIManager
• AudioManager
• MusicManager
• CameraManager
• SaveManager
• MultiLangManager
B. Systems Layer (Middle Level)
• Dialogue System
• Save/Load System
• Localization System
• Transition System
• Collider System
C. Resource Layer (Bottom Level)
• Animations
• Fonts
• Sprites
• Audio Files
• Language Files
Component Relationships
• Systems should connect to their respective managers:
• Dialogue System → UIManager
• Save/Load System → SaveManager
• Localization System → MultiLangManager
• Transition System → UIManager
• Collider System → GameManager
Specific Component Details
GameManager:
┌─────────────────────┐
• GameManager │
• ┤
• Scene Management │
• Game State │
• Core Events │
• Manager Registry │
• ┘
Systems:
┌─────────────────────┐
• Dialogue System │
• ┤
• Writer │
• Text Effects │
• Event Triggers │
• ┘
Implementation Notes
Notes for:
• Don't Destroy On Load components
• Scene-specific vs. Persistent objects
• Resource loading paths
• Save data structure
The persistence and state management
Remember to include version information and any critical dependencies (like TextMeshPro) in a separate documentation block.
This architecture represents a robust game framework with emphasis on modularity, extensibility, and clean communication between components.