Screenshot 1 of 1. MinecraftHub-generated editorial cover for In Control!, a voxel diorama around the lime MinecraftHub block
What In Control! works with.
| Platform | Java Edition |
|---|---|
| Loaders | NeoForge, Forge |
| Minecraft versions | 1.10.2, 1.11.2, 1.12.2, 1.15.2, 1.16.5, 1.18.2, 1.19.3, 1.20.1, 1.21.1 |
| Environment | Server |
In Control! is a rule-based mod that decides where mobs may spawn, and it runs on NeoForge and Forge. It is server-side only, and the player's own install does not support it. Anyone searching for the in control mod usually wants spawn blocking, but the same rule system also covers loot and experience.
Loaders and versions
- NeoForge: Minecraft 1.21 to 1.21.1. The newest build needs no dependencies, optionally The Lost Cities.
- Forge: Minecraft 1.10.2 to 1.20.1. The newest build needs no dependencies, optionally The Lost Cities.
What the rules control
Every rule lives in a JSON file inside `config/incontrol`. The files split the work by job:
- `spawn.json` blocks spawning under certain conditions. When a spawn is allowed, it can also change mob properties such as maximum health.
- `summonaid.json` is structured like `spawn.json` but applies only when zombies are summoned for aid.
- `potentialspawn.json` removes and adds spawn rules (1.12 only).
- `spawner.json` adds spawn rules (1.16 or later).
- `loot.json` controls what mobs drop when killed, based on various criteria.
- `experience.json` controls how much experience a kill gives.
In the 1.12 setup, rules in `potentialspawn.json` are used before the rules in `spawn.json`, so make sure any new mob you add there is also allowed in `spawn.json`.
Installation
- 1.Set up the matching loader for your release, following the Forge and NeoForge install guide.
- 2.Place the mod file in the `mods` folder on the server. The newest builds need no other mod.
- 3.Edit the rule files in `config/incontrol`. More in-depth documentation is on the In Control! wiki.
Fx Control! is listed as the companion mod. In Control! may be used freely in any modpack. For general steps on mod files and folders, see the Java mod install guide.
Questions about In Control!.
4 questions
How do I use the In Control mod?
Install it on the server with a matching Forge or NeoForge setup, then edit the JSON rule files in config/incontrol. Each file handles one job: spawn.json blocks or adjusts spawns, loot.json changes drops, and experience.json changes experience rewards.
Does In Control need to be installed on players' own installs?
No. The mod is required on the server, and the player's own install is marked unsupported, so it belongs in the server's mods folder only. Players joining that server do not add it to their own setup. Pair it with a matching Forge or NeoForge loader on the server.
Which loaders does In Control support?
It has builds for NeoForge and Forge. NeoForge covers Minecraft 1.21 to 1.21.1, and Forge covers 1.10.2 to 1.20.1. There is no Fabric or Quilt build listed. The newest builds need no required dependency, with The Lost Cities as an optional extra.
Can I use In Control in a modpack?
Yes. The creator states that the mod can be freely used in any modpack, and the source repository carries an MIT License file. Remember that it still needs to run on the server of the pack and not on the player's side.
