-
Notifications
You must be signed in to change notification settings - Fork 21
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
Purpur 1.21.4 - Player Name Changes, Database Cache Errors #2910
Comments
Hey! Thanks for reporting. Did you change the username in Mojang or using a third party plugin, i.e. Essentials' nick? |
I changed the username with Mojang |
Issue is also still happening on ChatControl-11.0.3-BETA version. |
Thanks for the info. This will be addressed when I'm back in office, thanks for your understanding and Merry Christmas! Until then you'd need to remove the db entry :/ |
Issue is also still happening on ChatControl-11.0.4-BETA version. |
Are you using MySQL?
Yes
Are you using a proxy?
Yes - Velocity
"/version ChatControlRed" - plugin version
11.0.1
Optional: Error log
https://pastebin.com/NjzCdBXx
ZIP of "/chc debug"
debug.zip
Steps to reproduce
ChatControl is unable to process Minecraft player name changes. I changed my name from MorkiePorkie to HeartKitties. I restarted the proxy, lobby, and towny servers. ChatControl gives an error message that that database is loading. This loading message never stops. I've also restarted my Minecraft launcher and Minecraft in general, issue is not client side. Additionally, other plugins are handling the name changes instantly and updating databases accordingly.
ChatControl gives an error message in the console that the database player is already cached. ChatControl is not automatically updating the database with the new player name. ChatControl is unable to handle the changes of player names. I do not want to manually remove a player from the database. This should be automatic. Please determine a fix for this issue. Please message me with any questions or concerns.
Thank you!
The text was updated successfully, but these errors were encountered: