Configure Building Decay on a Rust Server

Updated 6 November 2026 · Standard formula, shown below

This guide explains how to adjust the building decay system on a Rust server, giving you control over how quickly player-built structures deteriorate when not maintained. You’ll edit the server’s configuration files to set decay rates, damage thresholds, and upkeep requirements. Before starting, ensure you have file access to your server’s root directory and that the server is stopped to avoid conflicts.

What You’ll Need

Access to your Rust server’s files (via FTP, file manager, or console)
A text editor (Notepad++, VS Code, or even Notepad)
Basic understanding of Rust’s server configuration structure
If using a hosting panel (like Oxide/ uMod), ensure it’s installed for advanced decay tweaks

Step-by-Step

Stop your server to prevent file corruption while editing.
Locate the server files – typically in a folder named server or rust on your hosting. The main config file is server.cfg in the root directory.
Open server.cfg with a text editor. This file contains startup parameters and console commands.
Add or modify decay-related commands. The most common ones are:
- decay.upkeep – Set to true (default) to enable upkeep system, or false to disable it entirely (structures decay faster unless you also adjust decay.scale).
- decay.scale – Global decay multiplier. Default is 1.0. Lower it (e.g., 0.5) to slow decay, raise it (e.g., 2.0) to speed up.
- decay.duration – Time in minutes before a structure starts decaying after being placed. Default is 1440 (24 hours). Set to 0 for immediate decay.
- decay.tick – How often decay is applied in seconds. Default is 600 (10 minutes). Lower values make decay more responsive.
Set specific building block decay values (optional). For finer control, use commands like building.blockdecay and building.decay. Example: building.blockdecay 0.2 to make foundations decay slower than walls. These are advanced and require testing.
If using Oxide/uMod, you can install a plugin like Building Decay for more granular settings. After installing, edit its config file in oxide/config/ – look for files like BuildingDecay.json. Adjust values like decayMultiplier or per-material settings.
Save the file and close it.
Start your server and test the decay by placing a structure and observing how long it takes to start decaying.

Common Mistakes

Editing while the server is running – changes may be overwritten or cause crashes.
Setting decay.upkeep false without adjusting decay.scale – this leads to extremely fast decay, often making bases unplayable.
Using wrong syntax – commands are case-sensitive and use periods, not spaces. For example, decay.scale 0.5 is correct, decay scale 0.5 is not.
Forgetting to save – always save after edits; some editors require explicit save.
Not backing up original config – if you break something, you’ll need a clean copy.

Tips

Start with small changes – modify one setting at a time to see its effect.
Use a test server – try changes on a private server before applying to a live one.
Understand the upkeep system – with decay.upkeep true, structures decay only if the tool cupboard lacks resources. Adjusting decay.scale affects how fast they decay when upkeep runs out.
Read the official Rust wiki – for a full list of decay commands and their defaults.
Consider player experience – too fast decay frustrates players, too slow makes raiding less rewarding. Balance is key.

Troubleshooting

Changes not taking effect – verify the server is fully stopped, re-check the file path, and ensure you’re editing the correct server.cfg. Some hosts use a separate config file; check your panel’s documentation.
Server won’t start – likely a syntax error. Remove the lines you added and re-add them one by one, testing each time.
Decay too fast/slow – adjust decay.scale incrementally (e.g., 0.1 steps) and test.
Upkeep not working – ensure decay.upkeep is true and that tool cupboards are placed correctly. Also check if the server has an economy plugin interfering.
Plugin conflicts – if using Oxide plugins, disable them temporarily to see if one is overriding decay settings.

Frequently Asked Questions

What is the default decay rate?

The default decay.scale is 1.0, meaning structures decay at the standard rate. With upkeep enabled, they only decay when the tool cupboard is empty.

How do I disable decay entirely?

Set decay.upkeep false and decay.scale 0 in server.cfg. This stops all decay, but note that raiding becomes easier as walls never weaken.

Can I set different decay rates for different building materials?

Yes, with advanced commands like building.blockdecay or via plugins. For example, building.blockdecay 0.5 halves decay for all blocks, but per-material requires a plugin.

Does decay affect deployables like workbenches?

Yes, deployables have their own decay timers. You can adjust them with deploy.decay commands, but most servers leave these at defaults.

Will changing decay affect server performance?

Generally no, but setting decay.tick very low (e.g., 1 second) can increase CPU load. Keep it above 60 seconds for optimal performance.

How do I reset decay settings to default?

Remove all decay-related lines from server.cfg or restore a backup. Defaults are: decay.upkeep true, decay.scale 1.0, decay.duration 1440, decay.tick 600.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.