Debugging In Control Rules That Do Not Seem to Work

Most In Control problems come from a rule that loads but never matches, or a rule that matches too broadly. Here is how to narrow it down.

Check the log first

In Control writes to the game log when it loads rules and when it rejects a rule. Open the log and search for the mod name. A malformed JSON file will usually produce a parse error with a line number — fix that before anything else. If the file loads cleanly but nothing changes, the issue is in the filters, not the syntax.

Isolate the rule

Temporarily replace your rule set with a single rule that denies one common mob in the dimension you are testing. If that works, your file is loading and the problem is in the original filters. Add filters back one at a time until the rule stops working — the last filter you added is the culprit. Common offenders are biome or dimension names that do not match the registry, coordinates in the wrong order, and rules placed after a catch-all deny that already matched. Keep a backup of a working config so you can revert quickly.