If a plugin stops loading after a configuration edit, inspect the console error first. Rust Admin gives you browser access to files and the console to investigate the change.
Check the configuration
Oxide configs normally live in oxide/config/. Preserve the original contents before editing. This example demonstrates JSON syntax, not settings for a particular plugin:
{
"Enabled": true,
"Message": "Welcome!"
}Use your plugin's documented field names. Also check value types: the boolean true and the string "true" differ.
Apply and test
Validate locally, save and follow the plugin author's reload procedure. A common command is oxide.reload MyPlugin. Check new console lines and test the feature in the game.
If your changes disappear
Some plugins save settings on unload, requiring an unload → edit → load sequence. See the Oxide configuration guide. If syntax is valid but the feature still fails, check version-specific documentation, permissions and dependencies. Fix the smallest relevant change rather than deleting the entire configuration.
See the workflow in Rust Admin
The interface demonstration below uses sample data to illustrate the section. These are not measurements from your server.
Connect Rust Admin to edit available files and check the result in the console. Sign in with Steam · View plans
