When I replaced the latest version of LimboAPI with an older stable release, it started work as should. But when I switched back to the version 1.1.19 - nobody can join the server because of "timed out" kick. So this issue belongs only to the used version of LimboAPI, because even when I tried to disable other plugins, it was still not working good (and it stopped happening only when I disabled LimboAPI).
From the logs it's clear that the plugin tries to use NMS on connection and receives a NoSuchMethodError exception due to, as far as I know, Velocity does not have NMS classes, which means the plugin can't use it on Velocity so it deadlocks until exceeding timeout.
Describe the bug
When a player connects to a proxy server with the latest version (1.1.19) of LimboAPI, he gets kicked with "timed out" message.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Hm... Maybe the player shouldn't be kicked for "timed out"?
Screenshots
What happens when connecting to the server
Server Info (please complete the following information):
Additional context
When I replaced the latest version of LimboAPI with an older stable release, it started work as should. But when I switched back to the version 1.1.19 - nobody can join the server because of "timed out" kick. So this issue belongs only to the used version of LimboAPI, because even when I tried to disable other plugins, it was still not working good (and it stopped happening only when I disabled LimboAPI).
From the logs it's clear that the plugin tries to use NMS on connection and receives a
NoSuchMethodError
exception due to, as far as I know, Velocity does not have NMS classes, which means the plugin can't use it on Velocity so it deadlocks until exceeding timeout.