Database issues
Jakaboii opened this issue · 7 comments
What steps will reproduce the problem?
- Enable "sql" on the storage.type option in config.yml
- Join the server
- wait
What were you expecting to happen? What happened instead?
What version of the plugin are you using?
3.18.1-SNAPSHOT
What Spigot version are you using?
Paper 1.8.8 (latest release)
What plugins are you using? Type /plugins
Do you have an error log?
https://hatebin.com/pdpeqmstan
Did your client crash?
No
Additional information?
I'm using Flamecord & I don't think this happened on previous versions, I can't remember though
The error didn't happen when I changed storage.type to "local"
This still may not be caused by NickNamer, as I actually don't exactly know how to reproduce this, I just said was I'm pretty sure happened
I'm guessing this might be caused by the database closing the connection and the plugin not trying to reconnect again.
Since you said you have to "wait" for this to happen, I guess this just happens randomly over time without any interaction?
Yea, it just happens randomly over time
I get this as well - https://pastebin.com/raw/UDv5nyb1
Although, I'm testing for plugin conflicts that may be causing this.
Nevermind, there doesn't appear to be any plugin conflicts. I can reproduce this with only: LuckPerms, NickNamer, PacketListenerAPI, and PlaceholderAPI.
I've noticed the names not properly syncing between my servers (with MySQL & BungeeCord plugin utilized), it was likely this issue. Additionally, I have the skin feature disable yet when the names do sync, the inventories are refreshed with a noticeable delay upon joining.
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
This is still an issue that prevents me from using the plugin. I'll test it on 1.16.2 when it comes out.
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.