Since the Rust update Breach and Clear from September 3, 2026, a base's upkeep costs also depend on its detected group size. For server operators, this means: check the displayed costs, the permissions, and your own decay settings before you correct a supposed bug in the Tool Cupboard with plugins or blanket multipliers.
How the Additional Upkeep Comes About
Facepunch takes into account TC permissions as well as code lock access, including guest access. Recently removed permissions still count for up to 24 hours. The first four players don't cause a group surcharge, the next six each add two percentage points, and additional players each add four percentage points. The surcharge is capped at 300 percent.
| Detected Players | Additional Upkeep |
|---|---|
| 4 | 0 % |
| 6 | 4 % |
| 10 | 12 % |
| 12 | 20 % |
The table only calculates the group surcharge according to these rules. It is not a complete material cost table for a specific base. You can see the surcharge actually applied in the open TC by hovering over the upkeep costs.
Checking Permissions Transparently
If you get a question about this, first create a small before-and-after comparison: the same base, the same server build, and the same settings. Note the displayed surcharge, TC authorizations, and relevant lock access. Then check whether any access was removed in the past 24 hours. An immediate comparison right after removal can otherwise create the false impression that the change has no effect.
Don't put access codes in public bug reports. For diagnosis, the number and type of access along with the time of the change are enough. A group should maintain its permissions according to actual gameplay needs; briefly toggling access back and forth doesn't provide a clean test.
Reconciling Your Own Server Rules and Plugins
Facepunch lists adjustable ConVars in the Decay class, including an option to disable it. Check the parameters actually available in your build and document any deviation from the default. Don't adopt guessed keys from older guides.
- Back up the configuration and the working plugin state.
- Note all extensions that manage decay, building costs, TCs, or groups.
- First compare the default behavior with the same base on a test copy.
- Then enable exactly one of your own rules or extensions and repeat the comparison.
- Adopt the verified setting and describe it clearly in your server rules.
Multiple simultaneous multipliers make diagnosis harder. So don't change group settings, plugin configuration, and base layout all at the same time.
What Additionally Counts Since the August Update
Power Trip introduced a fixed upkeep of 20 percent for high exterior walls. This difference and the new group surcharge can coincide on the same base. Treat them as separate factors and compare the actually displayed material costs before reporting a bug.
Frequently Asked Questions
Why doesn't the surcharge drop immediately after removing a player?
Recently revoked TC and lock permissions can still be counted for up to 24 hours. Check this time window as well as any remaining access.
Do I need to wipe the world for this?
A changed upkeep value alone doesn't justify an additional manual wipe. First clarify build, permissions, and configuration; a wipe doesn't replace this diagnosis.
Can a plugin change the displayed costs?
Check this for the extension actually in use. Compare its documented effect with a test without that extension before attributing the result to the base software.