Plugin config validator
Paste an Oxide or Carbon plugin config. See the exact line and column of any JSON error, fix trailing commas and comments in one click, and pretty print it before you reload the plugin.
Everything runs in your browser. Your config is never uploaded.
Why plugin configs break
Oxide and Carbon plugins keep their settings in a JSON file, oxide/config/PluginName.json (Carbon: carbon/configs/PluginName.json). JSON is strict: one missing comma or an extra one stops the whole file from loading.
When that happens the console shows something like "Failed to load config file (is the config file corrupt?)". Many plugins then fall back to default values, and some overwrite your file with the defaults the next time they save. Validate before you reload, and keep a copy of your edits.
The mistakes this catches
- Trailing commas after the last item in an object or list.
- Missing commas between two settings, usually at the end of the line before the error.
- Comments (
//or/* */): JSON has no comments. - Single quotes instead of double quotes, and unquoted property names.
- True/False with a capital letter, and Windows paths with single backslashes.
After fixing
Save the file and reload the plugin from the console: oxide.reload PluginName (Carbon: c.reload PluginName). Check the console for a "Loaded plugin" line.
FAQ
Is my config sent anywhere?
No. The validator runs entirely in your browser. Nothing you paste is uploaded or stored.
Why did my plugin reset its config to defaults?
Most plugins catch a broken config, log a warning and load defaults. If the plugin saves afterwards, your file is replaced. Fix the JSON, then reload the plugin before it saves again.
What indentation do Oxide configs use?
Oxide writes configs with two-space indentation. The Format button uses the same style, so diffs against the original stay small.