![XP Obelisk](https://media.forgecdn.net/avatars/thumbnails/413/374/256/256/637634189318351856.png)
Command issues on 1.19.2.
pokesmells opened this issue ยท 23 comments
Hi! when joining the server with this mod it does this:
Joining the server and typing any command (example of /gamemode creative here) this appears in chat.
Cannot invoke "com.mojang.brigadier.CommandDispatcher.execute(String, Object)" because net.fabricmc.fabric.impl.command.client.ClientCommandInternals.activeDispatcher" is null
Now it fixes by joining a single-player world first then joining the server, but having to join a single-player world each time on launch just to use any commands is annoying and weird.
To determine this mod was the issue, I did a binary search and concluded this mod was the one causing the issues.
I read the logs and oh boy there are a lot of errors/warnings conflicts and failed mixings... I don't find any problem on my side and I hear about this issue for the first time. I take a deeper look and Test a little bit.
And can you tell me more about the binary search?
hello,
Can you provide a crash report and a list of mods on which you play on?
I cant imagine that my mod does this... i modify none of command or chat things.
i try to take a look but i don't know if i can resolve that issue...
Hi!, I'll recreate the issue once again, and provide latest logs and screenshots/video evidence, but it does not create a crash report as it doesn't crash the client or server, rather for some odd reason, it just doesn't let the client initiate commands and returns with the statement I provided above, ALTHOUGH I can do commands through the console.
It fixes itself when joining a single player world and then leaving the single-player world, then rejoining the server.
Restarting the server does not make the problem comeback, which would indicate this is a client side bug with the mods.
Closing and relaunching does make the problem comeback UNLESS you do the single-player join fix.
b84dc8fbfeb403705c99dd77d2de6c75.mp4
1e9e350bf3c4d2f0bedca7832f1d14b7.mp4
This is to show I had your mods in both the server and client when showing the issues above.
49f8974650901d479af73fbe1282da3a.mp4
Here is the video showing I have my server up, and cannot initiate commands via the client.
latest.log
This is the latest log for the server-side of things, WITH your mods
latest.log
This is the latest log with the client-side WITH your mods
a5d967a1bce04909c6e3a7efcc9c4be5.mp4
Here is the video showing that commands work via client input WITHOUT your mods installed on client and server
This is the latest log of the client side WITHOUT your mods
Here is the latest log of the server side WITHOUT your mods
e9b02d500641db2d5b6004d918c5092d.mp4
4ba614d5fb7a0fa828c5d390be63b7f0.mp4
This is to show that I did not have your mods installed during the time of the second test when commands worked both on the client side or server side.
I love love your mods capabilities, but hopefully you can figure out what the heck is going on so I can use it once again!
I wish you good luck in the search for the issue :)
thanks for the feedback, does the issue occur without the additions mod? maybe there lies the problem?
I basically just kept taking out mods until the issue stopped, legit had to go in one by one
Ran into this issue as well on our server. Going back to a previous version of the xp obelisk mods fixed it.
Here's our modlist if you want it.
mod list.txt
Thanks for the list.
that's strange, some other mod interact with my mod. since stand alone this error don't occur and the mod does nothing with commands etc...
Took me forever to figure out that down revving these two fixed it after updating all of our mods.
I thought it was strange too. We have some mods that I would have expected to cause issues, but this wasn't one of them. I can run commands in the console just fine, but not in game. Made sure it wasn't an op issue as well.
Also, for extra info. You can run commands just fine with these 2:
xp_obelisk-0.4.5.r_for_1.19.x_Fabric.jar
xp_obelisk_additions-0.1.3+1.19.x.jar