Rust updates need a maintenance plan that covers the game, plugins, saved data, and player communication. For a community using Space-Node's Rust hosting, confirm the backup and update procedure before maintenance begins, then use the checks below to decide when the server is ready to reopen.
October 2026: Released Update and Next Maintenance Date
The Livestock Update was released on 1 October 2026. It adds cows and sheep, new farming resources, a Biofuel Generator, and Powergrid Lootrooms. For admins, these are useful areas to test alongside economy and custom loot plugins after updating. Facepunch's Livestock announcement contains the release details.
Facepunch also announced a mandatory server and client update for 22 October 2026 at 18:00 BST, which is 19:00 in Europe/Amsterdam. That Halloween update shipped on 22 October, and our Halloween update checklist covers what it changed for servers. The announcement does not specify a wipe, so do not schedule one on that basis. Check the final release notes before changing saved data.
The same announcement extends TPM and Secure Boot requirements to six additional Facepunch servers. It does not introduce a requirement for every community server.
Timeline
1 Week Before
- Read the official release announcement and distinguish a scheduled update from a confirmed wipe.
- Use a separate test server if you want to try staging builds. Keep production saves out of that test.
- List critical plugins, their versions, and the server rules that depend on them.
- Alert your moderator team and assign someone to validate the server before reopening.
2 to 3 Days Before
- Check framework and plugin maintainers' release notes for compatibility information.
- Verify that a recent backup can be downloaded and restored to an isolated test location.
- Record your server identity, branch, build, map settings, startup arguments, and framework version.
- Draft a community announcement with the confirmed date, time zone, and whether a wipe is actually planned.
Update Day
Use the time in the current official announcement. Avoid promising a fixed reopening time before the update and plugin checks are complete.
Phase 1: Confirm the release and secure a backup
- Confirm that the required server build is available and review the release notes.
- Notify players, save the world, and shut the server down cleanly. Prevent scheduled restarts during maintenance.
- Back up the complete server identity directory, configuration, startup settings, and framework and plugin files, including their data. Include external plugin databases if you use them.
- Keep a dated copy outside the files being updated. Verify that it is readable and contains the expected data before proceeding.
Phase 2: Update the server and framework
- Update Rust Dedicated Server through the hosting panel or SteamCMD, using the intended branch. Its Steam app ID is
258550. - If you use Oxide, apply the compatible framework release after the game update and verify that it loads. Facepunch's server setup documentation explains that a SteamCMD update can replace framework files with vanilla files.
- Apply configuration changes deliberately and record them.
- Follow the confirmed wipe requirements for this release and your published server policy. Keep map and blueprint decisions separate. Do not delete the entire identity directory to perform a map wipe.
Phase 3: Validate plugins and saved data
- Check startup logs for framework and plugin errors.
- Test the plugins that enforce permissions, team limits, economy, and other server rules.
- Confirm the intended map, player data, and configuration loaded.
- Connect with an updated client and test joining, spawning, saving, and the gameplay features affected by the patch.
- Keep the server closed if a missing plugin would change your rules or expose player data to unintended changes.
Phase 4: Go live
- Reopen only after the required checks pass.
- Announce the actual server status and any known limitations.
- Monitor logs and player reports, then take a new backup once the updated server is verified.
Post-Update Week
- Check official hotfix notes and relevant plugin releases.
- Investigate repeated errors before changing several settings at once.
- Compare resource use and server behaviour under similar conditions to your recorded baseline.
- Update the community announcement when a known issue is resolved.
Common Update Issues
Oxide or a critical plugin is not ready:
Check the maintainer's current release information. There is no fixed compatibility timetable. If the server relies on plugins for its rules, keep it closed until those dependencies are ready and tested. Opening as vanilla can change gameplay and saved state.
A plugin fails after the update:
Preserve its logs, configuration, and data before making changes. Test the maintainer's fix on an isolated copy where possible. Disabling an optional plugin may be appropriate, but first check whether other plugins depend on it.
The update fails or saved data is wrong:
Stop the server before repeated restarts modify more data. Preserve the failed state and logs separately. If SteamCMD printed state is 0x486 after update job, the update never installed; our SteamCMD 0x486 fix has the retry and validate steps. Identify whether the fault is in the game build, framework, plugin, configuration, or save before choosing a recovery step.
Restore a coherent backup set to a separate location first. Confirm that the target Rust build and plugins can read it, then validate it before restoring production. A backup does not guarantee that an older build can serve clients after a mandatory update. If the old build or save is incompatible, recovery may require the current supported build and a compatible save or maintainer fix. Tell players which save timestamp will be restored and what progress would be lost.
Community Communication
For the announced October maintenance, use the confirmed time and avoid an unsupported wipe claim:
Before the update: "Rust's mandatory Halloween server and client update is scheduled for 22 October at 19:00 Amsterdam time. We will confirm the maintenance window and reopen after our checks. Facepunch's current announcement does not specify a wipe."
During maintenance: "The game update is installed. We are checking the framework, plugins, and saved data. The server remains closed until those checks pass."
After validation: "The server is open. Update your Rust client before joining. Known issues: [list verified issues, or state that none were found in the checks]."
Space-Node Update Process
Before starting maintenance, check which update controls and backup options are available for your server. Confirm the latest backup's timestamp and scope, keep a separate copy, and retain console logs if an update fails. Contact support with the affected build, plugin versions, and relevant errors when you need help identifying the next step.