This update breaks the old database, delete it and a new one will be generated.Since it's the first update I will not implement database data bridging to avoid clutter and focus on new features. If you need more help please join the discord.
- Added `unplaceable` option for items: prevents items from being placed, useful for keys (i.e. tripwire hook) - Fixed a bug where you could place blocks in gate occupied locations - Fixed compatibility with 1.16.5 - Added toolEquals condition - Added toolIdEquals condition (the id is the name of the item yaml section) - Added `restore-original-blocks-on-remove` option to config.yml. Now if you place a gate that removes existing blocks, those blocks will be saved temporarly so that they can be replaced if you decide to remove the gate. keep-blocks-on-remove overrides this feature.
- You can now place blocks against a gate reducing frustration when building your map. Must have the castlegates.build.on.gate permission!
- Completely reworked the gate state and logic and decoupled it from the gate class.