Disconnect Fallback Rules
A disconnect fallback rule defines what happens when a player unexpectedly loses their connection to a server — for example, if the server crashes, restarts, or becomes unreachable.
Without a fallback, the player simply gets disconnected and has to reconnect manually. With a fallback rule, OrbisManager quietly moves them to another server so they stay in your network.
How it works
When a player disconnects from a server unexpectedly, OrbisManager checks if there's a fallback rule matching that source. If one is found, the player is automatically sent to the target server or pool.
Creating a fallback rule
Click + Add Rule and set:
| Field | What it does |
|---|---|
| Name | A label for this rule |
| Source | Which server or pool the player disconnected from |
| Target (Fallback) | Where to send the player |
Both source and target can be either a single server or a pool.
Using a pool as the target
Using a pool as the fallback target is recommended. If the fallback server is offline or full, OrbisManager will automatically pick another available server from the pool.
Example:
- Source: Any game server in Game Pool
- Target: Lobby Pool (always has space)
Example setup
A typical network might have:
- Players join through the Lobby
- From the lobby, they go to Game Servers
- If a game server crashes mid-game:
- Fallback rule: Source = Game Pool → Target = Lobby Pool
- Players are quietly moved back to a lobby server
This keeps players in your network even when individual servers have problems.
Set up fallback rules for every important server group. At minimum, make sure your game servers always fall back to a lobby or hub.