Rust Server Configuration
Complete guide to configuring your Rust server on Witchly.host. Learn about server.cfg, startup parameters, decay, crafting, and gameplay settings.
Rust (7 articles)
On This Page
Rust Server Configuration
Rust offers extensive server configuration options through startup parameters and the server.cfg file. Understanding these settings lets you create the exact gameplay experience you want, from vanilla survival to heavily modified custom servers.
Configuration Methods
Rust server settings can be configured in two ways:
- Startup Parameters — Set through the Startup tab in your dashboard. These take effect when the server starts.
- server.cfg — A configuration file in your server’s
server/my_server_identity/cfg/directory. Settings here are applied on startup and can be changed at runtime via the console.
Both methods are complementary. Startup parameters handle core settings (world size, seed, port), while server.cfg handles gameplay tweaks (decay, crafting, PvP rules).
Essential Startup Parameters
These settings are configured in the Startup tab of your dashboard:
| Parameter | Description | Default | Recommended |
|---|---|---|---|
server.hostname | Server name displayed in the browser | Rust Server | Your community name |
server.description | Server description | Empty | Brief rules/info summary |
server.maxplayers | Maximum concurrent players | 50 | Based on your plan |
server.worldsize | Map size in meters | 3000 | 2000-4500 |
server.seed | World generation seed | Random | Any integer |
server.saveinterval | Auto-save interval in seconds | 600 | 300-600 |
server.tickrate | Server tick rate | 30 | 30 (do not change) |
server.headerimage | URL to server banner image (512x256) | Empty | Your banner URL |
server.url | Server website URL | Empty | Your website/Discord |
World size recommendations:
- The Radtown (10 GB): 2000-3500 map size, up to 75 players
- The Launch Site (16 GB): 3000-4500 map size, up to 150 players
Larger maps consume more RAM and take longer to save. Balance map size with your player count — a 4500 map with 20 players will feel empty, while a 2000 map with 100 players will be extremely competitive.
The server.cfg File
The server.cfg file is located at server/my_server_identity/cfg/server.cfg. Edit it through the Files tab in your dashboard or via SFTP (port 2022).
Here is a well-commented example configuration:
// Server Identity
server.hostname "My Rust Server | Witchly.host"
server.description "Welcome to our server! Weekly wipes, active admins."
server.headerimage "https://example.com/banner.png"
server.url "https://discord.gg/yourserver"
// Player Settings
server.maxplayers 100
server.pve false
// Decay Settings
decay.scale 1.0
decay.upkeep true
decay.upkeep_period_minutes 1440
// Crafting
craft.instant false
// Airdrop
airdrop.min_players 15
// Stability
server.stability true
// Chat
chat.globalchat true
chat.localchat true
// Save
server.saveinterval 300
After editing server.cfg, either restart the server or run individual commands through the console to apply changes immediately.
Decay Settings
Decay controls how quickly abandoned structures deteriorate. This is critical for server performance and keeping the map clean:
| Setting | Description | Default |
|---|---|---|
decay.scale | Multiplier for decay rate (0 = no decay, 1 = normal, 2 = double speed) | 1.0 |
decay.upkeep | Whether upkeep costs are enabled | true |
decay.upkeep_period_minutes | How long upkeep materials last before decay begins | 1440 (24 hours) |
decay.upkeep_grief_protection | Minutes of grief protection after a base is raided | 1440 |
Recommended decay configurations:
- Standard server:
decay.scale 1.0with upkeep enabled — vanilla behavior - Casual/beginner server:
decay.scale 0.5— structures last longer, more forgiving for new players - High-activity server:
decay.scale 1.5— faster cleanup of abandoned bases, better performance - No decay (not recommended):
decay.scale 0— bases never decay, but this causes severe performance issues over time as entities accumulate
Important: Never disable decay on a long-running server. Accumulated entities from undecayed bases will cause lag and eventually crash the server. If you want slower decay, reduce decay.scale rather than setting it to 0.
Crafting Settings
| Setting | Description | Default |
|---|---|---|
craft.instant | Instant crafting (no wait time) | false |
craft.timescale | Crafting speed multiplier (lower = faster) | 1.0 |
Setting craft.instant true removes all crafting time, which significantly changes gameplay pacing. Many modded servers use instant craft for a faster-paced experience.
PvP and PvE Settings
| Setting | Description | Default |
|---|---|---|
server.pve | PvE mode (no player damage) | false |
halloween.enabled | Halloween event items and content | false |
xmas.enabled | Christmas event items and content | false |
For more granular PvP control (time-based PvP, zone-based PvP), you will need Oxide/uMod plugins. See our Plugins guide.
Airdrop Settings
| Setting | Description | Default |
|---|---|---|
airdrop.min_players | Minimum online players before airdrops trigger | 15 |
Lower this value on smaller servers so airdrops still occur. For a server with 20-30 max players, set it to 5 or 8.
Admin and Ownership
Managing admin access through the console:
// Grant owner access (full admin + can add other admins)
ownerid <steamid64> "PlayerName" "reason"
// Grant moderator access (admin commands but can't add other admins)
moderatorid <steamid64> "PlayerName" "reason"
// Remove admin access
removeowner <steamid64>
removemoderator <steamid64>
// Save admin changes
server.writecfg
Always run server.writecfg after changing admin lists to persist changes across restarts.
Team Settings
| Setting | Description | Default |
|---|---|---|
maxteamsize | Maximum players per team | 8 |
Adjust based on your server’s focus:
- Solo/Duo/Trio servers: Set to
2or3(enforce with plugins for reliability) - Small groups: Set to
4-6 - Large clans: Keep at
8or increase
Server Identity and Branding
Make your server stand out in the server browser:
- Server name — Include key info like wipe schedule, group size, and gather rate. Example:
[US] MyServer | 2x | Weekly | Solo/Duo/Trio - Description — List rules, Discord link, and key features. Displayed when players hover over your server.
- Header image — A 512x256 PNG or JPG hosted at a public URL. Shows in the server browser above your description.
- Server URL — Links to your website or Discord when players click the link icon.
Runtime Configuration Changes
Many settings can be changed while the server is running using the dashboard console:
- Go to Dashboard and select your server
- Open the Console tab
- Type the command (e.g.,
decay.scale 0.5) and press Enter - Run
server.writecfgto save changes permanently
Changes made via the console take effect immediately but will revert on restart unless saved with server.writecfg.
Configuration Best Practices
- Start with vanilla settings and adjust based on player feedback
- Document your configuration — keep notes on what you changed and why
- Back up server.cfg before making changes (see our Backups guide)
- Test changes during low-traffic hours to minimize disruption
- Announce significant changes to your community in advance
- Monitor performance after changing settings that affect world simulation (decay, entity limits, world size)
For a complete list of Rust server variables, check the official Rust documentation or use the find command in the console to search for specific settings (e.g., find decay lists all decay-related variables).
Need help with server configuration? Our support team is available on Discord.