orion-system-framework

To structure an Unreal Engine system layer safely, define clear architecture boundaries separating GameCore systems from host game modules. This ensures reusable framework code remains isolated from game-specific logic.

Use WorldSubsystem for per-world lifecycle management and GameInstance for global runtime managers persisting across level transitions. Choosing the correct lifecycle pattern prevents state loss during loading.

Integrate AssetManager and GameFeature plugins by defining configuration contracts and module organization rules. This validates loading flows and ensures protected core layers handle asset streaming correctly.

Implement replicated state containers by extending WorldSubsystem patterns and applying subsystem creation rules. This maintains networked state consistency while adhering to framework architecture validation practices.

Yes, the framework guidance applies to both new and existing host game modules. It defines extension workflows and validation practices for reviewing and implementing runtime systems without breaking existing architecture boundaries.