redot-architecture

What problem does it solve?

Redot architecture guides game teams to make deliberate, scalable decisions about data ownership, autoload boundaries, and inter-system communication to avoid brittle, tightly-coupled code.

Core Features & Use Cases

• Autoload responsibilities and ownership boundaries (Constants, GameState, EventBus, SaveManager, and domain managers).
• Clear role separation for world objects, UI, and domain logic to prevent leakage of responsibilities.
• Patterns for scene/tree wiring, cross-scene messaging, and interaction system architecture.
• Guidance on how to coordinate between multiple systems during feature planning and refactoring.

Quick Start

Review your project’s autoloads and scene wiring and adjust to ensure data ownership is centralized and interactions route through EventBus or domain managers.