Change a managed server's allowed origins, error reporting, logging and database without re-creating it.

Game Server Settings

Change your managed server's security, error-reporting, logging and database settings without re-creating it. Your settings are sent to the running server; an empty server restarts with them right away, and a busy one restarts after an in-game countdown (or waits for its next update, if you prefer).

Where to author it#

Account → Studio → your project → Server → the server's detail view → Game server settings panel (under Game server updates).

Set it up#

Open your server's detail view and scroll to Game server settings.
Pick Allowed browser origins. Leave it on Recommended unless you host your own play page — the recommended list is the ED5 play site and Studio Web, which is where your players and your editor connect from.
Optionally paste your Sentry DSN and choose the other settings (each dropdown's Default keeps the built-in behaviour).
Choose When players are online: restart after an in-game countdown, or wait for the next update / restart. Pick the countdown length.
Click Preview changes. Nothing is saved; you see exactly which settings change and what will happen on the server (restart now, countdown, or wait).
Click Save server settings. The status line shows when the settings are on the server and when they are live.

Fields#

Field	What it does
Allowed browser origins	Web pages allowed to open a game connection. Recommended = the ED5 play site + Studio Web. Custom list = your own comma-separated origins (`https://play.example.com`, `.example.com`). None* = log other pages but let them connect. The desktop player and native clients are always allowed.
Origin check	strict refuses web pages not on the list; shadow only logs them; off disables the check. Default: strict whenever origins are listed.
Sentry DSN	Sends server errors to your Sentry project. Stored hidden; leave blank to keep it, tick Remove to clear it.
Sentry error sample rate	Share of errors sent to Sentry (1 = all).
Log level	Lowest level written to the server log (debug, info, warn, error, silent).
Log format	text or json (one object per line, for log shippers).
Player message validation	strict drops malformed player messages; shadow only logs them. Use shadow only as a temporary kill switch.
Tick intent queue	off restores direct handling of slow player actions. Kill switch — leave on Default.
External database	Runs your world on your own Postgres instead of the database built into the server. Paste a connection string (`postgres://user:password@host:5432/database`; Supabase connection strings work too). Stored as a secret: the dashboard only shows whether it is set. Leave empty to use the built-in database.
When players are online	Restart after an in-game countdown: players see warnings at 10 / 5 / 1 minutes, the world is saved, everyone reconnects automatically. Wait for the next update or restart: nobody is interrupted.
In-game countdown	Countdown length when restarting a busy server (1–30 minutes).

Gotchas#

An empty server restarts immediately in either mode — that is how the new settings take effect.
"Settings apply only when the server is next re-created" means your server runs an older agent. Saved settings are kept and are applied the next time the server is re-created (resize, restore or re-provision); servers created from now on receive them live.
Custom origins must be exact web origins (https://host[:port], or *.domain.tld for all subdomains). Paths, * alone and *.com are refused. If players on your own site can't connect after switching to a custom list, add that site's origin or go back to Recommended.
Switching to an external database starts from an empty world. The server sets up the new database and creates a starter world there. Publish your project again from the editor to put your content on it. Player characters stay in the built-in database — they do not move across.
Switching back is safe. The built-in database is kept on the server untouched while you use an external one. Clear the field and save to go back to it.
The database host must be public. Addresses like localhost, 127.0.0.1, 10.x, 192.168.x and other private ranges are refused ("External database: the host must be a public database server.").
You back up an external database. While one is set, the server's automatic backups and automatic restore are switched off — use your database provider's backups.
If the server cannot reach the external database, the world stays offline and the server's status shows database failed with the connection error. Fix the database or the connection string and save again.
Sharding settings are managed by ED5 and appear read-only ("Managed by ED5: …"). Multi-server is switched on by ED5 for eligible plans.
If an update countdown is already running, your settings ride along with that restart instead of starting a second countdown.
Nothing to enable: there is no feature flag. The panel says "not enabled yet" until ED5 has switched the feature on for the platform.

Game Server Settings

Set it up#

Open your server's detail view and scroll to Game server settings.

Pick Allowed browser origins. Leave it on Recommended unless you host your own play page — the recommended list is the ED5 play site and Studio Web, which is where your players and your editor connect from.

Optionally paste your Sentry DSN and choose the other settings (each dropdown's Default keeps the built-in behaviour).

Choose When players are online: restart after an in-game countdown, or wait for the next update / restart. Pick the countdown length.

Click Preview changes. Nothing is saved; you see exactly which settings change and what will happen on the server (restart now, countdown, or wait).

Click Save server settings. The status line shows when the settings are on the server and when they are live.

Fields#

Field	What it does
Allowed browser origins	Web pages allowed to open a game connection. Recommended = the ED5 play site + Studio Web. Custom list = your own comma-separated origins (`https://play.example.com`, `.example.com`). None* = log other pages but let them connect. The desktop player and native clients are always allowed.
Origin check	strict refuses web pages not on the list; shadow only logs them; off disables the check. Default: strict whenever origins are listed.
Sentry DSN	Sends server errors to your Sentry project. Stored hidden; leave blank to keep it, tick Remove to clear it.
Sentry error sample rate	Share of errors sent to Sentry (1 = all).
Log level	Lowest level written to the server log (debug, info, warn, error, silent).
Log format	text or json (one object per line, for log shippers).
Player message validation	strict drops malformed player messages; shadow only logs them. Use shadow only as a temporary kill switch.
Tick intent queue	off restores direct handling of slow player actions. Kill switch — leave on Default.
External database	Runs your world on your own Postgres instead of the database built into the server. Paste a connection string (`postgres://user:password@host:5432/database`; Supabase connection strings work too). Stored as a secret: the dashboard only shows whether it is set. Leave empty to use the built-in database.
When players are online	Restart after an in-game countdown: players see warnings at 10 / 5 / 1 minutes, the world is saved, everyone reconnects automatically. Wait for the next update or restart: nobody is interrupted.
In-game countdown	Countdown length when restarting a busy server (1–30 minutes).

Gotchas#

An empty server restarts immediately in either mode — that is how the new settings take effect.

"Settings apply only when the server is next re-created" means your server runs an older agent. Saved settings are kept and are applied the next time the server is re-created (resize, restore or re-provision); servers created from now on receive them live.

Custom origins must be exact web origins (https://host[:port], or *.domain.tld for all subdomains). Paths, * alone and *.com are refused. If players on your own site can't connect after switching to a custom list, add that site's origin or go back to Recommended.

Switching to an external database starts from an empty world. The server sets up the new database and creates a starter world there. Publish your project again from the editor to put your content on it. Player characters stay in the built-in database — they do not move across.

Switching back is safe. The built-in database is kept on the server untouched while you use an external one. Clear the field and save to go back to it.

The database host must be public. Addresses like localhost, 127.0.0.1, 10.x, 192.168.x and other private ranges are refused ("External database: the host must be a public database server.").

You back up an external database. While one is set, the server's automatic backups and automatic restore are switched off — use your database provider's backups.

If the server cannot reach the external database, the world stays offline and the server's status shows database failed with the connection error. Fix the database or the connection string and save again.

Sharding settings are managed by ED5 and appear read-only ("Managed by ED5: …"). Multi-server is switched on by ED5 for eligible plans.

If an update countdown is already running, your settings ride along with that restart instead of starting a second countdown.

Nothing to enable: there is no feature flag. The panel says "not enabled yet" until ED5 has switched the feature on for the platform.