Skip to main content
Rust servers are configured through convars (console variables). On your Wasabi Hosting server you can set them in two places: the Startup tab of the Game Panel (applied as launch parameters) or the server.cfg file inside your server identity folder. This guide covers the convars that matter most and where to edit them.

Where to Edit Configuration

Launch parameters set in the Startup tab override values in server.cfg. Don’t define the same convar in both places, or you’ll wonder why your server.cfg change “isn’t working.” Never edit serverauto.cfg — it is auto-generated and overwritten by the server.

Essential Convars

ConvarDefaultDescription
server.hostnameServer name shown in the browser. Include rates/wipe schedule for visibility.
server.descriptionDescription shown on the server’s info panel. Use \n for line breaks.
server.headerimageURL to a banner image (512x256 recommended) shown in the server info panel.
server.urlWebsite URL players can open from the server info panel.
server.maxplayers50Maximum concurrent players. Keep it realistic for your plan’s resources.
server.worldsize4500Procedural map size, 10006000.
server.seedrandomMap generation seed. Same seed + same size = same map.
server.identitymy_server_identityFolder name under /server/ where map, saves, and player data live.
server.saveinterval300Seconds between automatic world saves.
decay.scale1.0Decay speed multiplier. 0 disables decay, 0.5 halves it.

RCON Settings

RCON lets external tools (like web RCON clients) send commands to your server:
ConvarDescription
rcon.portRCON port, conventionally game port + 1 (e.g. 28016).
rcon.passwordSet a strong password. Anyone with it has full control of your server.
rcon.web 1Enables WebSocket RCON, required by modern tools such as RustAdmin and web consoles.
You rarely need RCON for day-to-day admin work — the Console tab in the Game Panel gives you a live server console with full command access. Consider locking down the RCON port with the Firewall Manager if you enable it.

Map Size and Seed Explained

Rust generates its procedural map from two values: server.worldsize and server.seed. The same combination always produces the identical map, so you can share or reuse maps you like.
World sizeBest for
10002000Very small servers, aim training, duo battles
30003500Small communities (up to ~50 players), lower RAM usage
4500 (default)Standard full-size map, 100+ players
50006000Large-population servers; longer generation time and higher RAM usage
Example configuration for a mid-size map:
+server.worldsize 3500 +server.seed 1847520
Changing the size or seed only takes effect on a fresh map — you must delete the old map files (a map wipe) for a new map to generate. See the server wipes guide.
Want to preview a map before wiping to it? Community tools like RustMaps let you browse generated maps by seed and size, then copy the values into your Startup tab.

Applying Changes

1

Edit your values

Change convars in the Startup tab or server.cfg as described above.
2

Restart the server

Restart from the Game Panel. Most convars are read at boot; hostname/description changes appear in the browser after the restart.
3

Verify in the console

Type a convar name with no value in the panel Console (e.g. server.worldsize) to print its current value.

Upgrade your Rust experience

Running a bigger map or higher pop? Wasabi Rust servers start at €9.99/month on Ryzen X3D hardware — and upgrades keep all your files.