Skip to main content

Remove a Rust plugin and keep a way to bring it back

Begin by checking what still uses the plugin. Retire the feature and its live code first. Deal with its old settings and player data after you have verified that the rest of the server works.

Find incoming dependencies before you unload it

Check the author’s listing and review the features you use on the server. For example, Image Library is used by Rust Kits and other plugins. Removing one user of the library is different from removing the library while another menu still depends on it.

Plan a stop if the plugin or an accompanying extension needs one. Otherwise unload the plugin with the framework's documented command and put its source outside the plugin folder. An unloaded file left in that folder can load again later.

Archive by ownership

Keep a copy of its exact source file and any settings, player state and translations you may want again. Leave shared files alone. Note the names of plugin-specific grants if you intend to remove them from groups, and review each grant before changing it. A shared group may still serve another plugin.

After the next startup, check that the old plugin is absent and try one feature that used to share a dependency with it. Keep the archive until you are comfortable restoring that setup from scratch.

Sources

Analytics settings

Analytics are off.

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