InControl 1.19-7.1.17
- Fixed a problem with "onjoin" rules where the "incontrol" tag would not work properly
InControl 1.21-10.0.1
- Fixed a problem with "onjoin" rules where the "incontrol" tag would not work properly
- Added two new keywords: "inmultibuilding" and "multibuilding" that work similar to the "inbuilding" and "building" keywords but for multi buildings (Lost Cities)
- Some fixes
InControl 1.20-9.2.7
- Fixed a problem with "onjoin" rules where the "incontrol" tag would not work properly
- Added two new keywords: "inmultibuilding" and "multibuilding" that work similar to the "inbuilding" and "building" keywords but for multi buildings (Lost Cities)
InControl 1.18-6.1.14
- Fixed a problem with "onjoin" rules where the "incontrol" tag would not work properly
InControl 1.19-7.1.16
- 'hasstructure' and 'structuretags' now actually work
InControl 1.21-10.0.0
- First version for 1.21
InControl 1.19-7.1.15
- The 'structure' test now supports lists
- New 'hasstructure' boolean test
- New' structuretags' test to test for structure tags
InControl 1.20-9.2.6
- Fixed a problem with the 'hasstructure' test
InControl 1.20-9.2.5
- New 'hasstructure' boolean test to test if the current position has any structure
- New 'cave' test that tries to see if the position is in a cave
- The 'mod' test in item filters was not working at all
- Item filters have improved. It's now possible to not have to specify the item but instead match on tag or mod only
- 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
InControl 1.19-7.1.14
- 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
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
InControl 1.19-7.1.13
- The remove gamestage action did actually8 add the stage instead of removing it
InControl 1.20-9.2.4
- The remove gamestage action did actually add the stage instead of removing it
InControl 1.20-9.2.3
- Fixed race condition in the event system
InControl 1.20-9.2.2
- The 'structures' test now supports lists
- New 'structuretags' test to support a (list of) structure tags
InControl 1.20-9.2.1
- Fix with position checks. They would crash if you used deny
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
InControl 1.20-9.1.3
- The 'spawner' test will now also work for 'onjoin'
InControl 1.19-7.1.12
- Removed invalid dimension test from the parser. That test would give errors when loading for dimensions that don't exist yet
InControl 1.20-9.1.2
- Removed invalid dimension test from the parser. That test would give errors when loading for dimensions that don't exist yet