Skip to content

Framework Overview ​

This overview maps the framework's runtime responsibilities to the sample project.

From launch to gameplay ​

  1. Bootstrap loads the default EngineSettings from Resources.
  2. Content providers initialize.
  3. RedEngine creates the configured GameInstance.
  4. The game instance creates a Fusion runner and travels to the selected scene.
  5. A World wraps the active simulation scene.
  6. On the server, the world finds the scene's GameModeBase actor.
  7. 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 ​

ConcernTypical home
Startup and travelRedEngine.Runtime, GameInstance
Player admission and match rulesGameModeBase
Application-wide servicesGameInstanceSubsystem
Scene-scoped servicesWorldSubsystem
Replicated entitiesActor and ActorComponent
Tick inputInputSettings, InputContext, NetworkInputData
Abilities and effectsRedEngine.Gameplay.AbilitySystem
Items and loadoutInventory and Equipment modules
Player-facing screensRedEngine.UI
Content loadingRedEngine.Assets
LogsDiagnostics module
Runtime commandsDeveloper 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.

RedEngine Framework documentation