Skip to main content

​
Symptoms

You changed a value in one of the product’s configs/*.jsonc files, and nothing changed in game. The console may show nothing at all.

​
Causes

In order of how often they are the answer:
  1. The resource was not restarted. Settings are read when it starts.
  2. The file has a syntax error. The whole file is then ignored and every setting in it goes back to the shipped value. The console says so once, among the start-up lines.
  3. The key name does not match. A misspelled key, a key in the wrong place in the nesting, or a key a newer release renamed, is ignored without a message.
  4. An update replaced the file. An update replaces the whole folder, configs included.
  5. The value has the wrong type, such as "50" where 50 belongs. Values are not checked, so it gives wrong behaviour instead of an error.
  6. The setting is in the wrong file. Each file holds only the settings of its own area.

​
Fix

1

Restart the resource

If the change now shows, that was it.
2

Look for a configuration warning

That line means the file was ignored. Look for a comma after the last value, a missing bracket or quote, or a missing comma between two values. Comments (// and /* */) are allowed and are not the problem.
3

Compare the key with the product's page

Open the product’s configuration page for that file and compare the key, character by character, including where it sits in the nesting. Check the patch notes for a rename if it worked before an update.
4

Narrow it down

Put back the file the release shipped, then add your changes back one at a time, restarting after each. The first one that does not take effect is the one to look at. A file holding a single key is complete and valid.

​
Check that it worked

Restart the resource and confirm both:
  • no Config file for "…" missing or invalid line in the console;
  • the change is visible in game.
The in-game check is the one that proves it. A misspelled key gives a clean console. How configuration files work is in How configuration works.