-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please add support to 1.20.4 #70
Comments
As i know, this plugin is not version dependent! Whats the bugs or problems? |
I know 1 problem, I can't connect the plugin to database, when I connected it, it created a big mess in console and wasn't even working properly or it would just nor start the plugin. |
You have the error logs? |
Well I wanted to send you logs but I don't see the error anymore in the console. Don't know what happened :D But I appreciate the update you released thank you for that :) And I found 1 bug, when I use %pixelvip_expiration_desc% in BeastTokens menu it shows this error in console and the plugim (BeastTokens) stops working. Error: |
Update, %pixelvip_expiration_desc% <-- this placeholder isn't working anymore, not even if I try to do /papi parse %pixelvip_expiration_desc% It just shows this error: org.bukkit.command.CommandException: Unhandled exception executing command 'papi' in plugin PlaceholderAPI v2.11.6 |
And here is another error in console when removing player vip [02:30:22 INFO]: [PixelVip] Error on removeVip: Cannot invoke "String.split(String)" because "key[2]" is null |
Last error I found ( You could fix this one <3 ) [15:50:25 WARN]: [PixelVip] Task #60347 for PixelVip v3.0.5 generated an exception
|
The latest error i can fix, the others i cant test anymore as i am not using and i dont have a mysql setup to test, but can you test using local database instead mysql? |
As I'm only server technician I don't think I can experiment with plugins. |
Please update the plugin for 1.20.4, maybe you could fix some known bugs too :) I really like this plugin and it would be a shame if it stopped working :(
The text was updated successfully, but these errors were encountered: