server.stability (Rust server ConVar)
server.stability turns Rust's building stability simulation on or off. What the server says it does, the stability.* settings, and where to persist it.
Last updated Verified on Rust build 25582902, 2026-09-28
- Kind
- Variable
- Value on build 25582902
True- Server help text
- (Generated) Enables structural stability simulation; when disabled buildings will not collapse even if their supports are destroyed
- Applies
- Immediately (runtime)
- Persists in
- server.cfg
- Vanilla Rust
- Yes, native
- Example
server.stability 1
Gotchas
- Reads back as True or False; Panelra writes it as 1 in server.cfg and the server accepts that.
- Panelra's generated server.cfg always writes server.stability 1. To turn it off, add it under Custom ConVars, which are written later in the same file.
- server.writecfg does not save it: our test server's serverauto.cfg has no line for it. Keep it in server.cfg.
server.stability switches the building stability simulation, the system that makes unsupported building blocks fall. The server's help text on build 25582902: "(Generated) Enables structural stability simulation; when disabled buildings will not collapse even if their supports are destroyed".
It reads True on our test server, which sets it with server.stability 1 in server.cfg. 1 works in the file, as that line shows, and the server reads it back as True or False.
What turning it off means
Going by the help text, with stability off, destroying the supports under a structure no longer brings down what stands on them. Leave it on unless you run a mode that needs it off. We have not switched it off on a live server, so try the effect on a staging server first.
Setting and keeping it
In server.cfg, or over RCON:
server.stability 1
server.writecfg does not save it: our test server's serverauto.cfg has no line for it. Put the value in server.cfg so it survives restarts and is not undone by the next server.readcfg.
The stability.* settings
The simulation itself is tuned by the stability namespace. Values and help text on our server:
| ConVar | Value | Help text (shortened) |
|---|---|---|
stability.collapse | 0.05 | Stability value below which a building block is considered unsupported and will collapse |
stability.strikes | 10 | Number of stability propagation iterations performed per tick |
stability.refresh_stability | command | Forces an immediate recalculation of stability for all building blocks in the world; expensive on large bases |
At startup the server logs a line such as Initializing 975 stability supports; the number on our test server varied between 932 and 1035 across restarts.
In Panelra
Panelra's generated server.cfg always contains server.stability 1. To change it, add server.stability under Custom ConVars. Custom ConVars are sent to the running server and written further down in the same server.cfg, and lines in the file run in order, so your value is the one that sticks.
Set it in Panelra
Change server.stability from the dashboard instead of editing files over SSH.
Related ConVars
- stability.collapse(Generated) Stability value below which a building block is considered unsupported and will collapse; default 0.05 means blocks below 5% support fall
- stability.refresh_stability(Generated) Forces an immediate recalculation of stability for all building blocks in the world; expensive on large bases
- stability.strikes(Generated) Number of stability propagation iterations performed per tick; higher values resolve complex multi-block stability chains faster at the cost of CPU time
Skip the manual work: install the Panelra agent
Wipes, updates, restarts, plugins and crash alerts for your Rust servers, from one dashboard. One install command on your Linux host, no inbound ports for the agent.
Free during the open beta. Pricing will be announced before the beta ends.