Whilst the /datapack command is very rarely used, it frequently happens to be the case that you will want a certain datapack to load before/after another. This can be due to creators wanting certain functions from other datapacks to The issue with this is that the way to do that would be the following.
Within the function mentioned in 'load.json', the following two commands would be run.
datapack disable <this datapack>
datapack enable <this datapack> <before|after|whatever> <other datapack>
The issue with this is that it will automatically run the /reload command along with any iteration of the /datapack command. It should be mentioned that Mojang has managed to stop the issue of infinite regression that could occur if a /reload or /datapack command was run in the assigned loading function however it still remains the issue that the function is run multiple times every time the player reloads the world.
Mojang has, however, not stopped it if two loading functions from two different functions disabled and re-enabled each other. That will go on infinitely and increase your server tick count to upwards of 2000ms per tick.
In future, I would like to see this auto-reload functionality either removed or togglable within the command itself. With new snapshots coming out, I am hopeful that this idea will be welcomed by Mojang as the game's command block community would, too, welcome it.
Thank you.
Please sign in to leave a comment.
1 Comments