
When should you update a Rust server extension by itself?
An extension can provide shared code for several Rust plugins. Give it its own maintenance window when it can change separately from the game or framework. Use a private restart to test every player or staff feature that depends on it.
Find out what has to change together
Read the extension's version support and installation notes. Oxide describes extension DLLs and recommends stopping the server for a replacement unless the extension explicitly supports another method. Check the extension's own dependencies, and list the plugins that use it. Keep the current extension package and relevant settings available.
Choose the window from the compatibility notes
Keep a version sheet for the game, framework, extension and affected plugins.
| Release says | Decision |
|---|---|
| The new extension supports the same game and framework | Rehearse replacing just the extension in a maintenance window. Keep other versions fixed. |
| The extension is required for a new game or framework build | Rehearse the documented compatible set together. Do not mix unsupported versions to discover which will load. |
| A required dependent has no compatible version | Hold the change or keep the affected feature unavailable until a supported setup passes. |
Check more than the loaded extension name
On a spare host, follow the author's stopped-server replacement procedure and start fresh. Read the extension and plugin load results. Repeat one real action from each affected plugin using test accounts and data. Practice returning to the known working versions on that spare host, then repeat the same actions. Set the live maintenance window only when the tested change and recovery both pass.