
Why your Rust plugin settings revert when you reload it
Read the file before editing, right after saving and after the plugin reloads. Note the console events between those reads. That timeline can show whether the edit never reached the active file or whether the plugin wrote a value back.
Capture three snapshots on a test world
Use an easy-to-recognize notice or greeting on an isolated instance. Save the original file. Confirm you are editing the active folder for the framework and that the game's console is open.
- Before the edit, record the file's full location, its current value and the text the player actually sees.
- Apply one edit and reopen that exact file from the host or panel. Note whether the new text remains and whether the console already reports a load after the save.
- Check the file once more after the relevant reload completes and repeat the player action. If the framework already reacted to the save, use that attempt for your timeline.
Match the rewrite to an event
Oxide documents that some plugins write settings while unloading. It also detects changes to watched files.
| Observation | Next action |
|---|---|
| The active file never showed the edit | Check which instance and folder the editor saved to, then confirm the active file again. |
| The edit vanished on unload | On the test world, use Oxide's unload control, wait until the plugin is unloaded, edit the settings and load it again. Do this with players and other tasks isolated during the test. |
| The edit survived unload but changed during load | Check the first configuration warning, the value's type and whether a version migration changed a key. Use the author's expected format. |
| The file kept the edit but the player sees the old copy | Check the loaded version and whether the field controls that action or locale. |
End with the file and player results in agreement
A valid edit in the intended file, a clean load and the matching player response give you a result to keep. If the plugin still rewrites the value, send the three snapshots and first related error to the author with sensitive settings removed.
In disposable tests, Oxide and Carbon reacted to edits on their own. In a separate configuration test, an invalid value produced different load lines across the two frameworks. Check the concrete error and behavior before assuming the same symptom means the same cause.