Updating the plugin

Updating is the same as installing: replace one file and reload.

On Pterodactyl?

If your server runs the CerebRUST edition of the Rust egg, it already downloads the current plugin every time the server starts. Restarting is the update — there is nothing on this page to do unless you turned that off.

The easiest way: let CerebRUST do it

Your server’s Overview tells you when the plugin is out of date, from the version the plugin reported when it last started. If you have connected SFTP on the Integrations page, that notice carries an Update button, and so does the top of the Server config page — which reads the version actually installed on your host and compares it against the published build.

Pressing it writes the new file and nothing else. Oxide notices the change and recompiles on its own within a few seconds — no restart, and your config and token are untouched.

Two things it will not do, on purpose:

• It will not install the plugin for the first time. If there is no Cerebrust.cs in your Oxide folder it says so and stops. Updating something you chose to run is a different thing from putting it there.
• It will not write a file that does not match its published checksum. A half-downloaded plugin does not sit harmlessly on disk — Oxide would fail to compile it and unload the working one. If the check fails, nothing is written at all.

Any admin on the server can press it. Connecting SFTP in the first place is owner-only.

How to update by hand

1. Download the current Cerebrust.cs.
2. Overwrite oxide/plugins/Cerebrust.cs.
3. Run o.reload Cerebrust.
4. Confirm CerebRUST ingest initialized. appears in the console.

Your config is not touched. Your token stays where it is, and your dashboard settings live on CerebRUST rather than in the file, so nothing needs reconfiguring.

When to update

• After a monthly Rust force wipe, once a plugin build for the new game version is out
• When a fix or feature you want is announced

New builds are announced in the #changelog channel of the CerebRUST Discord. That is the place to watch.

Checking your version

The plugin logs its version when it loads:

Loaded plugin CerebRUST v0.17.0 by Ruu Mouat

Since v0.45.0 the plugin also tells CerebRUST its version when it starts, and your servers list shows it — no SFTP and no console needed. When that version is behind the current release, the server’s Overview says so.

Nothing reported yet?

The version is only sent when the plugin loads, so a server that has been running since before you updated shows nothing until its next restart or o.reload. “Not reported” means exactly that — it is not a warning, and a plugin older than v0.45.0 will always show it.

If you have SFTP connected, the Server config page also shows the installed version read straight off your host.

After a monthly Rust update

Rust updates monthly, and every update can change internals that plugins depend on. Two things are worth a minute of your time:

Check furnace boost first

If you run furnace boost, light a furnace and confirm it actually smelts.

That feature replaces Rust’s smelting loop with its own, which makes it the most likely thing to break when Facepunch changes how ovens work. A break is usually silent — furnaces just stop progressing.

Then check the rest of your enabled mods behave: gather rates, turret auth, SAM auth, sort button. Telemetry — the map, chat, players, raids — is far more stable across updates and rarely needs attention.

If an update goes wrong

The previous version keeps working, so the safe move is to keep a copy of the file you are replacing. If a new build misbehaves, restore the old file and o.reload Cerebrust.

Then tell us in Discord — say which version broke, what you saw, and anything in your console. That is how it gets fixed for everyone.