
How to put Oxide back after a Rust update
If all your plugins disappear together after the game updates, first check whether the server is still running Oxide. In the server console, run oxide.version. If it returns a version, investigate the plugins that failed before replacing the framework.
Pick the release for the host and the game update
Read the Oxide.Rust release notes against the Rust update or hotfix you installed. A release for the monthly update can precede a separate hotfix. If the matching build is still pending, keep the planned downtime or run vanilla only if you have checked what the missing plugins would mean for your players.
Use the Windows ZIP for a Windows host or the Linux ZIP for a Linux host. In a rental panel with an Oxide installer, use the host's matching install option.
Keep the existing installation and world
Stop the server and save a copy of the Oxide folder and your server data. Extract the framework archive separately, then copy its contents into the existing game root, keeping the archive's folder structure. If you see a new nested server directory alongside RustDedicated, check where you extracted it before starting up.
Start with the usual launch settings. Check oxide.version again, then repeat one real player action from an essential plugin. That catches the case where the framework is back and one plugin still needs its own update.