Skip to main content

Which Rust plugin updates belong on force-wipe day?

Prepare the game and its compatible framework first. Then decide which plugin changes the world needs in order to reopen. Keep unrelated enhancements for another window so a new gameplay problem has fewer possible causes.

Give each change a reason to be in the window

Take the version you have running and the version you would install. Read the release notes and the dependency list for each. Decide before wipe day what you can hold.

Give each change a reason to be in the window
What changedDecision
A fix for a required plugin that fails on the new buildRehearse the supported release with the new game and framework. Check the essential player action and its dependents.
Optional feature added to a plugin that still works on the new buildKeep the version that passed your checks. Test the optional feature in another window.
A plugin needs a dependency whose compatible build is unavailableHold the dependant change. If it owns a protection you promised players, keep the world closed until that protection passes.
An update will convert stored progressGive it a separate recovery decision. Save the matched files before conversion and rehearse the return on a spare world.

Test the break that matters

For example, a PvE world needs its advertised building protection before it can reopen. On the test copy, have two ordinary accounts repeat the existing protection check on the new build. Record the running framework and plugin versions and the observed result. Treat untested protection as unavailable when deciding whether to reopen.

Do not assume a plugin rollback makes the previous Rust build compatible with current clients. The first recovery choice may be to keep the updated world closed while a compatible plugin is prepared. Put the opening decision and its reason in the staff handoff.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details