Unreservation flow

Note: The content on this page pertains to Clanforge. If you’re using Multiplay Hosting, refer to the Multiplay Hosting documentation.

Similarly to deallocations, Clanforge must know when a game server that's using the reservation model is no longer in use to return that server back to the available pool.

The following steps outline the unreservation process. A flowchart showing the game client first connecting to the game server, which in turn communicates with Multiplay Hosting's reservation processor to return an unused server back to the available pool.

  1. The game session finishes.
  2. The game server calls the Unreserve API endpoint to unreserve itself.
  3. Clanforge's reservation processor looks up the calling game server, then adds it back to the available server pool. This is done to help with scaling decisions rather than to prevent it from being allocated twice.