Rust's Livestock Update is live on October 1, 2026. It adds cows and sheep, a Biofuel Generator, and power-grid loot rooms.
For server owners, the immediate work is updating the dedicated build, checking plugins, and deciding how the new progression fits your community.
Update before reopening the server
Run the update as a maintenance window, even if your regular wipe is automated.
- Tell players the downtime and what will reset.
- Run
server.save, wait for the save, then stop normally. - Create a backup of the identity, configs, and plugin data.
- Update the dedicated server and its selected mod framework.
- Wait for
Server startup completein Console. - Join with an updated client and test before announcing the server is open.
On berrybyte, open Settings → Game Settings and check Modding Framework: Vanilla, Oxide, or Carbon. Keep the framework your existing server uses. Starting the server checks for the Rust update and refreshes the selected framework. Watch Console for download failures and plugin errors.
For a self-hosted installation, run SteamCMD against the existing server folder:
./steamcmd.sh +force_install_dir /srv/rust +login anonymous +app_update 258550 +quitReplace /srv/rust with your actual installation directory. Facepunch's
server setup guide
documents the dedicated app and startup checks.
Keep wipe decisions separate from backups
Use your announced map and blueprint policy. A new map and a blueprint reset are different changes; tell players explicitly which you are performing.
Keep server.identity stable so the server continues using the intended
config, owner records, and plugin data. Do not delete the whole identity
folder to perform a map wipe.
Our wipe and update guide covers the save files involved. Keep the pre-update backup even after the new map opens.
Test plugins against the new entities and items
Get the matching framework build from Oxide/uMod or Carbon. Check each important plugin's release notes; a successful framework boot does not prove every plugin works.
Prioritize these tests:
| Plugin type | Check before players return |
|---|---|
| Loot, shops, and kits | New items do not produce missing-item errors or unintended prices |
| NPC, animal, and spawn control | New animals behave as intended under your rules |
| Building and PvE permissions | Livestock enclosures and deployables follow protection rules |
| Progression and monument plugins | Players can use the intended vendors and loot rooms |
| Admin and RCON tools | Owners can connect, run commands, and save |
These are recommended checks, not a claim that those plugins are broken. Start with errors named in Console and isolate one plugin at a time.
Decide how Bandit Camp helicopter access works
The Air Wolf helipad now starts damaged; vehicle sales resume after repairs. Facepunch documents these controls:
| Control | Effect |
|---|---|
vehicle.padrepairsrequired false | Disable the repair requirement |
vehicle.setrepairablepads 0 | Force pads into disrepair |
vehicle.setrepairablepads 1 | Force pads into the repaired state |
Keep the default for a vanilla progression experience. A community that wants
immediate vendor access can deliberately disable the requirement.
Record a persistent policy in server/<identity>/cfg/server.cfg;
the force-state command is an action to test separately.
Check access with an ordinary player account. Admin privileges can hide a permission problem.
Review power-grid settings on quieter servers
Heavy fuses now last four times longer at ten or fewer online players,
scaling back to the previous duration at 100. The relevant controls are
powergrid.fusedecaylowpop, powergrid.fusedecayhighpop, and
powergrid.fusedecaylowpopscale.
Inspect existing overrides before changing anything. Observe whether your community can keep the intended loot routes available under the new defaults. Change one value at a time and record its previous setting.
Monitor more than server FPS
Facepunch budgets NPC work across frames; overloaded animals can react more slowly while FPS remains stable.
Watch dedicated-process memory, CPU, save times, and animal behavior during the first busy session. Compare similar player counts and map conditions. Do not resize a server using a client's graphics-performance report.
If performance deteriorates, keep the startup log, active plugin list, player count, and resource readings. Rust connection fixes and common server issues cover the next checks.
Schedule the October 22 update too
Facepunch also announced a mandatory server and client Halloween update for October 22. Add another maintenance window and confirm its timing from the official announcement before notifying players.
berrybyte Rust hosting includes the dashboard, backups, and framework selection used here. If your update or framework fails to load, open a support ticket with the server linked and the first error from Console.