Skip to content

Add server controls to experience page menu - #439

Open
KyoMarketing wants to merge 5 commits into
NotValra:mainfrom
KyoMarketing:feat/game-server-controls
Open

KyoMarketing wants to merge 5 commits into
NotValra:mainfrom
KyoMarketing:feat/game-server-controls

Conversation

@KyoMarketing

Copy link
Copy Markdown

What it does

Adds two options to the "⋯" menu on experience pages you can manage (right under "Configure this Place"):

  • Restart servers for updates: closes only the servers running an old version, players are moved to the latest version.
  • Shut down all servers: closes every server of the experience, including the ones on the latest version.

Both ask for confirmation first and show a success or error alert. The options only appear if you have manage permission on the experience.

Why

After publishing an update you no longer need to open the Creator Hub, find the experience and go to Server Management. It's one click from the experience page.

How

  • Uses the matchmaking API launch-update endpoint (same one the Creator Hub uses), with closeOldVersionsOnly: true for restart and false for shut down, as recommended in Roblox's Server Management announcement. The old shutdown endpoint no longer works for this.
  • Same structure as the Make Public / Make Private PR (add make public / make private to the experience page menu #381): permission check with develop/v1/universes/multiget/permissions, items injected in #game-context-menu.

Settings

New Server Controls setting in Developer, with a child toggle for each action.

Screenshots

{CD15DD30-95F8-4E14-8393-84705B2828F2} {39864858-D683-496B-9F22-E49AE24EF110} {5A6890C3-FB2C-4688-B768-E1A14AFD7AAD}

Adds Restart servers for updates and Shut down all servers to the experience page menu for experiences you can manage, using the matchmaking API with a confirmation prompt.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants