Skip to content
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

[BUG] Packet limit #104

Open
GIGABAIT93 opened this issue Aug 17, 2023 · 6 comments
Open

[BUG] Packet limit #104

GIGABAIT93 opened this issue Aug 17, 2023 · 6 comments
Labels
bug Something isn't working

Comments

@GIGABAIT93
Copy link

When I go to the server with mods, I get the error shown in the screenshot.
Changing the max-unknown-packet-length, max-single-generic-packet-length, max-multi-generic-packet-length, max-packet-length-to-suppress-it limit settings does not help.
There is no such error when disabling the plugin.
I suspect that the packet limit settings are not working. Perhaps it is worth adding a parameter that will disable this check altogether

Screenshots
зображення

@GIGABAIT93 GIGABAIT93 added the bug Something isn't working label Aug 17, 2023
@GIGABAIT93 GIGABAIT93 changed the title [BUG] [BUG] Packet limit Aug 17, 2023
@hevav
Copy link
Member

hevav commented Aug 17, 2023

This is not LimboAPI fault, the error is caused either by some mod, or by some Velocity plugin (send /velocity dump)

@GIGABAIT93
Copy link
Author

This is not LimboAPI fault, the error is caused either by some mod, or by some Velocity plugin (send /velocity dump)
When I remove the plugin there is no such error and everything works fine

@Hiradpi
Copy link

Hiradpi commented Sep 4, 2023

why every other plugin works fine ? this is limbo's fault please fix it

this is caused using via (rewind) tring to connect using 1.8 (bedwars) and the client cannot decode or parse the sent packet
image

I know it's not right to use via plugins on velocity servers but it's the best way to run bedwars server and there are a lots of bedwars servers out there
please fix this

@vovamod
Copy link

vovamod commented Sep 14, 2023

why every other plugin works fine ? this is limbo's fault please fix it

this is caused using via (rewind) tring to connect using 1.8 (bedwars) and the client cannot decode or parse the sent packet image

I know it's not right to use via plugins on velocity servers but it's the best way to run bedwars server and there are a lots of bedwars servers out there please fix this

Are you dump? Use Via plugins ONLY on backend. You make almost every data that is going through a proxy to main server go throught Via plugins which is a bad practice, come to your god damn senses and use plugins only as needed

@creaper3
Copy link

creaper3 commented Apr 6, 2024

I am also getting these issues when using forge. Changing limits doesn't fix anything. Works fine when I disable limboapi. Interestingly changing the IP address from 192.168.0.4:25566 to 0.0.0.0:25566 (while still connecting to the same server) shows a different packet limit.

@gass-ita
Copy link

Having the same issue trying to connect with a forge 1.20.1 client

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants