Finally an event about datapacks... Unfortunately, a framework is imposed!
It poses many problems in my opinion:
- We (datapack creators) don't all have the same way of coding and that can disturb more than one. I know that this is also done so that everyone can try to do something, however I don't find the way it was done intuitive.
- The imposed framework is globally badly coded. For having a look at the code there are unfortunately much better things to do, which is disturbing for an event! It would have been necessary to review some parts, especially in terms of optimization (even if I know that compatibility is not always easy to manage). Commenting on what has been done also seems very important to me in the context where some people will use it as a base.
- Modifying the framework for 1.16 is a very bad idea. I know that the event was launched in 1.15 and that 1.16 (which allows more things) is out. Unfortunately doing a datapack event on two versions can cause compatibility problems. Either people playing with it will have to change versions, or the creators will have to update them once their work is done for a version that is still unstable.
- The recurring presence (each time the datapack is loaded etc...) of the name of the host of the event is also disturbing. I know that this argument may seem silly but it offers a lot of visibility for something that is unfortunately not worth it.
Anyway, I'm not sending this comment to denigrate the work that has been done upstream, but to suggest to review in the future the points I criticized.I'm not completely opposed to the idea of imposing a framework, but it has to be clear to everyone and this is just my opinion.
Awhikax
