ВЕРСИИ (228)

## InControl 26.3-12.0.0-fabric - Port to Minecraft 26.3 with Fabric

## InControl 26.3-12.0.0 - Port to 26.3/NeoForge

## InControl 26.2-11.0.0-fabric - Port to Minecraft 26.2 with Fabric and Java 25 - Migrate existing phases, numbers, and day counters to the new saved-data format

## InControl 26.2-11.0.0 - Port to 26.2/NeoForge

## InControl 1.21.1-10.3.0-fabric - Port to fabric

## InControl 1.21-10.3.0 - Added KubeJS server persistent-data conditions when KubeJS is installed

## InControl 1.20-9.5.0 - Added KubeJS server persistent-data conditions when KubeJS is installed

## InControl 1.21-10.2.7 - Fixed tfc items not being recognized because they contain a '/'

## InControl 1.20-9.4.7 - Fixed tfc items not being recognized because they contain a '/'

<h2>InControl 1.21-10.2.6</h2><br/>&nbsp;&nbsp;&nbsp;- Small bugfix when checking things based on nearest player<br/>&nbsp;&nbsp;&nbsp;- Small bugfix in the 'number' test. It would crash the game if there was a wrong expression<br/>

<h2>InControl 1.20-9.4.6</h2><br/>&nbsp;&nbsp;&nbsp;- Small bugfix in the 'number' test. It would crash the game if there was a wrong expression<br/>

<h2>InControl 1.21-10.2.5</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a problem with spawning NPC mobs<br/>&nbsp;&nbsp;&nbsp;- 'mindist' and 'maxdist' are now also supported for spawn.json. They will use the position to the closest player<br/>

<h2>InControl 1.20-9.4.5</h2><br/>&nbsp;&nbsp;&nbsp;- Small bugfix<br/>

<h2>InControl 1.20-9.4.4</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a problem with spawning NPC mobs<br/>&nbsp;&nbsp;&nbsp;- 'mindist' and 'maxdist' are now also supported for spawn.json. They will use the position to the closest player<br/>

<h2>InControl 1.20-9.4.3</h2><br/>&nbsp;&nbsp;&nbsp;- TqLxQuanZ fixed a problem with customnpcs stopping spawning after spawning a few<br/>

<h2>InControl 1.21-10.2.4</h2><br/>&nbsp;&nbsp;&nbsp;- TqLxQuanZ fixed a problem with customnpcs stopping spawning after spawning a few<br/>

<h2>InControl 1.21-10.2.3</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed another problem with loot<br/>

<h2>InControl 1.20-9.4.2</h2><br/>&nbsp;&nbsp;&nbsp;- Changed the 'ai' system. Removed 'cleargoals' and 'cleartargets' and made them part of the goal/target array by using "removeall" there<br/>

<h2>InControl 1.21-10.2.2</h2><br/>&nbsp;&nbsp;&nbsp;- Changed the 'ai' system. Removed 'cleargoals' and 'cleartargets' and made them part of the goal/target array by using "removeall" there<br/>

<h2>InControl 1.21-10.2.1</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed loot handling again. It was still broken<br/>

<h2>InControl 1.21-10.2.0</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed loot handling. It was 100% broken before<br/>&nbsp;&nbsp;&nbsp;- Removed summonaid.json. It's obsolete since you can now test for spawntype<br/>&nbsp;&nbsp;&nbsp;- New 'ai' command for spawn.json to change the ai of mobs. This is currently still experimental<br/>&nbsp;&nbsp;&nbsp;- Attempt to make parsing spawner.json more robust on foreign language systems<br/>&nbsp;&nbsp;&nbsp;- Thanks to Goodbird from CustomNPCs InControl now has support for CustomNPCs. You can use the 'npc' condition to test for NPCs and you can spawn npbs with spawner.json or events.json<br/>&nbsp;&nbsp;&nbsp;- New 'minlight_sky' and 'maxlight_sky' keywords to specifically test for skylight<br/>&nbsp;&nbsp;&nbsp;- Also added 'minlight_sky' and 'maxlight_sky' to the spawner 'and' and 'not' blocks<br/>&nbsp;&nbsp;&nbsp;- Added new vertical 'cylinder' type for areas. x and z are the horizonal circumference and y is height<br/>&nbsp;&nbsp;&nbsp;- The 'mob' keyword for spawn.json now also understands mob tag id's (starting with '#')<br/>&nbsp;&nbsp;&nbsp;- New 'blocktest' keyword which adds a much more flexible way to test for blocks above or under the spawn position<br/>&nbsp;&nbsp;&nbsp;- The 'incontrol info' command now also shows the block light, sky light and full light at the player position. In addition it shows the current day time and day count<br/>

<h2>InControl 1.21-10.1.4</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a problem with the 'mobsfrombiome' action in spawner<br/>

<h2>InControl 1.20-9.4.1</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed the 'npc' keyword in spawn.json. It was broken<br/>

<h2>InControl 1.20-9.4.0</h2><br/>&nbsp;&nbsp;&nbsp;- New 'ai' command for spawn.json to change the ai of mobs. This is currently still experimental<br/>&nbsp;&nbsp;&nbsp;- Attempt to make parsing spawner.json more robust on foreign language systems<br/>&nbsp;&nbsp;&nbsp;- Thanks to Goodbird from CustomNPCs InControl now has support for CustomNPCs. You can use the 'npc' condition to test for NPCs and you can spawn npbs with spawner.json or events.json<br/>&nbsp;&nbsp;&nbsp;- New 'minlight_sky' and 'maxlight_sky' keywords to specifically test for skylight<br/>&nbsp;&nbsp;&nbsp;- Also added 'minlight_sky' and 'maxlight_sky' to the spawner 'and' and 'not' blocks<br/>&nbsp;&nbsp;&nbsp;- Added new vertical 'cylinder' type for areas. x and z are the horizonal circumference and y is height<br/>&nbsp;&nbsp;&nbsp;- The 'mob' keyword for spawn.json now also understands mob tag id's (starting with '#')<br/>&nbsp;&nbsp;&nbsp;- New 'blocktest' keyword which adds a much more flexible way to test for blocks above or under the spawn position<br/>&nbsp;&nbsp;&nbsp;- The 'incontrol info' command now also shows the block light, sky light and full light at the player position. In addition it shows the current day time and day count<br/>

<h2>InControl 1.21-10.1.3</h2><br/>&nbsp;&nbsp;&nbsp;- New 'command' action for events. This is a json array of commands that will be executed when the event happens<br/>

<h2>InControl 1.20-9.3.3</h2><br/>&nbsp;&nbsp;&nbsp;- New 'command' action for events. This is a json array of commands that will be executed when the event happens<br/>

<h2>InControl 1.20-9.3.2</h2><br/>&nbsp;&nbsp;&nbsp;- The biometags test wasn't working in spawner.json<br/>

<h2>InControl 1.21-10.1.2</h2><br/>&nbsp;&nbsp;&nbsp;- The biometags test wasn't working in spawner.json<br/>

Hotfix: fixed problem with spawner.json

Hotfix: fixed a bug with spawner.json

<h2>InControl 1.21-10.1.0</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed the 'area' sphere test. It was incorrect<br/>&nbsp;&nbsp;&nbsp;- Much improved caching for counting. This has a great effect on performance<br/>&nbsp;&nbsp;&nbsp;- New server config file where you can control this counting cache as well as change the radius used for nearest player tests<br/>&nbsp;&nbsp;&nbsp;- TqLxQuanZ added knockbackset/multiply/add as well as knockbackresistanceset/multiply/add<br/>&nbsp;&nbsp;&nbsp;- The spawner system (spawner.json) now supports many new conditions to improve performance and make rules easier to write (avoid the need for spawn.json rules). These conditions are encapsulated in a new 'and' block. There is also a 'not' block for negative conditions<br/>&nbsp;&nbsp;&nbsp;- New 'spawntype' condition for spawn.json. This will allow you to test what type of spawn it is. Possible values are 'spawn_egg', 'natural', 'chunk_generation', 'structure', 'mob_summoned', 'conversion', ...<br/>&nbsp;&nbsp;&nbsp;- New 'potionnoparticles' action for effects.json. This will allow you to do potion effects without particles<br/>

<h2>InControl 1.20-9.3.0</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed the 'area' sphere test. It was incorrect<br/>&nbsp;&nbsp;&nbsp;- Much improved caching for counting. This has a great effect on performance<br/>&nbsp;&nbsp;&nbsp;- New server config file where you can control this counting cache as well as change the radius used for nearest player tests<br/>&nbsp;&nbsp;&nbsp;- TqLxQuanZ added knockbackset/multiply/add as well as knockbackresistanceset/multiply/add<br/>&nbsp;&nbsp;&nbsp;- The spawner system (spawner.json) now supports many new conditions to improve performance and make rules easier to write (avoid the need for spawn.json rules). These conditions are encapsulated in a new 'and' block. There is also a 'not' block for negative conditions<br/>&nbsp;&nbsp;&nbsp;- New 'spawntype' condition for spawn.json. This will allow you to test what type of spawn it is. Possible values are 'spawn_egg', 'natural', 'chunk_generation', 'structure', 'mob_summoned', 'conversion', ...<br/>&nbsp;&nbsp;&nbsp;- New 'potionnoparticles' action for effects.json. This will allow you to do potion effects without particles<br/>

<h2>InControl 1.21-10.0.5</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a bug in minverticaldist/maxverticaldist<br/>

<h2>InControl 1.20-9.2.11</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a bug in minverticaldist/maxverticaldist<br/>

<h2>InControl 1.21-10.0.4</h2><br/>&nbsp;&nbsp;&nbsp;- The 'phase' command now actually supports multiple phases now<br/>&nbsp;&nbsp;&nbsp;- The 'eventspawn' condition will now also work correctly even with "when": "onjoin"<br/>

<h2>InControl 1.20-9.2.10</h2><br/>&nbsp;&nbsp;&nbsp;- The 'phase' command now actually supports multiple phases now<br/>&nbsp;&nbsp;&nbsp;- The 'eventspawn' condition will now also work correctly even with "when": "onjoin"<br/>

<h2>InControl 1.21-10.0.3</h2><br/>&nbsp;&nbsp;&nbsp;- The 'command' action now supports a list of commands<br/>

<h2>InControl 1.20-9.2.9</h2><br/>&nbsp;&nbsp;&nbsp;- The 'command' action now supports a list of commands<br/>

<h2>InControl 1.19-7.1.18</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a problem with the block test sometimes crashing<br/>

<h2>InControl 1.20-9.2.8</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a problem with the block test sometimes crashing<br/>

<h2>InControl 1.21-10.0.2</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a problem with the block test sometimes crashing<br/>

<h2>InControl 1.19-7.1.17</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a problem with "onjoin" rules where the "incontrol" tag would not work properly<br/>

<h2>InControl 1.21-10.0.1</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a problem with "onjoin" rules where the "incontrol" tag would not work properly<br/>&nbsp;&nbsp;&nbsp;- Added two new keywords: "inmultibuilding" and "multibuilding" that work similar to the "inbuilding" and "building" keywords but for multi buildings (Lost Cities)<br/>&nbsp;&nbsp;&nbsp;- Some fixes<br/>

<h2>InControl 1.20-9.2.7</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a problem with "onjoin" rules where the "incontrol" tag would not work properly<br/>&nbsp;&nbsp;&nbsp;- Added two new keywords: "inmultibuilding" and "multibuilding" that work similar to the "inbuilding" and "building" keywords but for multi buildings (Lost Cities)<br/>

<h2>InControl 1.18-6.1.14</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a problem with "onjoin" rules where the "incontrol" tag would not work properly<br/>

<h2>InControl 1.19-7.1.16</h2><br/>&nbsp;&nbsp;&nbsp;- 'hasstructure' and 'structuretags' now actually work<br/>

<h2>InControl 1.21-10.0.0</h2><br/>&nbsp;&nbsp;&nbsp;- First version for 1.21<br/>

<h2>InControl 1.19-7.1.15</h2><br/>&nbsp;&nbsp;&nbsp;- The 'structure' test now supports lists<br/>&nbsp;&nbsp;&nbsp;- New 'hasstructure' boolean test<br/>&nbsp;&nbsp;&nbsp;- New' structuretags' test to test for structure tags<br/>

<h2>InControl 1.20-9.2.6</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a problem with the 'hasstructure' test<br/>

<h2>InControl 1.20-9.2.5</h2><br/>&nbsp;&nbsp;&nbsp;- New 'hasstructure' boolean test to test if the current position has any structure<br/>&nbsp;&nbsp;&nbsp;- New 'cave' test that tries to see if the position is in a cave<br/>&nbsp;&nbsp;&nbsp;- The 'mod' test in item filters was not working at all<br/>&nbsp;&nbsp;&nbsp;- Item filters have improved. It's now possible to not have to specify the item but instead match on tag or mod only<br/>&nbsp;&nbsp;&nbsp;- New 'armorset', 'armormultiply', 'armoradd', 'followrangeset', 'followrangemultiply', and 'followrangeadd' actions to change the armor and follow range of mobs<br/>&nbsp;&nbsp;&nbsp;- New 'attackspeedset', 'attackspeedmultiply', 'attackspeedadd', 'armortoughnessset', 'armortoughnessmultiply', and 'armortoughnessadd' actions to change the attack speed and armor toughness of mobs<br/>&nbsp;&nbsp;&nbsp;- All actions that modify attributes will now work properly if spread out in multiple rules<br/>

<h2>InControl 1.19-7.1.14</h2><br/>&nbsp;&nbsp;&nbsp;- New 'armorset', 'armormultiply', 'armoradd', 'followrangeset', 'followrangemultiply', and 'followrangeadd' actions to change the armor and follow range of mobs<br/>&nbsp;&nbsp;&nbsp;- New 'attackspeedset', 'attackspeedmultiply', 'attackspeedadd', 'armortoughnessset', 'armortoughnessmultiply', and 'armortoughnessadd' actions to change the attack speed and armor toughness of mobs<br/>&nbsp;&nbsp;&nbsp;- All actions that modify attributes will now work properly if spread out in multiple rules<br/>

**1.18-6.1.13:** - New 'armorset', 'armormultiply', 'armoradd', 'followrangeset', 'followrangemultiply', and 'followrangeadd' actions to change the armor and follow range of mobs - New 'attackspeedset', 'attackspeedmultiply', 'attackspeedadd', 'armortoughnessset', 'armortoughnessmultiply', and 'armortoughnessadd' actions to change the attack speed and armor toughness of mobs - All actions that modify attributes will now work properly if spread out in multiple rules

<h2>InControl 1.19-7.1.13</h2><br/>&nbsp;&nbsp;&nbsp;- The remove gamestage action did actually8 add the stage instead of removing it<br/>

<h2>InControl 1.20-9.2.4</h2><br/>&nbsp;&nbsp;&nbsp;- The remove gamestage action did actually add the stage instead of removing it<br/>

<h2>InControl 1.20-9.2.3</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed race condition in the event system<br/>

<h2>InControl 1.20-9.2.2</h2><br/>&nbsp;&nbsp;&nbsp;- The 'structures' test now supports lists<br/>&nbsp;&nbsp;&nbsp;- New 'structuretags' test to support a (list of) structure tags<br/>

<h2>InControl 1.20-9.2.1</h2><br/>&nbsp;&nbsp;&nbsp;- Fix with position checks. They would crash if you used deny<br/>

**1.20-9.2.0:** - New named number system where you have variables with a name and an integer value: - Two new commands: 'numbers' to show the current numbers and 'setnumber' to set a number - New 'number' test that can be used in almost all rules to test if a number satisfies a given expression. Example expression: "number": { "name": "mycounter", "expression": "gt(10)" } - This test also works for events and spawner rules. Basically everwhere that you can test for a phase you can now also test for a number - New event action called 'number'. This will allow you to modify a number when an event happens. For example: { "name": "mycounter", "value": "+1" } - New 'changenumber' action that can be used in many rules. Same syntax as the number event action: "changenumber": "mycounter=+1" - Various fixes and improvements to the phase system: - Manually set phases will now also be persisted when the world is reloaded - New event action called 'phase'. This will allow you to set or clear a phase when an event happens. For example, you can now set a phase when a player kills a mob and then use that phase in a spawner rule to spawn mobs only when that phase is set - The 'phase' test is now also supported for experience, loot, effect, harvest, left click, right click, place, and summon aid rules - New custom event: - New 'customevent' action that you can use from within many rules to fire a custom event - New event trigger called 'custom' - New 'result' called 'deny_with_actions' which will deny the event but still execute the actions. This can be used to deny the spawn of a mob but still send out an event

<h2>InControl 1.20-9.1.3</h2><br/>&nbsp;&nbsp;&nbsp;- The 'spawner' test will now also work for 'onjoin'<br/>

<h2>InControl 1.19-7.1.12</h2><br/>&nbsp;&nbsp;&nbsp;- Removed invalid dimension test from the parser. That test would give errors when loading for dimensions that don't exist yet<br/>

<h2>InControl 1.20-9.1.2</h2><br/>&nbsp;&nbsp;&nbsp;- Removed invalid dimension test from the parser. That test would give errors when loading for dimensions that don't exist yet<br/>

<h2>InControl 1.18-6.1.12</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a rare threading condition related to counting<br/>

<h2>InControl 1.20-9.1.1</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a problem with the 'spawner' test not working with 'when' equal to 'position' (default)<br/>&nbsp;&nbsp;&nbsp;- Fixed a timing isue with loading the rule files again. In some cases rules where not executing during initial chunk loading<br/>

<h2>InControl 1.20-9.1.0</h2><br/>&nbsp;&nbsp;&nbsp;- New events.json system that allows the player to spawn mobs whenever something happens. Still work in progress<br/>&nbsp;&nbsp;&nbsp;- Implemented 'mob_killed' and 'block_broken' events<br/>&nbsp;&nbsp;&nbsp;- New 'eventspawn' test in 'spawn.json' that can be used to test for mobs spawned by the new events.json system<br/>&nbsp;&nbsp;&nbsp;- Added new 'setphase', 'clearphase', and 'togglephase' actions for effects, experience, leftclicks, rightclicks, harvests, and spawn events<br/>&nbsp;&nbsp;&nbsp;- New area system in 'areas.json'. This can be used by map makers to define predefined locations on the map. These areas can then be used in various rules. For example to create a peaceful area on a server<br/>&nbsp;&nbsp;&nbsp;- New 'area' test that can be used in nearly all rules (like spawn.json, loot.json, effects.json, ...). This will evaluate to true if the position is in the specified area<br/>&nbsp;&nbsp;&nbsp;- Added new /incontrol area command to show the current area<br/>&nbsp;&nbsp;&nbsp;- Added 'setphase' and 'clearphase' commands<br/>

<h2>InControl 1.20-9.0.4</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a timing error with loading rules at startup. They were loaded too late which causes onjoin rules to not work soon enough<br/>

<h2>InControl 1.20-9.0.3</h2><br/>&nbsp;&nbsp;&nbsp;- The 'timeout' keyword wasn't working in effects.json<br/>&nbsp;&nbsp;&nbsp;- Fixed a problem with the damage action. It wasn't working properly<br/>

<h2>InControl 1.18-6.1.11</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a problem in the spawner where there was the possibility that some mobs caused crashes during spawn position selection<br/>

<h2>InControl 1.19-7.1.11</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a problem in the spawner where there was the possibility that some mobs caused crashes during spawn position selection<br/>

<h2>InControl 1.19-7.1.10</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a rare threading condition related to counting<br/>

<h2>InControl 1.20-9.0.2</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a rare threading condition related to counting<br/>

<h2>InControl 1.20-9.0.1</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed spawn.json not working correctly for mobs spawned using spawner.json<br/>

<h2>InControl 1.20-9.0.0</h2><br/>&nbsp;&nbsp;&nbsp;- In Control for 1.20 works differently then previous versions. "onjoin" is gone. Instead there is now "when" with four possible values 'position', 'onjoin', 'finalize', and 'despawn'<br/>&nbsp;&nbsp;&nbsp;- The 'special.json' file is gone. Instead you can now use 'spawn.json' for all your needs. Using 'when' at finalize you can now control the equipment and stats of mobs<br/>&nbsp;&nbsp;&nbsp;- Merged all FxControl functionality into InControl<br/>

<h2>InControl 1.19.3-8.0.7</h2><br/>&nbsp;&nbsp;&nbsp;- Added 'minlight_full' and 'maxlight_full' keywords. These are similar to 'minlight' and 'maxlight' but they will test the full light level (including the sky light level)<br/>

<h2>InControl 1.19-7.1.9</h2><br/>&nbsp;&nbsp;&nbsp;- Added 'minlight_full' and 'maxlight_full' keywords. These are similar to 'minlight' and 'maxlight' but they will test the full light level (including the sky light level)<br/>

<h2>InControl 1.18-6.1.10</h2><br/>&nbsp;&nbsp;&nbsp;- Added 'minlight_full' and 'maxlight_full' keywords. These are similar to 'minlight' and 'maxlight' but they will test the full light level (including the sky light level)<br/>

<h2>InControl 1.19.3-8.0.6</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a bug in 'addscoreboardtags'<br/>

<h2>InControl 1.19-7.1.8</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a bug in 'addscoreboardtags'<br/>

<h2>InControl 1.18-6.1.9</h2><br/>&nbsp;&nbsp;&nbsp;- Fixed a bug in 'addscoreboardtags'<br/>

<h2>InControl 1.18-6.1.8</h2><br/>&nbsp;&nbsp;&nbsp;- Small validation fix for spawner.json<br/>

<h2>InControl 1.19.3-8.0.5</h2><br/>&nbsp;&nbsp;&nbsp;- InControl would not initialize correctly due to a bad placed validation<br/>

<h2>InControl 1.18-6.1.7</h2><br/>&nbsp;&nbsp;&nbsp;- InControl would not initialize correctly due to a bad placed validation<br/>

<h2>InControl 1.19-7.1.7</h2><br/>&nbsp;&nbsp;&nbsp;- InControl would not initialize correctly due to a bad placed validation<br/>

<h2>InControl 1.19.3-8.0.4</h2><br/>&nbsp;&nbsp;&nbsp;- New 'addscoreboardtags' keyword for spawner.json and spawn.json. With this you can add scoreboard tags on each entity spawned by this rule<br/>&nbsp;&nbsp;&nbsp;- New 'scoreboardtags_all' and 'scoreboardtags_any' conditions for spawn, experience, loot, special, and summonaid. These will test if all or any of the given tags are present on the entity<br/>&nbsp;&nbsp;&nbsp;- New 'nodespawn' action for spawn, special, and summonaid. This will prevent the mob from despawning<br/>&nbsp;&nbsp;&nbsp;- New 'time', 'height', and 'light' keywords which are supported wherever the corresponding min/max versions are supported. Using these keywords you can do more precise testing on the specific values. The wiki will contain more documentation on this<br/>&nbsp;&nbsp;&nbsp;- The 'daycount' keyword now also supports this new expression syntax. Using this you can now do things like: 'spawn zombies for two days every 10 days and spawn creepers for one day in the same cycle'<br/>&nbsp;&nbsp;&nbsp;- Added new 'minverticaldist' and 'maxverticaldist' keywords to the spawner system. These will allow you to specify a vertical distance between the spawner and the spawn position<br/>&nbsp;&nbsp;&nbsp;- The spawner system will now fail if no dimensions are specified (as it should, it's not optional)<br/>

<h2>InControl 1.19-7.1.6</h2><br/>&nbsp;&nbsp;&nbsp;- New 'addscoreboardtags' keyword for spawner.json and spawn.json. With this you can add scoreboard tags on each entity spawned by this rule<br/>&nbsp;&nbsp;&nbsp;- New 'scoreboardtags_all' and 'scoreboardtags_any' conditions for spawn, experience, loot, special, and summonaid. These will test if all or any of the given tags are present on the entity<br/>&nbsp;&nbsp;&nbsp;- New 'nodespawn' action for spawn, special, and summonaid. This will prevent the mob from despawning<br/>&nbsp;&nbsp;&nbsp;- New 'time', 'height', and 'light' keywords which are supported wherever the corresponding min/max versions are supported. Using these keywords you can do more precise testing on the specific values. The wiki will contain more documentation on this<br/>&nbsp;&nbsp;&nbsp;- The 'daycount' keyword now also supports this new expression syntax. Using this you can now do things like: 'spawn zombies for two days every 10 days and spawn creepers for one day in the same cycle'<br/>&nbsp;&nbsp;&nbsp;- Added new 'minverticaldist' and 'maxverticaldist' keywords to the spawner system. These will allow you to specify a vertical distance between the spawner and the spawn position<br/>&nbsp;&nbsp;&nbsp;- The spawner system will now fail if no dimensions are specified (as it should, it's not optional)<br/>

<h2>InControl 1.18-6.1.6</h2><br/>&nbsp;&nbsp;&nbsp;- New 'addscoreboardtags' keyword for spawner.json and spawn.json. With this you can add scoreboard tags on each entity spawned by this rule<br/>&nbsp;&nbsp;&nbsp;- New 'scoreboardtags_all' and 'scoreboardtags_any' conditions for spawn, experience, loot, special, and summonaid. These will test if all or any of the given tags are present on the entity<br/>&nbsp;&nbsp;&nbsp;- New 'nodespawn' action for spawn, special, and summonaid. This will prevent the mob from despawning<br/>&nbsp;&nbsp;&nbsp;- New 'time', 'height', and 'light' keywords which are supported wherever the corresponding min/max versions are supported. Using these keywords you can do more precise testing on the specific values. The wiki will contain more documentation on this<br/>&nbsp;&nbsp;&nbsp;- The 'daycount' keyword now also supports this new expression syntax. Using this you can now do things like: 'spawn zombies for two days every 10 days and spawn creepers for one day in the same cycle'<br/>&nbsp;&nbsp;&nbsp;- Added new 'minverticaldist' and 'maxverticaldist' keywords to the spawner system. These will allow you to specify a vertical distance between the spawner and the spawn position<br/>&nbsp;&nbsp;&nbsp;- The spawner system will now fail if no dimensions are specified (as it should, it's not optional)<br/>

<h2>InControl 1.19.3-8.0.3</h2><br/>&nbsp;&nbsp;&nbsp;- Added new 'building' keyword that you can use to test as a condition. This will allow testing if (for example) a spawn is in a certain list of buildings<br/>

<h2>InControl 1.19-7.1.5</h2><br/>&nbsp;&nbsp;&nbsp;- Added new 'building' keyword that you can use to test as a condition. This will allow testing if (for example) a spawn is in a certain list of buildings<br/>

<h2>InControl 1.18-6.1.5</h2><br/>&nbsp;&nbsp;&nbsp;- Added new 'building' keyword that you can use to test as a condition. This will allow testing if (for example) a spawn is in a certain list of buildings<br/>

<h2>InControl 1.19.3-8.0.2</h2><br/>&nbsp;&nbsp;&nbsp;- Added support for the 'tag' keyword in a block description (in favor of the old and non functional 'ore' keyword)<br/>

<h2>InControl 1.19-7.1.4</h2><br/>&nbsp;&nbsp;&nbsp;- Added support for the 'tag' keyword in a block description (in favor of the old and non functional 'ore' keyword)<br/>

<h2>InControl 1.18-6.1.4</h2><br/>&nbsp;&nbsp;&nbsp;- Added support for the 'tag' keyword in a block description (in favor of the old and non functional 'ore' keyword)<br/>

<h2>InControl 1.18-6.1.3</h2><br/>&nbsp;&nbsp;&nbsp;- Added new 'validspawn' and 'sturdy' conditions to the spawner system. This avoids spawning mobs on slabs for example<br/>

<h2>InControl 1.19-7.1.3</h2><br/>&nbsp;&nbsp;&nbsp;- Added new 'validspawn' and 'sturdy' conditions to the spawner system. This avoids spawning mobs on slabs for example<br/>

<h2>InControl 1.19.3-8.0.1</h2><br/>&nbsp;&nbsp;&nbsp;- Added new 'validspawn' and 'sturdy' conditions to the spawner system. This avoids spawning mobs on slabs for example<br/>

<h2>InControl 1.19.3-8.0.0</h2><br>&nbsp;&nbsp;&nbsp;- Port to 1.19.3<br>

<h2>InControl 1.19-7.1.2</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a problem with 'seesky' potentially locking the world in combination with onjoin: true<br>

<h2>InControl 1.18-6.1.2</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a problem with 'seesky' potentially locking the world in combination with onjoin: true<br>

<h2>InControl 1.18-6.1.1</h2><br>&nbsp;&nbsp;&nbsp;- The 'spawner' check works correctly for special.json too now<br>

<h2>InControl 1.19-7.1.1</h2><br>&nbsp;&nbsp;&nbsp;- The 'spawner' check works correctly for special.json too now<br>

<h2>InControl 1.19-7.1.0</h2><br>&nbsp;&nbsp;&nbsp;- Added an entirely new rule file (special.json). This rule file has 100% the same capabilities as the default spawn.json. However you don't control spawns in this rulie file but instead you have the option to control the equipment in a proper way. Rules in special.spawn have the following three results: "replace", "before", or "after". This way you can either replace or change the default vanilla behaviour with regards to setting default equipment, random follow range and handedness<br>

<h2>InControl 1.18-6.1.0</h2><br>&nbsp;&nbsp;&nbsp;- Added an entirely new rule file (special.json). This rule file has 100% the same capabilities as the default spawn.json. However you don't control spawns in this rulie file but instead you have the option to control the equipment in a proper way. Rules in special.spawn have the following three results: "replace", "before", or "after". This way you can either replace or change the default vanilla behaviour with regards to setting default equipment, random follow range and handedness<br>

<h2>InControl 1.19-7.0.16</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a potential hang when using the new groupdistance feature<br>

<h2>InControl 1.18-6.0.25</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a potential hang when using the new groupdistance feature<br>

<h2>InControl 1.19-7.0.15</h2><br>&nbsp;&nbsp;&nbsp;- Fixed 'blockoffset' and also allow "x", "y", "z" to be specified directly inside 'blockoffset' tag (in addition to being supported inside the 'offset' child tag)<br>

<h2>InControl 1.18-6.0.24</h2><br>&nbsp;&nbsp;&nbsp;- Fixed 'blockoffset' and also allow "x", "y", "z" to be specified directly inside 'blockoffset' tag (in addition to being supported inside the 'offset' child tag)<br>

<h2>InControl 1.18-6.0.23</h2><br>&nbsp;&nbsp;&nbsp;- Support for Serene Seasons is working again<br>

<h2>InControl 1.19-7.0.14</h2><br>&nbsp;&nbsp;&nbsp;- Support for Serene Seasons is working again<br>

<h2>InControl 1.19-7.0.13</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a bug in the new groupdistance feature<br>

<h2>InControl 1.18-6.0.22</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a bug in the new groupdistance feature<br>

<h2>InControl 1.18-6.0.21</h2><br>&nbsp;&nbsp;&nbsp;- Technical change: wrong interpretation of SpecialSpawn<br>

<h2>InControl 1.19-7.0.12</h2><br>&nbsp;&nbsp;&nbsp;- Technical change: wrong interpretation of SpecialSpawn<br>

<h2>InControl 1.18-6.0.20</h2><br>&nbsp;&nbsp;&nbsp;- Technical change: mobs spawned through the spawner system will now correctly fire the SpecialSpawn event<br>&nbsp;&nbsp;&nbsp;- New feature 'groupdistance' for spawner.json (in the 'amount' section). If this is set to 0 or greater mobs will spawn in groups (with the groupdistance used as the maximum distance between them)<br>

<h2>InControl 1.19-7.0.11</h2><br>&nbsp;&nbsp;&nbsp;- Technical change: mobs spawned through the spawner system will now correctly fire the SpecialSpawn event<br>&nbsp;&nbsp;&nbsp;- New feature 'groupdistance' for spawner.json (in the 'amount' section). If this is set to 0 or greater mobs will spawn in groups (with the groupdistance used as the maximum distance between them)<br>

<h2>InControl 1.19-7.0.10</h2><br>&nbsp;&nbsp;&nbsp;- Improved parsing of itemstacks. Removed the obsolete @ notation (metadata). Instead of the InControl &lt;itemid&gt;/&lt;nbtjson&gt; syntax you can now also use the vanilla syntax &lt;itemid&gt;{&lt;nbtjson&gt;}. Also / is no longer restricted in the nbt string<br>

<h2>InControl 1.18-6.0.19</h2><br>&nbsp;&nbsp;&nbsp;- Improved parsing of itemstacks. Removed the obsolete @ notation (metadata). Instead of the InControl &lt;itemid&gt;/&lt;nbtjson&gt; syntax you can now also use the vanilla syntax &lt;itemid&gt;{&lt;nbtjson&gt;}. Also / is no longer restricted in the nbt string<br>

<h2>InControl 1.19-7.0.9</h2><br>&nbsp;&nbsp;&nbsp;- Fixed major slowdown in biome testing<br>

<h2>InControl 1.18-6.0.18</h2><br>&nbsp;&nbsp;&nbsp;- Fixed small slowdown in biome testing<br>

<h2>InControl 1.18-6.0.17</h2><br>&nbsp;&nbsp;&nbsp;- Better 'insphere' test using newer version of Lost Cities<br>&nbsp;&nbsp;&nbsp;- Added new 'slime' test to test if a position is in a slime chunk<br>

<h2>InControl 1.19-7.0.8</h2><br>&nbsp;&nbsp;&nbsp;- Better 'insphere' test using newer version of Lost Cities<br>&nbsp;&nbsp;&nbsp;- Added new 'slime' test to test if a position is in a slime chunk<br>

<h2>InControl 1.19-7.0.7</h2> <p><br>&nbsp;&nbsp;&nbsp;- Fixed a problem with 'canspawnhere' and 'notcolliding' potentially locking up worldgen</p>

<h2>InControl 1.18-6.0.16</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a problem with 'canspawnhere' and 'notcolliding' potentially locking up worldgen<br>

<h2>InControl 1.18-6.0.15</h2><br>&nbsp;&nbsp;&nbsp;- Nbt 'value' matching was broken<br>

<h2>InControl 1.19-7.0.6</h2><br>&nbsp;&nbsp;&nbsp;- Nbt 'value' matching was broken<br>

<h2>InControl 1.16-5.2.12</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a potential incompatibility with fake worlds<br>

<h2>InControl 1.19-7.0.5</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a potential incompatibility with fake worlds<br>

<h2>InControl 1.18-6.0.14</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a potential incompatibility with fake worlds<br>

<h2>InControl 1.16-5.2.11</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a bug with nbt matching (comparing any given tag with 'value'). It would only work for numeric values. Now strings and boolean values are also supported<br>

<h2>InControl 1.18-6.0.13</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a bug with nbt matching (comparing any given tag with 'value'). It would only work for numeric values. Now strings and boolean values are also supported<br>

<h2>InControl 1.19-7.0.4</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a bug with nbt matching (comparing any given tag with 'value'). It would only work for numeric values. Now strings and boolean values are also supported<br>

<h2>InControl 1.19-7.0.3</h2><br>&nbsp;&nbsp;&nbsp;- Updated to latest forge<br>

<h2>InControl 1.19-7.0.2</h2><br>&nbsp;&nbsp;&nbsp;- Fixed the list and kill commands<br>&nbsp;&nbsp;&nbsp;- Fixed minlight/maxlight<br>

<h2>InControl 1.18-6.0.12</h2><br>&nbsp;&nbsp;&nbsp;- Fixed the list and kill commands<br>&nbsp;&nbsp;&nbsp;- Fixed minlight/maxlight<br>

<h2>InControl 1.16-5.2.10</h2><br>&nbsp;&nbsp;&nbsp;- Fixed minlight/maxlight<br>

<h2>InControl 1.19-7.0.1</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a problem with the biome test. It would crash occasionally<br>

<h2>InControl 1.19-7.0.0</h2><br>&nbsp;&nbsp;&nbsp;- First port to 1.19<br>

<h2>InControl 1.18-6.0.11</h2><br>&nbsp;&nbsp;&nbsp;- Added support for babies (new 'baby' keyword)<br>

<h2>InControl 1.16-5.2.9</h2><br>&nbsp;&nbsp;&nbsp;- Added support for babies (new 'baby' keyword)<br>

<h2>InControl 1.16-5.2.8</h2><br>&nbsp;&nbsp;&nbsp;- New feature where you can specify 'all': true in a counting rule (similar to hostile/passive)<br>

<h2>InControl 1.18-6.0.10</h2><br>&nbsp;&nbsp;&nbsp;- New feature where you can specify 'all': true in a counting rule (similar to hostile/passive)<br>

<h2>InControl 1.18-6.0.9</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a deadlock problem with minlight/maxlight for chunks that were being generated<br>&nbsp;&nbsp;&nbsp;- Fixed a deadlock problem with the spawner<br>

<h2>InControl 1.16-5.2.7</h2><br>&nbsp;&nbsp;&nbsp;- Fixed the 'continue' keyword in spawn.json<br>

<h2>InControl 1.18-6.0.8</h2><br>&nbsp;&nbsp;&nbsp;- Fixed the 'continue' keyword in spawn.json<br>

<h2>InControl 1.18-6.0.7</h2><br>&nbsp;&nbsp;&nbsp;- Mrbysco re-enabled GameStages support<br>&nbsp;&nbsp;&nbsp;- Re-enabled Lost Cities support<br>&nbsp;&nbsp;&nbsp;- 'helditem' as an action no longer worked<br>

<h2>InControl 1.18-6.0.6</h2><br>&nbsp;&nbsp;&nbsp;- Port to 1.18.2<br>

<h2>InControl 1.16-5.2.6</h2><br>&nbsp;&nbsp;&nbsp;- Made InControl compatible with FxControl again<br>&nbsp;&nbsp;&nbsp;- Fixed the 'phase' keyword for spawn rules<br>

<h2>InControl 1.18-6.0.5</h2><br>&nbsp;&nbsp;&nbsp;- Made InControl compatible with FxControl again<br>&nbsp;&nbsp;&nbsp;- Fixed the 'phase' keyword for spawn rules<br>

<h2>InControl 1.18-6.0.4</h2><br>&nbsp;&nbsp;&nbsp;- Bugfix with onjoin<br>

<h2>InControl 1.16-5.2.5</h2><br>&nbsp;&nbsp;&nbsp;- Bugfix with onjoin<br>

<h2>InControl 1.18-6.0.3</h2><br>&nbsp;&nbsp;&nbsp;- Added checks everywhere to see if invalid keywords are being used. When a keyword is not recognized you will get a warning<br>&nbsp;&nbsp;&nbsp;- Added new 'daycount' condition for phases and normal rules. This condition will evaluate true every 'N'th day. For example, "daycount": 10 will be true on day 0, day 10, day 20, and so on<br>

<h2>InControl 1.16-5.2.4</h2><br>&nbsp;&nbsp;&nbsp;- Added checks everywhere to see if invalid keywords are being used. When a keyword is not recognized you will get a warning<br>&nbsp;&nbsp;&nbsp;- Added new 'daycount' condition for phases and normal rules. This condition will evaluate true every 'N'th day. For example, "daycount": 10 will be true on day 0, day 10, day 20, and so on<br>

<h2>InControl 1.18-6.0.2</h2><br>&nbsp;&nbsp;&nbsp;- Fixed illegal limits on minheight/maxheight. They can now go negative<br>

<h2>InControl 1.16-5.2.3</h2><br>&nbsp;&nbsp;&nbsp;- Added new 'healthset', 'damageset', and 'speedset' keywords to specifically hard-set these attributes instead of modifying them<br>&nbsp;&nbsp;&nbsp;- Added protection to spawner so it doesn't try forever to find a suitable place to spawn a mob in case the box has a weird shape<br>&nbsp;&nbsp;&nbsp;- New statistics for spawn.json and spawner.json. These can help with debugging. Use the commands /incontrol showstats or /incontrol clearstats<br>&nbsp;&nbsp;&nbsp;- Fixed a problem where setting the current day (using /incontrol days) didn't get persisted correctly<br>

<h2>InControl 1.18-6.0.1</h2><br>&nbsp;&nbsp;&nbsp;- Added new 'healthset', 'damageset', and 'speedset' keywords to specifically hard-set these attributes instead of modifying them<br>&nbsp;&nbsp;&nbsp;- Fixed a problem with the spawner and negative heights<br>&nbsp;&nbsp;&nbsp;- Added protection to spawner so it doesn't try forever to find a suitable place to spawn a mob in case the box has a weird shape<br>&nbsp;&nbsp;&nbsp;- New statistics for spawn.json and spawner.json. These can help with debugging. Use the commands /incontrol showstats or /incontrol clearstats<br>&nbsp;&nbsp;&nbsp;- Fixed a problem where setting the current day (using /incontrol days) didn't get persisted correctly<br>

<h2>InControl 1.18-6.0.0</h2> <p><br>&nbsp;&nbsp;&nbsp;- First port to 1.18</p>

<h2>InControl 1.16-5.2.2</h2><br>&nbsp;&nbsp;&nbsp;- Attempt two to fix the spawner deadlock<br>

<p>1.16-5.2.1:<br>- Fixed a problem with the spawner where it was possible to get a deadlock situation with a rule that never managed to succeed</p>

<h2>InControl 1.16-5.2.0</h2><br>&nbsp;&nbsp;&nbsp;- InControl now keeps track of the day counter. Using the '/incontrol days' command you can see what the current day is and also change it. The day counter progresses whenever the time goes from night to day<br>&nbsp;&nbsp;&nbsp;- New 'mindaycount' and 'maxdaycount' tags for spawn.json, potentialspawn.json, summonaid.json, and also the new spawner.json.<br>&nbsp;&nbsp;&nbsp;- New phases.json rule file. There you can define phase rules for a limited set of global conditions. These phases can then be used in spawner, spawn, potentialspawn, ... for a more optimal way to check for rules<br>&nbsp;&nbsp;&nbsp;- New '/incontrol phases' command to check the current active phases<br>&nbsp;&nbsp;&nbsp;- New '/incontrol list' command to list all current mobs in the current world<br>&nbsp;&nbsp;&nbsp;- New 'weight' system for spawner so that you can now have relative weights for the different mobs spawned by a single rule<br>&nbsp;&nbsp;&nbsp;- The 'difficulty' test was broken<br>&nbsp;&nbsp;&nbsp;- Changed the 'inwater' option for spawner to only work for actual water and not for other fluids<br>&nbsp;&nbsp;&nbsp;- Added new 'inliquid' option which works for any liquid (as 'inwater' used to do)<br>&nbsp;&nbsp;&nbsp;- Added new 'inlava' option which works for lava<br>&nbsp;&nbsp;&nbsp;- Added the ability for spawner.json to spawn mobs that belong to the given biome. The new tag 'mobsfrombiome' can be used for that (instead of the normal 'mob' list). Possible values for this tag are: monster, creature, ambient, water_creature, water_ambient, and misc<br>

<h2>InControl 1.16-5.1.9</h2><br>&nbsp;&nbsp;&nbsp;- 'angry' tag should work better now<br>&nbsp;&nbsp;&nbsp;- The spawner system will no longer attempt to spawn hostile mobs in peaceful mode<br>&nbsp;&nbsp;&nbsp;- Fixed a serious problem with spawn rules using 'onjoin' and the 'block' test. It was possible that this rule would cause a deadlock (a non responsive Minecraft basically)<br>&nbsp;&nbsp;&nbsp;- The spawner system will no longer try to spawn mobs in unloaded chunks<br>&nbsp;&nbsp;&nbsp;- Much better error reporting and no longer crashing the game when there are json errors<br>

<h2>InControl 1.16-5.1.8</h2> <p><br>&nbsp;&nbsp;&nbsp;- Fixed mintime and maxtime</p>

<p>1.16-5.1.7:<br>- Fixed structure testing for good hopefully<br>- Fixed a serious problem with 'onjoin': true. It would also work for players and by doing that you could prevent players from joining the world which unfortunatelly doesn't work too well. Changed so that players are no longer affected</p>

<h2>InControl 1.16-5.1.6</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a few tests to work properly on new chunks<br>

<h2>InControl 1.16-5.1.5</h2><br>&nbsp;&nbsp;&nbsp;- Structure testing works again<br>&nbsp;&nbsp;&nbsp;- Added new 'dimensionmod' feature so that you can have a rule match for all dimensions of a given mod (like for example 'rftoolsdim')<br>

<h2>InControl 1.16-5.1.4</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a crash with the new spawner when the player moves outside world boundaries<br>

<h2>InControl 1.16-5.1.3</h2><br>&nbsp;&nbsp;&nbsp;- LostCity support is working again<br>&nbsp;&nbsp;&nbsp;- Made counting slightly safer in rare circumstances<br>

<h2>InControl 1.16-5.1.2</h2><br>&nbsp;&nbsp;&nbsp;- Gamestage support is working again<br>

<h2>InControl 1.16-5.1.1</h2><br>&nbsp;&nbsp;&nbsp;- Small bugfix<br>

<h2>InControl 1.16-5.1.0</h2><br>&nbsp;&nbsp;&nbsp;- Big new spawner system (spawner.json) which implements a custom spawner with very little restrictions<br>&nbsp;&nbsp;&nbsp;- New 'incontrol' tag for spawn.json to allow to test for a mob spawned by this new system<br>

<h2>InControl 1.16-5.0.4</h2> <p><br>&nbsp;&nbsp;&nbsp;- Fixed a big bug with the 'block' test which could cause worlgen to hang in some situations</p>

<h2>InControl 1.16-5.0.3</h2> <p><br>&nbsp;&nbsp;&nbsp;- Fixed a bug causing mob condition with multiple mobs to fail (one mob was fine)</p>

<h2>InControl 1.15-4.0.8</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a bug causing mob condition with multiple mobs to fail (one mob was fine)<br>

<p>3.9.18:<br>- The mob counter now ignores the nodespawn flag. This should make it more compatible with modded mobs</p>

<h2>InControl 1.15-4.0.7</h2><br>&nbsp;&nbsp;&nbsp;- New 'continue' flag for spawn rules. If this is true then when this rule fires it will not prevent processing for subsequent rules. This can be used (for example) to give armor to mobs under certain circumstances but still do other processing later<br>

<h2>InControl 1.16-5.0.2</h2> <p><br>&nbsp;&nbsp;&nbsp;- The 'biome' test would crash on biomes that were created using json<br>&nbsp;&nbsp;&nbsp;- New 'continue' flag for spawn rules. If this is true then when this rule fires it will not prevent processing for subsequent rules. This can be used (for example) to give armor to mobs under certain circumstances but still do other processing later</p>

<h2>InControl 1.16-5.0.1</h2><br>&nbsp;&nbsp;&nbsp;- The mob counter now ignores the nodespawn flag. This should make it more compatible with modded mobs<br>

<h2>InControl 1.15-4.0.6</h2><br>&nbsp;&nbsp;&nbsp;- The mob counter now ignores the nodespawn flag. This should make it more compatible with modded mobs<br>

<h2>InControl 1.16-5.0.0</h2><br>&nbsp;&nbsp;&nbsp;- Biome registry name is now preferred for biome checks<br>&nbsp;&nbsp;&nbsp;- 'tempcategory' is removed and replaced with a more generic 'category' for biomes. It's also a list now. The list of current categories is: taiga, extreme_hills, jungle, mesa, plains, savanna, icy, the_end, beach, forest, ocean, desert, river, swamp, mushroom and nether<br>&nbsp;&nbsp;&nbsp;- 'biometype' has changed. It now only works for the following values: desert, desert_legacy, warm, cool, and icy<br>&nbsp;&nbsp;&nbsp;- Numerical dimension ID's no longer work (like 0 for the overworld. Use 'minecraft:overworld' instead)<br>

<h2>InControl 1.15-4.0.5</h2><br>&nbsp;&nbsp;&nbsp;- The biome check now also supports biome registry names (this is prefered)<br>

<p>- Fixed a bug with the health, damage, and speed actions. They often fired multiple times making the mobs too OP</p>

<h2>InControl 1.12-3.9.17</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a bug with the health, damage, and speed actions. They often fired multiple times making the mobs too OP<br>

<p>4.0.3:<br>- 'perchunk' is implemented again<br>- Avoid server-side crashes in combination with debug command</p>

<p>4.0.2:<br>- Darkere improved performance when removing large amounts of mobs in potential spawn</p>

<p>4.0.1:<br>- Fixed a problem where the config files where generated in the root</p>

<p>First port to 1.15</p>

<h2>InControl 1.12-3.9.16</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a problem where 'onjoin' rules were also firing on the client which could cause issues with some of the conditions that don't properly work on the client<br>

<h2>InControl 1.12-3.9.15</h2><br>&nbsp;&nbsp;&nbsp;- Worked around a problem caused in the previous version. The issue was that there was both a condition called 'helditem' as well as an action called 'helditem'. For spawns the condition has been renamed to 'playerhelditem'. It is recommended to use this in other places as well (when used as a condition)<br>

<h2>InControl 1.12-3.9.14</h2><br>&nbsp;&nbsp;&nbsp;- Implemented a much requested feature with the spawn rules. That is support for gamestages. In Control will use the closest player (with a configurable maximum distance of 100). In addition keywords like helditem, helmet, trinker, ... are now also supported for spawn rules<br>

<h2>InControl 1.12-3.9.13</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a problem with the mincount/maxcount always using a hostile counter<br>

<h2>InControl 1.12-3.9.12</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a compatibility problem with old maxcount/mincount syntax<br>

<h2>InControl 1.12-3.9.11</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a problem that 'onJoin' rules would also affect entities like item drops and non-living entities<br>&nbsp;&nbsp;&nbsp;- Much more powerful 'mincount' and 'maxcount' syntax. The old syntax is still supported but you can now use a JSON object to specify one or more entities to count on, count entities for a given mod, and count scaled per player or per loaded chunk<br>&nbsp;&nbsp;&nbsp;- Fixed a problem with Minecraft mods being reported as 'forge' instead of 'minecraft'<br>

<h2>InControl 1.12-3.9.10</h2><br>&nbsp;&nbsp;&nbsp;- Removed some debug code<br>

<h2>InControl 1.12-3.9.9</h2><br>&nbsp;&nbsp;&nbsp;- Allow 'count' for itemstacks with 'give' and related commands<br>&nbsp;&nbsp;&nbsp;- Big optimisation in how 'maxcount' and 'mincount' are handled<br>

<h2>InControl 1.12-3.9.8</h2><br>&nbsp;&nbsp;&nbsp;- If a spawn rule has no explicit result given (as opposed to result default, deny, or allow) then InControl will no longer set any result but just leave the result in the event as it already is<br>&nbsp;&nbsp;&nbsp;- Added new 'customname' action for spawn rules that you can use to set customnames on mobs when they spawn (turns out this is not possible to do with NBT)<br>&nbsp;&nbsp;&nbsp;- The 'mintime' and 'maxtime' tests will now correctly work beyond the first day<br>

<h2>InControl 1.12-3.9.7</h2><br>&nbsp;&nbsp;&nbsp;- Various cleanups from SM9<br>&nbsp;&nbsp;&nbsp;- Subscribe to events with lowest priority to potentially catch more mods which have the same subscriber (from SM9)<br>&nbsp;&nbsp;&nbsp;- Fixed 'remove' in potential spawn. It was broken<br>

<h2>InControl 1.12-3.9.6</h2><br>&nbsp;&nbsp;&nbsp;- Update to be compatible with Fx Control<br>

<h2>InControl 1.12-3.9.5</h2><br>&nbsp;&nbsp;&nbsp;- Update to be compatible with Fx Control<br>

<h2>InControl 1.12-3.9.4</h2><br>&nbsp;&nbsp;&nbsp;- Loot control will now also support the more advanced itemstack syntax for removal. Note that this is a potentially compatibility breaking change as specifying something like 'minecraft:stone_sword' (without meta) will now match all stone swords while before it would only match stone_sword with meta 0<br>

<h2>InControl 1.12-3.9.3</h2><br>&nbsp;&nbsp;&nbsp;- Fixed a bug with the 'empty' keyword for items<br>&nbsp;&nbsp;&nbsp;- Postponed loading of the rule files so that blocks/items from other mods can be found better<br>

<h2>InControl 1.12-3.9.2</h2><br>&nbsp;&nbsp;&nbsp;- New 'mod' attribute for 'block' test so that you can test for modded blocks: 'block': { 'mod': 'rftools' }<br>&nbsp;&nbsp;&nbsp;- New 'mod' attribute for 'helditem' (and similar) test so that you can test for modded blocks<br>&nbsp;&nbsp;&nbsp;- New 'empty' attribute for 'helditem' (and similar) tests so that you can test for an empty item: 'helditem': { 'empty': true }<br>&nbsp;&nbsp;&nbsp;- New 'count' attribute for 'helditem' (and similar) tests so that you can add expresssions to test for amounts. For example 'helditem': { 'item': 'minecraft:coal', 'count': '>=10' }<br>&nbsp;&nbsp;&nbsp;- New 'ore' attribute for 'helditem' (and similar) tests to do ore dictionary tests<br>&nbsp;&nbsp;&nbsp;- New 'energy' attribute for 'helditem' (and similar) tests to that you can test for forge energy in an item. This supports expressions<br>&nbsp;&nbsp;&nbsp;- New 'energy' attribute for 'block' test to that you can test for forge energy in a block. There is also a new 'energyside' attribute which allows you to specify from which side the energy will be examined. If not given it will use null<br>

<h2>InControl 1.12-3.9.1</h2><br>&nbsp;&nbsp;&nbsp;- Much more powerful item description system with expressions on damage and nbt<br>&nbsp;&nbsp;&nbsp;- Giving items (armor, helditem, give command) is now also much more general and supports the new system<br>&nbsp;&nbsp;&nbsp;- Removed 'blockup' command and instead add a more general 'blockoffset' command that works together with the 'block' command<br>&nbsp;&nbsp;&nbsp;- Added support for EnigmaScript though 'state' and 'pstate' tests<br>

<h2>InControl 1.12-3.9.0</h2><br>&nbsp;&nbsp;&nbsp;- Added support for Serene Seasons with new 'winter', 'summer', 'spring', and 'autumn' boolean keywords<br>&nbsp;&nbsp;&nbsp;- Added support for baubles: new 'amulet', 'ring', 'belt', 'trinket', 'charm', 'body', 'and 'head' keywords<br>&nbsp;&nbsp;&nbsp;- New 'blockup' test for various rules which will test the condition of the block above the current position<br>&nbsp;&nbsp;&nbsp;- New 'message' action to print a status message on screen for the nearest player (for 'spawn')<br>

<h2>InControl 1.12-3.8.3</h2><br>&nbsp;&nbsp;&nbsp;- New 'offhanditem' and 'bothhandsitem' tags that are equivalent to 'helditem' but also work on the offhand (or both)<br>

<p>3.8.2:</p> <p>- Update to GameStages 2.0. This breaks compatibility with old GameStages so if you update this mod make sure to update GameStages as well!</p>

<h2>InControl 1.12-3.8.1</h2><br>&nbsp;&nbsp;&nbsp;- Added a rule to check for spawns by mob spawners<br>

<p><strong>3.8.0:</strong></p> <ul> <li>New 'itemcount' tag to specify the amount of items to drop in a loot rule. Can also depend on looting/fortune level. For example: "itemcount": "5/5-7/1000" would give 5 items at looting 0, 5-7 items at looting 1 and 1000 items at looting 2 or higher</li> <li> <p>&nbsp;The 'blocks' check can now also use the ore dictionary (use like 'ore:plankWood')</p> </li> <li>There is a new 'biometype' check that will check on biome dictionary entries (like 'COLD', 'WARM', ...)</li> </ul>

<p><strong>3.7.1:</strong></p> <ul> <li>Use new Lost City API which should make things compatible with sponge</li> <li>Requires Lost Cities 2.0.3</li> </ul>

<p><strong>3.7.0:</strong></p> <ul> <li>New 'experience.json' file where you can alter the experience that you get from monsters under certain conditions</li> <li>New 'insphere' keyword for Lost Cities to have different behaviour inside or outside a sphere</li> </ul>

<p><strong>3.6.6:</strong></p> <ul> <li>Andrew fixed a bug where items given by spawn rules would sometimes disappear</li> </ul>

<p><strong>3.6.5:</strong></p> <ul> <li>Added support for adding NBT to loot items and spawned mobs</li> </ul>

<p><strong>3.6.4:</strong></p> <ul> <li>Added 'gamestage' mod support to the loot rules. You can now have loot that depends on the current stage of the player</li> </ul>

<p><strong>3.6.3:</strong></p> <ul> <li>New 'fakeplayer' and 'realplayer' keywords for loot control. By using those you can have rules that only work on real or on fake players as opposed to all players. The normal 'players' keyword still works on both fake and real players like it did before</li> </ul>

<p><strong>3.6.3:</strong></p> <ul> <li>New 'fakeplayer' and 'realplayer' keywords for loot control. By using those you can have rules that only work on real or on fake players as opposed to all players. The normal 'players' keyword still works on both fake and real players like it did before</li> </ul>

<p><strong>3.6.2:</strong></p> <ul> <li>Fixed a potential bug that could cause loot to be too big in some cases</li> </ul>

<p><strong>3.6.2:</strong></p> <ul> <li>Fixed a potential bug that could cause loot to be too big in some cases</li> </ul>

<p><strong>3.6.1:</strong></p> <ul> <li>Fixed a problem preventing InControl from working properly on servers</li> </ul>

<p><strong>3.6.0:</strong></p> <ul> <li>New feature in spawn rules. If you add "onjoin": "true" to a spawn rule it will also be activated when entities join the world. This is a much stronger test and allows you to block spawns from mob spawners as well as make it easier to block passive mobs from spawning (which don't always pass through the regular 'checkspawn' event)</li> </ul>

<p><strong>3.6.0:</strong></p> <ul> <li>New feature in spawn rules. If you add "onjoin": "true" to a spawn rule it will also be activated when entities join the world. This is a much stronger test and allows you to block spawns from mob spawners as well as make it easier to block passive mobs from spawning (which don't always pass through the regular 'checkspawn' event)</li> </ul>

<p><strong>3.5.6:</strong></p> <ul> <li>Support for The Lost Cities mod: three new conditions: incity, instreet, and inbuilding</li> <li>New feature to allow specifying weights with helditem and other actions that add items to mob spawns. The new notation is: "armorchest": ["5=minecraft:iron_chestplate", "1=minecraft:golden_chestplate"] The old notation still works and then 1 is assumed</li> </ul>

<p><strong>3.5.6:</strong></p> <ul> <li>Support for The Lost Cities mod: three new conditions: incity, instreet, and inbuilding</li> <li>New feature to allow specifying weights with helditem and other actions that add items to mob spawns. The new notation is: "armorchest": ["5=minecraft:iron_chestplate", "1=minecraft:golden_chestplate"] The old notation still works and then 1 is assumed</li> </ul>

<p>First release for 1.12</p>

<p><strong>3.5.5:</strong></p> <ul> <li>Addded a ctrlshowmobs command that lists all available mob id's that you can use in the config (in the console output or log)</li> <li>New ctrlkill command to kill all entities of a certain type: 'all' will kill every entity (including drops but not players). 'hostile' will kill only hostile mobs, 'passive' only passive, 'entity' only non-living entities. You can also supply the name of the entity to kill (like 'ctrlkill minecraft:enderman' on 1.11) and an optional dimension id</li> </ul>

<p><strong>3.5.4:</strong></p> <ul> <li>For loot, helditem, remove item and everywhere else that you can specify items it is now possible to specify both metadata as well as NBT: <ul> <li>For metadata: "minecraft:hard_stained_clay@13"</li> <li>For NBT the same syntax as with /give command. For example:&nbsp; <pre>"minecraft:stained_hardened_clay@13/{display:{Lore:[\"My Clay\"]}}"</pre> </li> </ul> </li> </ul>

<p><strong>3.5.3:</strong></p> <ul> <li>Fixed a configuration problem with other mods because In Control was reading the config file too soon. That means it was not possible to configure based on mobs from other mods</li> </ul>

<p><strong>3.5.2:</strong></p> <ul> <li>Added four new commands 'ctrlloadloot', 'ctrlloadspawn', 'ctrlloadpotentialspawn', and 'ctrlloadsummonaid' which can be used to load custom rules at runtime. This can be useful for command blocks so that they can change the loot rules depending on external factors</li> <li>For enderman the 'helditem' tag will put the item in their hand as a block (if it is a block)</li> </ul>

<p><strong>3.5.1:</strong></p> <ul> <li>Added 'canspawnhere' and 'isnotcolliding' tests to the spawn rules</li> </ul>

<p><strong>3.5.0:</strong></p> <ul> <li>Reordered all rule checks so that faster checks come first</li> <li>New 'summonaid.json' file which works the same as the 'spawn.json' file but is triggered when zombies are summoned for aid</li> <li>Big refactoring to the code to make it much easier to handle</li> <li>Fixed player test for loot. It was broken</li> <li>Fixed explosion, projectile, fire, and magic tests for loot in case the damage had no source</li> <li>When the result of a spawn is 'default' (as opposed to 'deny' or 'allow') then the associated actions are also performed. So only in the case of 'deny' are the actions not performed</li> </ul>

<p><strong>3.0.0:</strong></p> <ul> <li>Big refactor of the rule parsing system. Much easier to manage and add new rules that way</li> <li>Added the option to add items and armor to spawned creatures (via spawn.json)</li> <li>Minspawndist/maxspawndist actually calculate to the actual spawn point of the map instead of 0,0,0</li> <li>Implemented spawn control and spawn rules based on structures. That means that you can now let rules match only in villages, nether fortresses, witch huts, ocean monuments, ...</li> <li>Added the ability to filter based on the number of mobs of a certain type already present</li> <li>Add the ability to remove spawns in potential spawns (potentialspawns.json)</li> <li>New loot rule system (loot.json). With this system you can now remove and add loot based on various conditions</li> </ul>

<p><strong>2.0.0:</strong></p> <ul> <li>A few fixes to existing features (like the ability to spawn mobs based on block wasn't working properly)</li> <li>Huge number of new tests for rules: <ul> <li>weather</li> <li>difficulty and regional difficulty</li> <li>light level</li> <li>seesky test</li> <li>time based checks</li> <li>biome temperature check</li> <li>biome check</li> <li>distance to spawn</li> <li>random test</li> </ul> </li> <li>If a test succeeds you can now also perform actions on the spawned entity: <ul> <li>Alter damage that a mob does</li> <li>Alter the movement speed</li> <li>Alter maximum health</li> <li>Make the mob 'angry' by default</li> </ul> </li> <li>Added a new type of rule (in 'potentialspawn.json'). These rules use the same tests (most of them) as the normal rules and allow you to add new types of spawn (i.e. creatures that normally don't spawn there)</li> <li></li> </ul>

<p><strong>1.0.0:</strong></p> <ul> <li>First release of InControl</li> </ul>