# What to do when a required Rust plugin is no longer maintained

[Rust server guides](https://rustsc.com/learn/index.html.md) / [Updates](https://rustsc.com/learn/updates/index.html.md)

Start with the features the old plugin enables. A missing update matters more if it owns your economy or protections than if it formats an optional notice. Identify what would fail before you change the live server.

## Draw the shortest dependency list that explains the risk

Check the installed version, the publisher's latest supported release and any pinned compatibility note. A quiet release page alone does not establish that a plugin has been abandoned. If there is a specific break, write the first broken game build and the player action you can reproduce.

List the plugin's required companions and the features that depend on it. Oxide's review guidance distinguishes optional integrations, required runtime features and dependencies that are necessary even to compile. On a private copy, verify which player step fails without the old component. Keep a record of stored data that would need to move.

## Decide one feature at a time

For example, a simple help notice can go away for one wipe. A virtual balance that people earned needs a recovery and player communication decision.

| Choice | When it fits |
| --- | --- |
| Maintain the existing version | The working version still supports your game and someone can own future build and restart checks. Ask the author before adapting code whose terms are unclear. |
| Replace it | A supported component covers the required feature and can handle the state you need. Prove the conversion on a fresh private copy. |
| Retire the feature | Players can do without it or another supported workflow meets the same need. Explain what stays, what ends and when. |

## Keep the fallback at the failing feature

Test the new choice against the same ordinary-player action as the old version. If it changes data, practice going back with the matching old files before releasing. If a critical protection still has no supported replacement, keep that ruleset closed rather than promise a safeguard you cannot demonstrate.

## Sources

- [Oxide requirements for plugin dependencies](https://docs.oxidemod.com/guides/reviewers/guidelines/dependencies)
- [Google SRE Workbook on limiting rollout risk](https://sre.google/workbook/canarying-releases/)

## Related resources

- [Track Rust plugin versions across marketplaces](https://rustsc.com/learn/updates/rust-plugin-version-register/index.html.md)
- [Remove a Rust plugin and keep a way to bring it back](https://rustsc.com/learn/updates/remove-rust-plugin-without-losing-data/index.html.md)
- [Roll back a plugin update that changed its data files](https://rustsc.com/learn/updates/rollback-plugin-update-with-data-conversion/index.html.md)

---

HTML version: https://rustsc.com/learn/updates/when-a-required-rust-plugin-is-no-longer-maintained/
