Where is server.cfg located?

In server/ /cfg/server.cfg, where is the server identity you launched with. Many host panels expose it as a 'server config' editor — same file underneath.

Do server.cfg changes need a restart?

Most convars can be set live in the console and take effect immediately. server.cfg is just a list of console commands run at boot — so editing the file changes what happens next restart, while running the same command in console changes it now.

What's the difference between server.cfg and the command line?

Command-line arguments (-batchmode, +server.identity, +server.port) set up how the process launches and can't easily change at runtime. server.cfg holds gameplay and world convars that you tune over the life of the server.

Rust server.cfg Settings — Full Reference

There is no single official, complete server.cfg reference — the settings are scattered across the Facepunch wiki, host knowledgebases, and forum posts of varying age. This page collects the convars that actually shape a community server, grouped by what they do, with sane starting values.

World & gather rates

The settings players notice first. Vanilla gather is 1.0; community servers commonly run 2–3x.

# Note: gather-rate scaling is usually handled by a plugin
# (e.g. GatherManager) for per-resource control. Core world convars:
server.tickrate 30          # network tick; 30 is fine for most, raise carefully
spawn.max_density 1.0       # resource node density
decay.scale 1.0             # 0.5 = slower base decay, 0 = no decay

For real gather control you want a plugin — see the directory— because server.cfg can't scale gather per-resource.

Decay & upkeep

The most-tweaked category on community servers, because vanilla decay punishes casual players.

decay.scale 0.5             # halve decay damage
decay.upkeep true           # whether upkeep (tool cupboard cost) applies
decay.duration 600          # seconds of grace before decay starts ticking

Population & world

server.maxplayers 100
server.worldsize 4000       # 3000-4500 typical; bigger = more spread, more load
server.seed 12345           # map seed; changes the map on next wipe
server.saveinterval 300     # seconds between world saves

server.worldsize and server.seed only take effect on a fresh map (a wipe). Changing them mid-wipe does nothing until the next map.

Performance — the convars hosts hide

These don't change gameplay but keep a busy server from stuttering. Host panels often don't surface them at all.

fps.limit 256               # uncap-ish; let the box do its work
server.entityrate 30
ai.npc_max_population_military_tunnels 1
budget.boundscheckmemory false

Identity & networking (command line, not server.cfg)

These belong on the launch command, not in server.cfg, because they define how the process starts:

+server.identity "myserver"
+server.port 28015
+server.queryport 28017
+rcon.port 28016
+rcon.password "use-a-real-password"

Where server.cfg fits in setup

server.cfg is step three of standing up a server: install the dedicated server, add Carbon, tune server.cfg, add your admins, then install plugins. The full path is in the Rust server setup guide.

rust server.cfg Settings — The Complete Reference