Windrose Self-Hosted Admin Console

Sign in

Admin features (config editor, mods, backups, world edits, manual upload, stop server) unlock after a successful sign-in. Leave the username blank; only the password is checked.

Password

Invite

Share this invite code with players. They enter it in the Windrose client to join.

...

Server Status

Server name: -
WindowsServer files: -
Server process: -
Uptime: -
Backend region: -
Active world: -
Save GameVersion: -
Worlds on disk: -
Players: -

Players

#	Name	State	In game	AccountId

Worlds pending changes

Island ID	Name	Preset	GameVersion

Stages a world tarball into R5/Saved/.../Worlds/<id>/; requires a server restart so the game releases its RocksDB handles.

Resource Usage

CPU: -
Memory (RSS): -

Usage is the game process's CPU share / RSS. Cap is the container limit (chart value) or the host's available CPU/RAM when unbounded.

Server Config pending changes

Edit fields then Stage — changes apply on next server restart. Identity (PersistentServerId) and world data are preserved. Under the default env config mode, the entrypoint only re-stamps a field if its current on-disk value matches the last stamp; edits made here diverge from that, so they persist across restarts.

Server name

Max players

Password protected

Password

Active world

Advanced

P2pProxyAddress

PersistentServerId

- read-only — editing would sever the backend island binding

InviteCode

- read-only — minted by the backend

Direct IP Connection (advanced)

Bypasses Windrose's backend connectivity service — players join via a raw IP:port instead of an invite code. Enable only if backend connectivity is blocked on your network, or you want LAN-only play. Requires manual port-forwarding on your router (UDP, to the port below). Invite codes stop working while this is on.

Use Direct IP

overrides the backend connectivity path

Server address

Server port

Proxy address

only set if you're fronting with an explicit proxy

Raw JSON (advanced)

Two-way sync: typing here updates the form fields live (and vice versa). Server validates schema on stage. Invalid JSON just stops the sync until you fix it.

Mods pending restart

Upload server-side Unreal mod archives. Changes are staged and apply on the next server restart, before the game launches.

Mods are third-party code/content loaded by the game server. Only install mods from sources you trust, and expect mismatched or broken mods to prevent players from joining until disabled.

I trust this mod and understand it will be installed on the server after Apply + restart.

Name	State	Uploaded	Size	Files

Backups

Snapshots of R5/Saved/ + identity files under /home/steam/backups/. Retention: most-recent N kept, plus anything within the age window — pinned entries (manual-*) never auto-prune.

ID (UTC)	Size

Import backup (.tar.gz):

Windrose's own auto-backups under R5/Saved/SaveProfiles/Default_Backups/. Managed by the game engine on its own schedule — we surface them here so you can restore one if a UI backup isn't recent enough. Restore merges the selected backup onto the live RocksDB tree and creates a pinned safety snapshot first.

Timestamp (UTC)	Size

Auto-backup schedule

Idle trigger captures state shortly after the last player disconnects — cheap CPU, clean save, natural end-of-session snapshot. Floor trigger is a safety net for long continuous sessions that never go idle. Manual Create backup now does not reset either clock (auto and manual are separate, like in-game auto-saves vs manual saves).

Idle minutes (0 = off)

min without players before auto-backup

Floor hours (0 = off)

max hours of continuous active session before a forced auto-backup

Retain count

most-recent N non-pinned backups kept regardless of age

Retain days

also keep anything younger than this, regardless of count

Last auto-backup: -
Last result: -
Override file: -

Maintenance mode

When on, the entrypoint sleeps instead of launching the game, so the server stays stopped through container/service restarts without editing values or touching systemd. Toggle off to boot normally on the next restart.

Current state: -

Idle CPU patch

Community binary patch that throttles the Boost.Asio drain-loop spin in socket_select_interrupter::reset(). Drops idle CPU from ~200% to ~5% on a canary. Applied by the entrypoint on next container restart when enabled; revertable byte-for-byte. See the script docstring for disclaimer and derivation details.

Binary state: -
Binary MD5: -
Configured via env: -
UI override: -
Effective on next restart: -

Log

Loading status...

Windrose Self-Hosted read-only