Fix "Failed to load config file (is the config file corrupt?)" in Oxide plugins

Oxide reads the config file with a JSON deserializer before the plugin's config object is created. JSON has no trailing commas, no comments, and requires double quotes around every key and string value. Common triggers: a comma left after the last property, a key or string typed without quotes, a // or /* */ comment pasted in, single quotes, or a value truncated when the file was edited by hand. The message in brackets is the deserializer's own report: Unexpected character encountered while parsing value: } means it found a closing brace where it expected a value, usually because of a trailing comma or an empty value. Path 'Reward amount' tells you which property the parser was reading when it failed. When loading fails, Oxide prints the warning and the plugin continues with its default config, so in-game behavior silently changes.

1. Open oxide/config/<Plugin>.json and go to the line and property named in the error.
2. Remove any trailing comma before } or ], wrap every key and string value in double quotes, and delete comments.
3. Validate the whole file with any JSON validator before saving; one bad character anywhere breaks the entire file.
4. If the file is too damaged, stop the server, delete it, and let the plugin write a fresh one on next load. Do not leave it half-edited.
5. Run oxide.reload <Plugin> and check the console: the Failed to load config file line must be gone and your values must appear in game.
6. Keep a backup copy before editing; a corrupt config is easy to restore from one. If the error persists after saving valid JSON, confirm you edited the file in the correct folder (oxide/config for Oxide, carbon/configs for Carbon) and that the server user can read it.