How to configure your Rust server: server.cfg and startup settings

A Rust server is controlled by two things: values passed when it starts, and a config file that runs each time it loads. Knowing which setting belongs where saves a lot of confusion, because some can only be set at start and others can be changed live from the console.

Startup settings and the config file

Startup settings are given on the command line with a + in front, for example +server.hostname "My Server". On a managed panel these usually appear as editable fields on the startup page, so you can change them without touching a command line.

The config file is called server.cfg. It lives in the server's identity folder, inside a cfg directory: server/IDENTITY/cfg/server.cfg. The identity is the name that groups your save data, set by the +server.identity setting. The file is a plain list of commands, one per line, that Rust runs when it starts.

If both set the same value, the later one wins, and which one is later depends on how the server runs it. To avoid surprises, set each value in only one place.

The settings most servers use

server.hostname "My Rust Server | Weekly Wipe"
server.description "Friendly community, no cheating. Join our Discord."
server.url "https://example-community.net"
server.maxplayers 100
server.worldsize 3500
server.seed 12345
server.saveinterval 600
server.pve false
rcon.port 28016
rcon.password "a-long-random-password"

What these do:

  • server.hostname is the name in the server list. Keep it short, and put the wipe schedule in it.
  • server.description is the longer text shown when players select your server. Use \n for new lines.
  • server.maxplayers is the player limit. Set it to what your plan can carry, not the biggest number allowed.
  • server.worldsize and server.seed decide the map. They only matter at map creation, so changing them needs a wipe. See Rust wipes explained.
  • server.saveinterval is how often the world is saved, in seconds. The default of 600 is every ten minutes. Shorter means less lost progress after a crash but more small hitches while saving.
  • server.pve turns on a mode where players cannot hurt each other.
  • rcon.port and rcon.password control remote access, covered below.

Quote text values, and use plain straight quote marks, not curly ones.

Settings that need a restart

Most server. settings load at startup. If you change server.cfg while the server runs, nothing happens until you restart, or until you run the command in the console to apply it. A world size or seed change does nothing to an existing map.

Staying in control of RCON

Rust's remote console, RCON, lets tools send commands to the server, and it uses a password you set. Anyone with the password and access to the port can control your server. Choose a long random one and keep the port private where you can. The risks are the same as for any server, and What RCON is and how to use it safely explains them, even though that article is written for another game. Do not reuse your hosting password.

Choosing a good name and description

Players search lists by keywords, so a name like "[EU] Friendly | Weekly | 2x" tells them what they want at a glance. Include:

  • Your region.
  • The wipe schedule.
  • A key feature, such as vanilla, modded or PvE.

Avoid false claims. Naming a rate you do not run gets you reported, and a bad reputation is hard to repair.

Making the server perform well

A few settings affect performance, but the biggest factors are population, map size and plugins. Keep your map to a sensible size, avoid piling on plugins, and watch your CPU and memory. What the CPU, memory and disk numbers on your server mean explains how to read them. And How to fix server lag lists the common causes.

Saving your changes

When you edit server.cfg, keep a copy of the old one first. If the server will not start after a change, the console says which line it did not like, and you can put the old file back. Editing config files without breaking them covers the common mistakes.

Still stuck? Open a ticket on Discord - run /ticket in any channel, pick a department, and include your Server ID or Invoice ID so we can jump straight in.