When configuring your Rust server, you’ll encounter two important files: server.cfg
and serverauto.cfg
. Although similar in name, these files serve different purposes and load differently. Knowing when to use each will help you manage your server settings efficiently.
π§ Overview of Configuration Files
Hereβs a quick breakdown of each file:
File Name | Loaded Automatically? | Execution Method |
---|---|---|
server.cfg | β No (manual load required) | Long-term configurations; server name, description, tags, plugin settings, custom commands. |
serverauto.cfg | β Yes, automatically at server startup | Essential settings that must load at every startup |
π Detailed Explanation
server.cfg
The server.cfg
file does not load automatically when your server starts. Instead, you must manually execute it with an in-game or RCON command each time you want to apply these settings:
server.readcfg
It’s ideal for storing settings like:
- Server hostname and description
- Rates (such as tick rate and player limits)
- Plugin configurations or special settings you may occasionally adjust
Recommended for:
- Long-term settings
- Settings that rarely change
- Special character support in the server name or description
Example Usage:
server.hostname "GGServers | The Best Rust Server!"
server.description "Welcome to GGServers Rust Server!\nHigh-performance hardware\nDDoS Protection\n\n\n\n\n\n\n\n"
server.tags "monthly,pve,roleplay"
β οΈ Important: You must run
server.readcfg
via console (F1) or RCON to load these settings after editing.
serverauto.cfg
This file automatically loads every time your Rust server starts. This makes it the ideal location for critical settings you need consistently enforced.
Example of settings typically added here:
- World seed (
server.seed
) - Map size (
server.worldsize
) - Difficulty (
server.pve
) - Automatic server protection settings
Example Usage:
server.seed 123456
server.worldsize 3500
server.pve false
β οΈ Important:
Do NOT manually edit the serverauto.cfg
file through your panel, as it resets automatically if modified incorrectly.
π© When to Use Each File (Quick Summary)
File | Recommended Use | When Does it Load? |
---|---|---|
server.cfg | Custom server names/descriptions, long-term or special configs | Manual: Execute using server.readcfg |
serverauto.cfg | Essential settings (map seed, map size, PvE/PvP mode) | Automatic: Every time the server restarts |
π© Recommended Best Practices
- Use
serverauto.cfg
for settings, you want to ensure always loads automatically. - Use
server.cfg
for occasional or manually-loaded settings, especially ones needing special characters.
Important:
Do NOT add settings to serverauto.cfg
manually unless absolutely necessary, as unintended edits can reset after server updates.
β Practical Examples
Here’s how a basic server.cfg
might look:
server.hostname "GGServers.com | High-Quality Rust Hosting"
server.description "Fast, reliable Rust servers powered by GGServers.com\nHosted on Ryzen CPUs\nJoin our Discord for support!\n\n\n\n\n\n\n"
server.tags "monthly,pve,roleplay"
For automatic critical settings, your serverauto.cfg
typically includes:
server.seed 123456789
server.worldsize 3500
server.maxplayers 150
server.pve false
β Notes & Best Practices
- Rust currently duplicates the server description due to an ongoing bug; adding multiple
\n
at the end minimizes the visual issue. - Only 4 tags are displayed publicly in Rustβs server browser.
- Avoid using multiple tags from the same category (e.g., don’t use
weekly
andmonthly
simultaneously).
Difference Between server.cfg
and serverauto.cfg
Here’s a simple breakdown to help you decide which configuration file to use:
π§ server.cfg
- Does NOT load automatically.
(You must runserver.readcfg
manually to apply settings.) - Use for settings like server name, description, and other options that rarely change.
Example:server.hostname "My Rust Server" server.description "Welcome to my Rust server!"
βοΈ serverauto.cfg
- Loads automatically whenever your server starts.
- Use it for essential settings such as:
- Map size (
server.worldsize
) - Map seed (
server.seed
) - PvE mode (
server.pve
)
Since it runs automatically and takes priority, most server owners prefer using this file.
β Quick Tips:
- Use
serverauto.cfg
for critical, always-needed settings. - Use
server.cfg
for custom or long-term settings that rarely change.
π οΈ Still Need Help?
If you’re unsure about configuring your Rust server or need additional help, please reach out to our support team.