[BUG] Kicked with error on restart

[fredagsguf]

Describe the bug
When servers are restarting, where LimboReconnect should kick in - it kicks players.
Errors point to LimboAPI.

To Reproduce
Install plugins
Restart a server

Expected behavior
To not kick players

Screenshots
If applicable, add screenshots to help explain your problem.

Server Info (please complete the following information):

• LimboAPI 1.1.27-SNAPSHOT, downloaded from https://github.com/Elytrium/LimboAPI/actions/runs/15980525021

• LimboReconnect 1.1.7

• /velocity dump link https://pastes.dev/UGnRyPTvOV
  Client error once kicked: https://pastes.dev/eOlXyoTfpa

Additional context
Kicking players when LimboReconnect limbo is started.

[UserNugget]

LimboReconnect has several builds of 1.1.7, can you try to reproduce this issue with the latest dev-build?

[fredagsguf]

LimboReconnect has several builds of 1.1.7, can you try to reproduce this issue with the latest dev-build?

Seems to work on the latest "dev" build, i just didn't think dev builds were to be used for production.

Anyway i got a strange error one of the times i tried to test the reconnecting when a backend server is restarting:

[17:17:44 INFO]: [connected player] Laukage (/127.0.0.1:51308) has disconnected: An internal error occurred in your connection.
[17:17:44 ERROR]: [connected player] Laukage (/127.0.0.1:51308): exception encountered in com.velocitypowered.proxy.connection.client.ClientPlaySessionHandler@7bfc05b
java.net.SocketException: Connection reset
        at java.base/sun.nio.ch.SocketChannelImpl.throwConnectionReset(SocketChannelImpl.java:401) ~[?:?]
        at java.base/sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:434) ~[?:?]
        at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:255) ~[proxy.jar:3.4.0-SNAPSHOT (git-e9940713-b522)]
        at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1132) ~[proxy.jar:3.4.0-SNAPSHOT (git-e9940713-b522)]
        at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:350) ~[proxy.jar:3.4.0-SNAPSHOT (git-e9940713-b522)]
        at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:152) ~[proxy.jar:3.4.0-SNAPSHOT (git-e9940713-b522)]
        at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.handle(AbstractNioChannel.java:445) ~[proxy.jar:3.4.0-SNAPSHOT (git-e9940713-b522)]
        at io.netty.channel.nio.NioIoHandler$DefaultNioRegistration.handle(NioIoHandler.java:383) ~[proxy.jar:3.4.0-SNAPSHOT (git-e9940713-b522)]
        at io.netty.channel.nio.NioIoHandler.processSelectedKey(NioIoHandler.java:577) ~[proxy.jar:3.4.0-SNAPSHOT (git-e9940713-b522)]
        at io.netty.channel.nio.NioIoHandler.processSelectedKeysOptimized(NioIoHandler.java:552) ~[proxy.jar:3.4.0-SNAPSHOT (git-e9940713-b522)]
        at io.netty.channel.nio.NioIoHandler.processSelectedKeys(NioIoHandler.java:493) ~[proxy.jar:3.4.0-SNAPSHOT (git-e9940713-b522)]
        at io.netty.channel.nio.NioIoHandler.run(NioIoHandler.java:470) ~[proxy.jar:3.4.0-SNAPSHOT (git-e9940713-b522)]
        at io.netty.channel.SingleThreadIoEventLoop.runIo(SingleThreadIoEventLoop.java:204) ~[proxy.jar:3.4.0-SNAPSHOT (git-e9940713-b522)]
        at io.netty.channel.SingleThreadIoEventLoop.run(SingleThreadIoEventLoop.java:175) ~[proxy.jar:3.4.0-SNAPSHOT (git-e9940713-b522)]
        at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:1073) ~[proxy.jar:3.4.0-SNAPSHOT (git-e9940713-b522)]
        at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[proxy.jar:3.4.0-SNAPSHOT (git-e9940713-b522)]
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[proxy.jar:3.4.0-SNAPSHOT (git-e9940713-b522)]
        at java.base/java.lang.Thread.run(Thread.java:1583) [?:?]
[17:17:44 INFO]: [server connection] Laukage -> lobby has disconnected

[UserNugget]

1. LimboReconnect dev-builds has protocol changes only, so should be stable enough.

2. Most likely caused by too-fast restart.
   By default LimboReconnect wait for 2 seconds before trying to reconnect the player. (see join-delay in the config)