How to Configure Your Rust Server (2025) – Complete Config & Console Command Guide
Running a Rust server is one thing. Configuring it properly is another. With the right tweaks, you can optimise performance, secure your server, and deliver the kind of gameplay experience that keeps players coming back.
This guide covers every Rust server configuration option, including launch parameters, server.cfg variables, console commands, and advanced decay/crafting settings. Whether you’re a first-time admin or running a large community, this is the most up-to-date reference you’ll find in 2025.
Getting Started: Where to Configure Rust Servers
Windows Users
- Use your .bat startup file in the Rust server directory.
- Open it with Notepad and edit the parameters directly.
Linux Users
- If you’re using LinuxGSM (LGSM), configs live in
rustserver.cfg. - Edit with:
nano rustserver.cfg
- Save changes and restart your server.
Config File vs Console
- server.cfg – permanent settings applied on boot.
- Console commands – temporary, unless saved with
server.writecfg.
Core Rust Server Launch Parameters
Here are the most critical options you should set in your .bat or launch file:
| Parameter | Default | Description |
|---|---|---|
+rcon.password | none | Change this immediately. Sets your RCON password for remote admin. |
+rcon.port | 28016 | Port for RCON. Open in firewall for remote access. |
+rcon.web | 1 | Enables WebSocket RCON. Required for some tools. |
+server.ip | 0.0.0.0 | Bind server to IP. Leave at 0.0.0.0 unless multi-IP. |
+server.port | 28015 | Main game port. Needs port forwarding. |
+server.queryport | 27015 | Controls visibility in server list. Must be open. |
+server.hostname | My Rust Server | Name shown in server browser. |
+server.description | none | Add rules, wipes, features here. Supports limited formatting. |
+server.maxplayers | 50 | Player slots. Dependent on hardware. |
+server.tickrate | 30 | How many updates per second. Higher = smoother but heavier on CPU. |
+server.worldsize | 3000 | Map size. Max 6000. Larger maps need more RAM. |
+server.seed | 0 | Map seed. Use to replicate specific maps. |
+server.saveinterval | 600 | Save interval in seconds. Default 10 minutes. |
+logfile | gamelog.txt | Write crash/error logs. |
-silent-crashes | n/a | Prevents popups on crash. Auto restarts in service mode. |
Rust Server Console Commands
Once your server is running, you can execute commands via console or RCON. Here are the most useful:
General Admin Commands
server.writecfg– Saves all settings to config file.quit– Shutdown server safely.status– Shows current players and connection info.kick “username”– Kick a player.ban “username/steamid”– Ban player.
Gameplay Toggles
server.pve true/false– Enable PvE mode.craft.instant true/false– Toggle instant crafting.chat.serverlog true/false– Enable or disable chat logging.
Environment & Performance
server.itemdespawn X– Time in seconds before items despawn (default 180).server.framerate X– Control FPS cap for server performance testing.server.tickrate X– Adjust tickrate dynamically.fps.limit X– Cap server frame rate.
AI & NPC Settings
ai.tickrate X– Frequency of NPC/animal updates. Lower = less lag.ai.move true/false– Toggle AI movement.ai.think true/false– Toggle AI logic.
Building Decay Configuration
Rust’s Building 3.0 system made decay more flexible. Default decay rates:
- Twig – 1h
- Wood – 2h
- Stone – 3h
- Metal – 5h
- Armoured – 12h
Key Decay Commands
decay.tick X– Frequency of decay ticks. Default 600.decay.scale X– Global decay speed multiplier.decay.upkeep true/false– Enable or disable upkeep system.decay.bracket_0_blockcount X– Adjust upkeep brackets.decay.upkeep_period_minutes X– Length of upkeep (default 1440 = 24h).decay.upkeep_heal_scale X– Healing speed when upkeep met.decay.upkeep_inside_decay_scale X– Inside decay speed.
Crafting, Loot & Economy Options
craft.instant true/false– Enable instant crafting.craft.timescale X– Modify crafting speed multiplier.server.globallootmodifier X– Scale loot tables globally.server.gather X– Adjust resource gathering multiplier.
Advanced Configuration
Networking
+server.secure true/false– VAC anti-cheat.+rcon.secure true/false– Enforce RCON authentication.+queryport– Manage server list queries.
Performance & Scaling
gc.interval X– Garbage collection frequency. Lower = less memory use, more CPU.gc.buffer X– Memory buffer size.server.maxthreads X– Force thread limits.
Security
server.encryption true/false– Encrypt traffic between client and server.server.secure true/false– Enable VAC security checks.
Best Practices for Rust Server Config
- Keep RCON secure – Use strong passwords and whitelist IPs.
- Don’t overdo tickrate – Stick near 30. Higher doesn’t mean better.
- Match world size to player count – 100 players? Use at least 4000–4500 world size.
- Back up your configs – Save
server.cfgand restart scripts in Git or cloud. - Monitor performance – Use
perf 1to track server FPS.
FAQs
Q: Where is my Rust config stored?
- Windows:
server\cfg\server.cfg - Linux:
lgsm/config-lgsm/rustserver
Q: Do console commands persist after restart?
No. Save them with server.writecfg.
Q: Can I disable decay?
Yes. decay.scale 0 disables it globally, or decay.upkeep false.
Q: How many players can I support?
Depends on hardware. A Ryzen 7950X3D with 64GB RAM can support ~200 players at 4000 world size.
Conclusion
Rust’s server configuration is vast — and that’s before you get into mods. Start with core parameters (RCON, ports, hostname, maxplayers, worldsize), then fine-tune performance and gameplay with console variables.
Configured correctly, you’ll run a stable, secure, and fair server that players want to join.
⚡ Want Hassle-Free Configuration?
With EUGameHost Rust Server Hosting you don’t need to worry about editing configs manually:
- One-click Rust + Oxide installs
- Auto-updates for every patch
- Pre-optimised configs
- Bulletproof DDoS protection
- High-performance Ryzen hardware