LimboAPI
LimboAPI copied to clipboard
[BUG] Packet limit
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
This is not LimboAPI fault, the error is caused either by some mod, or by some Velocity plugin (send /velocity dump)
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
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
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
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
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
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.
Having the same issue trying to connect with a forge 1.20.1 client