Appearance
Framework Overview
This overview maps the framework's runtime responsibilities to the sample project.
From launch to gameplay
Bootstraploads the defaultEngineSettingsfromResources.- Content providers initialize.
- RedEngine creates the configured
GameInstance. - The game instance creates a Fusion runner and travels to the selected scene.
- A
Worldwraps the active simulation scene. - On the server, the world finds the scene's
GameModeBaseactor. - The game mode creates player controllers and characters as players join.
The scene contains the game mode actor directly. Give it a NetworkObject, configure its player controller and character prefabs, and register spawnable prefabs with Fusion.
Where code belongs
| Concern | Typical home |
|---|---|
| Startup and travel | RedEngine.Runtime, GameInstance |
| Player admission and match rules | GameModeBase |
| Application-wide services | GameInstanceSubsystem |
| Scene-scoped services | WorldSubsystem |
| Replicated entities | Actor and ActorComponent |
| Tick input | InputSettings, InputContext, NetworkInputData |
| Abilities and effects | RedEngine.Gameplay.AbilitySystem |
| Items and loadout | Inventory and Equipment modules |
| Player-facing screens | RedEngine.UI |
| Content loading | RedEngine.Assets |
| Logs | Diagnostics module |
| Runtime commands | Developer Console module |
The network rule of thumb
If a value affects the outcome of gameplay, store and update it in Fusion state. A cooldown or respawn deadline belongs in a networked TickTimer. World.TimerManager, Unity coroutines, wall-clock time, and Task.Delay are suitable for local presentation cleanup, not replicated state transitions.
Modules stay optional
Assemblies have deliberately narrow responsibilities. Projects can use Core without Inventory, or Inventory without graph authoring tools. Reference only the required modules to keep dependencies explicit and editor APIs out of runtime code.
Next: Your first multiplayer scene.
Deep dives: GameInstance, Travel, and Bootstrap · GameMode pipeline.