Closed John-Paul-R closed 2 years ago
The registration callback is earlier for Command Aliases because of the mod id I presume. If I revert back this breaks all commands when using /reload
for datapacks.
I'm not sure how to tackle this issue, if someone knows a way to get around this without having both issues appear feel free to PR.
Alright, I've put up a PR with a possibly way to resolve this. Not sure I particularly like the approach, but I think it should work. Still need to do some local testing. (#35)
(I believe) Due to this command registration change, it is now possible for CommandAliases to load aliases before other mods have registered their commands, which will cause the registration process to fail for any CommandAliases nodes that reference one of these not-yet-registered commands.
Repro:
config/commandaliases/
/h
does not exist:/commandaliases reload
,/h
is registered and works as intended.