In Control Mod FAQ

Create or edit the JSON rule files in the mod's config folder, then reload them in-game with the reload command. Each rule defines a set of conditions and the spawn behavior to apply when those conditions match.

Spawn rules decide whether a mob is allowed to spawn at all under given conditions, while filters narrow down which mobs, biomes, dimensions, or blocks a rule applies to. You typically combine both: a filter selects the mobs, and the rule sets the outcome.

No, you can reload the rule files with the mod's reload command while the game is running. A full restart is only needed if you changed something outside the rule files themselves.

The most common causes are a JSON syntax error, a rule that never matches its conditions, or another mod overriding spawns after In Control runs. Check the log for parse errors and use the debug output to see which rules are being evaluated.

Yes, you can write a rule that matches a biome, dimension, or block-based condition and denies spawning there. Combine it with a filter for the mobs you want to block so other mobs still spawn normally.

Use a biome condition in your rule and set the spawn action to allow only when that condition matches. Mobs not covered by any allowing rule will fall back to vanilla spawning unless you also block them.

It can, but conflicts happen when two mods both try to control the same spawn event. If spawns behave unexpectedly, test with only In Control enabled to confirm your rules work, then add other mods back one at a time.

Rule evaluation is lightweight, but very large numbers of rules or complex conditions can add overhead during spawn attempts. Keep rules specific and avoid redundant entries that all match the same situation.

Write a rule that matches that mob and denies its spawn, without narrowing it to a biome or dimension. This effectively removes it from the spawn list while leaving other mobs untouched.

Yes, as long as the mob has a registered ID you can reference it in your filters the same way as vanilla mobs. Check the mod's registry name if the spawn rule doesn't seem to match.

In Control is a rule-based mod that gives you full control over where mobs are allowed to spawn. You define rules using configurable conditions and filters.

You write rules in the rule files located in config/incontrol. The rules let you block or add mob spawns, and alter mob properties, loot, and experience.

There are five rule files: spawn.json, summonaid.json, loot.json, experience.json, and potentialspawn.json (1.12 only) or spawner.json (1.16 or later).

The rule files are located in config/incontrol.

Spawn.json lets you block spawning of certain creatures under certain conditions, and when a spawn is allowed you can alter properties of the mob like maximum health.

Loot.json lets you control the loot that mobs drop when they are killed based on various criteria.

Experience.json controls how much experience you get from killing mobs based on various criteria.

Summonaid.json is structured the same as spawn.json but is only used when zombies are summoned for aid.

Supported criteria include weather, time of day, biome temperature category, light level, minimum and maximum height, distance to spawn, local difficulty, and mob counts.

Yes, one of the rule files allows you to add new spawns to the world, such as adding blazes to the overworld.