DocumentationServer Settings
Free

My Settings

Everything you change in Modifiers and Multipliers, Decay & Upkeep, Players and Gameplay, Blueprints, Default Events, the PVP/PVB switches, the locked crate timer and Custom Commands is saved here. When your server restarts, Surge puts it all back automatically.

01What it does

A lot of settings you change on a running Rust server don't survive a restart. My Settings fixes that. Each time you change a supported setting, Surge saves it here. When the server reboots, Surge waits for it to finish starting up and then puts every saved setting back, in the order you originally set them.

You don't need to do anything to turn this on. It's always running in the background.

02What gets saved

  • Cook and Smelt: gather scales, smelting scales, cook speed (including the global cook speed) and output multipliers.
  • Loot-Farm-Gather: global gather and loot scale, yield scales, tool multipliers and farming modifiers.
  • Recyclers: the on/off switch, processing time, start time, safe-zone recycler times and every monument you enable or disable. Force-spawns are one-off and are not saved.
  • Decay & Upkeep: the Decay Upkeep switch and every decay value under Building & Team, including each material's delay and duration, the overrides, decay speed and the advanced upkeep brackets.
  • Players and Gameplay: every value and switch in Players Settings (including Player Insights), Gameplay Settings (including trains) and Auto Turret Configuration, plus each animal and vehicle population you save.
  • Blueprints: the Unlock all switch and any single blueprints you've activated.
  • Default Events: the Bradley Respawn Timer, Heli Respawn Timer and Heli Lifetime.
  • Shortcuts: the Server Wide PVP and PVB switches, and the locked crate timer.
  • Custom Commands: every custom command you've saved.
Good to know

Item Restrictions and the Building Settings and Team Settings tabs of Building & Team are not saved here, so they aren't re-applied after a restart.

Each setting only has one entry. If you change the same thing twice, the newest value replaces the old one instead of piling up.

03How restarts are handled

When your server restarts, the Auto-apply card switches to Restart detected. Surge gives the server about 30 seconds to settle, then puts every saved setting back.

If the server isn't reachable yet, Surge keeps trying. While the server is offline you'll see a notice saying your settings will be applied once it's back.

The Server uptime card shows how long the server has been up and when it last restarted, and Last boot run tells you how many settings went through on the most recent run and whether it was automatic or started by an admin.

04Running boot commands by hand

Press Run Boot Commands to apply every saved setting right now. It's useful for testing, or if you think something didn't take after a restart.

The boot console shows live feedback for each setting as it runs. OK means it went through, FAIL comes with a short reason (like the server not replying in time or the connection dropping), and a final DONE line sums it all up. The badge at the top ends up as All applied, Partly applied or Failed.

The button is greyed out when the server is offline, when nothing is saved yet, or while a run is already going. Only one run can happen at a time.

05The saved settings list

On the right you'll see everything that's saved, grouped by category. Use the chips at the top to filter to one category. The list shows newest first, but remember settings are applied oldest first.

  • A status dot and label on each row show Not run yet, Applied with how long ago, or Failed on last run.
  • Saving a new value for a setting resets it to Not run yet until the next run.
  • Click the X on a row to stop Surge re-applying that setting after restarts. The value on the server right now stays as it is.
Good to know

Removing a custom command from this list deletes it from Custom Commands too.

06Tips

Tip

After a big round of changes, press Run Boot Commands once. If everything comes back OK, you know your next restart will look exactly the same.

Tip

If a row keeps failing, check whether the item short name or value still makes sense after a game update. Remove it, set it again from its own page, and run once more.