Skip to main content

Why did a Rust setting change back after restart?

If you changed a variable through the live console, check where your host keeps the settings for the next start. The console can show a successful change while an older value still waits in the startup settings.

Compare the same variable in every place it is set

For example, suppose the running console reports server.maxplayers as 20 and server.cfg also lists 20. If your launcher still passes +server.maxplayers 10, the game starts with 10 on builds that use the startup order Facepunch documents in Soft Refresh.

On a rented server, check the panel’s startup value as well as the file. If the host generates that argument, update the panel value. On a self-hosted server, choose one place you control for the setting and remove the conflicting entry if your setup allows it.

Check the value after a planned start

At the next planned restart, type just server.maxplayers in the server console to read it. If the wrong number returns, check that you edited the file under the running server’s identity and that the launcher is using the settings you changed.

Leave the same value in the settings your launcher actually uses and read it again after the next planned start.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details