-
-
Notifications
You must be signed in to change notification settings - Fork 625
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
Player get kicked due to out-of-order chat when sending messages rapidly #909
Comments
Change message frequency in litematica settings. You can't do anything else, unless a dev implements a config setting that toggles checking signed-ness of messages. |
Line 134 in c9e0e14
This condition could be (!this.timeKeeper.update(instant) && !config.allowMessageSpam) e.g. check if order is not preserved AND the message spam setting is not enabled (e.g. message spam is not allowed)
|
It's not velocity that's doing the kick, so adding a config option in velocity would be useless. It seems that there is a race condition in the logic somewhere |
I have a feeling it has to do with some line in velocity using |
also getting this error in 1.19.2 |
Getting this error in 1.19.4&1.19.2 Paper, but this problem doesn't occur when don't connect to the server through Velocity. I think this problem happens when the chat & command messages are sent to the fabric server from Velocity. The timestamps of messages are disarranged, so the fabric server receives out-of-order messages and ticks the player out. Maybe there are some bugs in Velocity when dealing with a lot of messages at one time. |
you can use the tin3omod to ban the out-of-order |
Hello everyone. Sorry to bother I have the same issue. I see that the branch LeavesMC fixed this, could you please try to implement the same to paper or velocity? |
They didn’t fix it, they just tried to hack around it there is a pr which looks to change some of the processing around the chat stuff, I don’t have hardware to look into it, but, if you can compile velocity probably worth testing |
I'm having the same issue. I'm able to replicate it by sending a chat message then immediately sending a random command. Connected on 1.19.2 to a 1.20.1 server (only happens for 1.19.1-3 clients, not 1.19.4 or any other) |
In a paper fork called pufferfish, the issue is resolved, but I'd rather stick to using Paper/Velocity. |
Could you try the latest build? There is a pull request merge that can fix this error |
I will be able to try it probably tonight :) ! Thanks for the heads up |
Should have been resolved by #1042 |
Sorry if i wasn't able to test it right away, Had RAM problem with my server. I confirm that this fix is working for us too! We appreciate it a lot! :) Have a great day |
Velocity version:
3.1.2-SNAPSHOT-201
force-key-authentication
is true or false, the player will be kickedmodern
andnone
player info forwarding modeServer: 1.19.3, fabric with mods:
fabric-api
,fabric-carpet
,carpet-tis-addition
,fabricproxy-lite
Velocity log:
fabric server log:
When directly connect to the fabric server or use Waterfall as proxy (delete
fabricproxy-lite
mod), player won't be kicked due to out-of-order chatTo reproduce:
fabric-api
,fabric-carpet
,carpet-tis-addition
,fabricproxy-lite
carpet antiSpamDisabled true
to disable spamming checks on players3.1.2-SNAPSHOT-201
Velocity and start itlitematica
mod and paste a schematic (or maybe some other methods that can send more than about 50 messages per second)The text was updated successfully, but these errors were encountered: