
plugin crashes in 1.17.1 when tab complete activates
HammerWizrd opened this issue ยท 7 comments
so im using this plugin on a 1.17.1 paper server and when i upgraded from 1.17 the plugin crashes itself whenever you try use a command with it, ill get as far as /warp and the moment i hit space itll crash. i dont quite know how to get ahold of you other than here so if you see this my discord tag is Hammer_Wizrd#8475.
Here is also a copy from the server cmd of the issue and its issues on boot with 1.17.1 : https://mcpaste.io/b57082f1f5038c71
Weird. I just tested using the most recent Spigot build (3266-Spigot-3892929-fd50041
). While tab complete did not work, the server did not crash.
Could you post the output of the following commands?
/version
/version mywarp
Also it was not the server that was crashing but the plugin itself, i couldnt use the warp system or locate any previous warps as well as most if not all commands. ingame it would give the could not tab complete error, server side would throw a larger error that was essentially the same thing. command line error is as follows : https://mcpaste.io/b269c8c38fcfa2a6
Could you try updating your version of Paper?
I just tested the latest build (353) which seems to work fine.
updated to 353 and the issue still persists
https://mcpaste.io/a119e1768750d7fd
After some research, it appears that the error may be caused by a corrupted JAR-file. This happen if you replace a plugin's JAR-file while the server is still running, or if you are using /reload
.
Please try the following:
- Stop your server
- Delete MyWarp's plugin-file (
mywarp-bukkit-3.1.1-all.jar
) - Download a fresh copy from BukkitDev and drop it in your plugin folder
- Start the server
In the last log I also noticed that there appears to be some issue with MyWarp's H2 database:
29.10 20:16:16 [Server] ERROR [MyWarp] Failed to initialize warp storage.
29.10 20:16:16 [Server] ERROR [MyWarp] (Message 90062 not found) [90062-200]
The error indicates that H2 cannot create its database file. This may or may not be related to the problem above. Are you using the storage default configuration?
so we got the issue sorted out, turns out it was a combo of corrupted .jar file, lost database file, and an initial setup after an FTP transfer. one of the assistants found that the plugin wasnt able to find the previous database file bc the location was swapped during the transfer and wasnt renamed causing the autocomplete to break. a rename and it was all good to go! Thank you again for the help!