subatomicsquid
commented
3 years ago Update: via /mg edit [game name] I was able to get to the GUI for setting up kits. While this didn't solve the issue, it provides a fairly easy workaround.
Open subatomicsquid opened 3 years ago
subatomicsquid
commented
3 years ago Update: via /mg edit [game name] I was able to get to the GUI for setting up kits. While this didn't solve the issue, it provides a fairly easy workaround.
Describe the bug Upon issuing the /mg globalloadout command, I'm met with "An internal error occurred while attempting to perform this command" in red text. The GUI does not appear.
To Reproduce To cause this issue, I began by creating a kit via /mg globalloadout. The armor slots were all black-dyed leather armor with projectile protection IV. The hotbar had a punch II bow in slot 1, a quick charge III crossbow in slot 2, and an unenchanted elytra in slot 3. I went to enter a name for the kit, and the GUI closed and the chat gave me the message telling me to put my desired name into the chat. I entered "Raven", and then reentered /mg globalloadout so I could apply potion effects. I hit the potion effect button, and was once again kicked out of the GUI and prompted to enter my desired effects into the chat. To my recollection, I entered "leaping 2 inf" into the chat, and that was it. Thereafter, giving the /mg globalloadout command consistently returns me the error message given earlier.
Expected behavior I just expect the GUI for setting up kits to open up.
Screenshots I'm afraid I can't duplicate this bug, as it seems to have had a permanent (until I can find a fix, that is) effect on the functionality of the globalloadout command. I performed the steps to instigate the bug once, now anytime I enter the command I get the same error message
Server (please complete the following information):
Additional context I'm very new to this whole thing. I apologize if this error that I'm running into is particularly simple to solve, or if I haven't managed to give enough information. I'm still learning to read code, and I'm working my way through it. Additionally, it may also be worth noting that although I've had this plugin for several weeks, today is the first day I'd began using the globalloadout command, and I was making my first kit when I encountered the error. The error code that reads on the console side of things will follow below: