-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
1.21.1: Reloading ChatControl with /chc rl will sometimes cause it to freeze #2923
Comments
It's either your database is too far away from the minecraft server or your network was slow, either way I can move these ops async but it will not solve the issue. Try looking into if you can add some driver flag to the Database.Line key to resolve the throttling, see if you find something on google. |
I reloaded ChatControl a few times today and it was fine, but then it started freezing the server again. I'll try looking into the driver flags. |
Upon updating to v11.0.4 I get the following error: https://pastebin.com/3q7ggmZv. I tried changing it to |
I apology for the issue, this should be fixed in today's release. I have also seen some other sentry reports from you, please open a separate ticket if you will still be getting "Cached player not found" or similar with steps to reproduce, thanks!! Matej |
Are you using MySQL?
Yes
Are you using a proxy?
Yes - BungeeCord
"/version ChatControlRed" - plugin version
11.0.3-BETA
Optional: Error log
https://pastebin.com/9EpibEXD
ZIP of "/chc debug"
debug.zip
Steps to reproduce
ChatControl was reloading fine before, until I tried adding a variable to the
List.Format
section insettings.yml
to see if it would work ({player_vanished_colored}
). It didn't work, so I reverted to{player_vanished}
, then did/chc rl
. Upon doing this, the server froze for about 15 seconds, then the plugin was reloaded and the change was applied. This has also happened to me a few other times when trying to add certain variables to my formats.You should be able to reproduce it by adding in a variable to the
List.Format
section ofsettings.yml
.The text was updated successfully, but these errors were encountered: