InControl 1.18-6.1.8
- Small validation fix for spawner.json
InControl 1.19.3-8.0.5
- InControl would not initialize correctly due to a bad placed validation
InControl 1.18-6.1.7
- InControl would not initialize correctly due to a bad placed validation
InControl 1.19-7.1.7
- InControl would not initialize correctly due to a bad placed validation
InControl 1.19.3-8.0.4
- New 'addscoreboardtags' keyword for spawner.json and spawn.json. With this you can add scoreboard tags on each entity spawned by this rule
- 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
- New 'nodespawn' action for spawn, special, and summonaid. This will prevent the mob from despawning
- 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
- 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'
- 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
- The spawner system will now fail if no dimensions are specified (as it should, it's not optional)
InControl 1.19-7.1.6
- New 'addscoreboardtags' keyword for spawner.json and spawn.json. With this you can add scoreboard tags on each entity spawned by this rule
- 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
- New 'nodespawn' action for spawn, special, and summonaid. This will prevent the mob from despawning
- 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
- 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'
- 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
- The spawner system will now fail if no dimensions are specified (as it should, it's not optional)
InControl 1.18-6.1.6
- New 'addscoreboardtags' keyword for spawner.json and spawn.json. With this you can add scoreboard tags on each entity spawned by this rule
- 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
- New 'nodespawn' action for spawn, special, and summonaid. This will prevent the mob from despawning
- 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
- 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'
- 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
- The spawner system will now fail if no dimensions are specified (as it should, it's not optional)
InControl 1.19.3-8.0.3
- 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
InControl 1.19-7.1.5
- 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
InControl 1.18-6.1.5
- 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
InControl 1.19.3-8.0.2
- Added support for the 'tag' keyword in a block description (in favor of the old and non functional 'ore' keyword)
InControl 1.19-7.1.4
- Added support for the 'tag' keyword in a block description (in favor of the old and non functional 'ore' keyword)
InControl 1.18-6.1.4
- Added support for the 'tag' keyword in a block description (in favor of the old and non functional 'ore' keyword)
InControl 1.18-6.1.3
- Added new 'validspawn' and 'sturdy' conditions to the spawner system. This avoids spawning mobs on slabs for example
InControl 1.19-7.1.3
- Added new 'validspawn' and 'sturdy' conditions to the spawner system. This avoids spawning mobs on slabs for example
InControl 1.19.3-8.0.1
- Added new 'validspawn' and 'sturdy' conditions to the spawner system. This avoids spawning mobs on slabs for example
InControl - 1.19.3-8.0.0
on Jan 26, 2023InControl 1.19.3-8.0.0
- Port to 1.19.3
InControl - 1.19-7.1.2
on Jan 26, 2023InControl 1.19-7.1.2
- Fixed a problem with 'seesky' potentially locking the world in combination with onjoin: true
InControl - 1.18-6.1.2
on Jan 26, 2023InControl 1.18-6.1.2
- Fixed a problem with 'seesky' potentially locking the world in combination with onjoin: true
InControl - 1.18-6.1.1
on Jan 26, 2023InControl 1.18-6.1.1
- The 'spawner' check works correctly for special.json too now