This guide covers how to configure your Rust dedicated server hosted with Legion Hosting, including server.cfg settings, GPanel startup variables, wipe scheduling, save management, and how to connect.
server.cfg or any other configuration files. Changes made while the server is running may be overwritten on shutdown.
Server Configuration — server.cfg
Rust reads its primary configuration from server/rust/cfg/server.cfg on your server. This file is created automatically the first time your server starts. Open it in the GPanel Files tab to edit your server's core settings.
Key Settings Reference
| Setting | Example Value | Description |
|---|---|---|
server.hostname |
My Legion Rust Server |
The name displayed in the in-game server browser. Make it descriptive so players can find your server. |
server.maxplayers |
40 |
Maximum number of simultaneous players. Should not exceed the slot limit on your hosting plan. |
server.worldsize |
3000 |
Map size in metres. Common values: 1000 (small), 2000, 3000 (medium), 4000, 6000 (large). Larger maps require significantly more RAM and CPU. |
server.seed |
123456 |
The random seed used to generate the map. The same seed + worldsize always produces the same map. Change this (with a map wipe) to generate a fresh map layout. |
server.saveinterval |
60 |
How often (in seconds) the server saves world data to disk. Default is 60 (1 minute). Lower values reduce data loss on crash but increase disk I/O. |
server.description |
A chill PvE server |
A description shown on the server info panel in-game. Keep it short and informative. |
server.url |
https://discord.gg/yourserver |
A URL shown on the server info panel. Typically a Discord invite or website. |
A minimal example server.cfg:
server.hostname "My Legion Rust Server"
server.maxplayers 40
server.worldsize 3000
server.seed 123456
server.saveinterval 60server.hostname "My Server". Numeric values do not need quotes.
rcon.password, rcon.port, rcon.web), see the Rust RCON Access and Admin Commands guide.
GPanel Startup Variables
Some Rust settings are configured as startup arguments in GPanel rather than in server.cfg. These control low-level server behaviour that must be set before the process starts.
- Log in to GPanel.
- Select your Rust server from the server list.
- Click the Startup tab.
- Review and set the variables shown. Changes here take effect the next time you start the server.
Key Startup Variables
| Variable | Default | Description |
|---|---|---|
QUERY_PORT |
(assigned) | The Steam query port used for server browser listings. Must match the query port assigned in GPanel's Network tab. |
APP_PORT |
(assigned) | Port for the Rust+ companion app. Set to -1 to disable the Rust+ app entirely if you do not need it. |
WORLD_SEED |
0 |
The map generation seed. When set to 0, the server automatically generates a random seed and saves it to seed.txt. The same random seed is reused on restart until you delete seed.txt or set a specific seed value. To get a completely different map layout, delete seed.txt before restarting, or set a specific non-zero seed here. |
FRAMEWORK |
vanilla |
The modding framework to load. Set to oxide or carbon to enable a modding framework, or leave as vanilla for no mods. See the Rust Oxide/uMod Plugin Installation guide for full details. |
server.cfg, the startup argument takes precedence. Use the Startup tab for ports, identity, and framework selection; use server.cfg for in-game tuning settings.
How to Connect to Your Server
Rust does not have a built-in server browser that is easy to search. The fastest way to connect directly is through the in-game F1 console.
- Launch Rust and reach the main menu.
- Press F1 to open the developer console.
- Type the following command and press Enter:
Replaceclient.connect IP:PORTIPandPORTwith your server's IP address and game port as shown in the GPanel Network tab.
You can also add the server to your in-game favourites list so it appears in Play > Community Servers > Favourites for quicker access in future sessions.
For details on finding your server's IP and port, see How to Find Your Server IP and Port.
Wipe Schedule and Mechanics
Rust has a built-in wipe system with two distinct types of wipe. Understanding the difference is essential for running a well-managed server.
Map Wipe vs Blueprint Wipe
| Wipe Type | What is Erased | What is Kept |
|---|---|---|
| Map Wipe | All player bases, items, resources on the map, and player positions. | Blueprints (research progress) and player data files. |
| Blueprint (BP) Wipe | All blueprints — players start from scratch on research. | Nothing specific — a BP wipe is almost always combined with a map wipe. |
Forced Wipes — First Thursday of Every Month
Facepunch (the Rust developer) releases mandatory game updates on the first Thursday of every month. These updates force a map wipe on all servers — the server cannot be used until the wipe is completed. Blueprint wipes are not always forced; Facepunch announces in advance when a forced BP wipe accompanies the monthly update.
How to Perform a Map Wipe
- Stop your server from the GPanel Console tab.
- Go to the Files tab and navigate to
server/rust/. - Delete all files matching
proceduralmap.*.savinserver/rust/. These are the world save files. - Also delete any files matching
proceduralmap.*.mapin the server root directory. These are the pre-generated map files. - Optionally update the
WORLD_SEEDstartup variable (orserver.seedinserver.cfg) to generate a completely different map layout. You can also deleteseed.txtif present to force a new random seed. - Start the server. Map generation will take several minutes on first start — this is normal.
How to Perform a Blueprint Wipe
- Stop your server.
- Navigate to
server/rust/in the GPanel file manager. - Delete the
.dbfile (e.g.player.blueprints.dbor similar). This file stores all player blueprint data. - Perform a map wipe at the same time (recommended) by also deleting the
proceduralmap.*.savsave files andproceduralmap.*.mapfiles as described above. - Start the server.
Save Management
Rust auto-saves the world at the interval defined by server.saveinterval (default: 60 seconds). Keep these tips in mind to avoid unexpected data loss:
- Verify
server.saveintervalis set to a reasonable value. Setting it to0or a very large number effectively disables auto-saves. - Run
server.savemanually via the GPanel console before stopping the server to force an immediate save. - Always stop the server gracefully from GPanel rather than killing the process. An abrupt kill can cause the last save interval's changes to be lost.
Related Articles
- Rust RCON Access and Admin Commands — RCON setup, external tools, and useful admin commands
- Rust Oxide/uMod Plugin Installation — Installing Oxide/Carbon, adding plugins, and popular plugin recommendations
- Rust Server Troubleshooting — Common issues and how to resolve them
- How to Find Your Server IP and Port
- How to Upload Files via SFTP
Need Help?
If you run into an issue not covered in this guide, our support team is available to help. Submit a support ticket and include your server ID, a description of the issue, and any relevant console output.
