<aside>
🟢 Release: -
</aside>
<aside>
🟠Release Candidate: -
</aside>
<aside>
🔴
In Development: v1.00.00
</aside>
Todo
- [x] Port everything from the old datapack framework
- [x] Update to mc1.21
- config
- [x] Fix a bug where listeners can respond to the same event twice
- add a EVENT$command.config.handled tag per datapack to make sure the same event doesn’t trigger twice, it will reset when EVENT$command.config DatapackManager is false
- try to make it not pollute the scoreboard
- [x] There’s currently a bug where if a datapack is not uninstalled correctly, the LOOP$main.isActive would still be true and prevent the start function from starting the datapack
- reset it upon first starting of loops onload
- [x] update from 1.21.4 to 1.21.8
- [x] add any missing specific versions required
- [ ] Port all existing datapacks to the new framework
- [x] update to 1.21.10
- [ ] update to 1.21.11
Applications : Minecraft : Gamer Geeks
Important Info
This contains critical information and explanations as to why certain design decisions are made.
- cascading datapack overrides
- datapacks are executed by alphabetical order, so adding the version to the back can prevent older versions from running (eg. v1 runs first, then v2 runs and disables v1)
- the fact that future versions run later gives them data priority and allows them to change a variable in v1 that disables them permanently