[BUG] Player cannot join the server after /velocity reload

[BestMark]

Describe the bug
A clear and concise description of the bug.

To Reproduce
Steps to reproduce the behavior:

1. Use /velocity reload command

Expected behavior
Players cannot join the server after /velocity reload

Server Info (please complete the following information):

• All Limbo plugins versions: latest Velocity-CTD and LimboAPI from here

Additional context

[18:43:18 ERROR] [limboapi]: Failed to handle GameProfileRequestEvent
java.lang.ClassCastException: class com.velocitypowered.proxy.connection.client.InitialInboundConnection cannot be cast to class com.velocitypowered.proxy.connection.client.LoginInboundConnection (com.velocitypowered.proxy.connection.client.InitialInboundConnection and com.velocitypowered.proxy.connection.client.LoginInboundConnection are in unnamed module of loader 'app')
        at net.elytrium.limboapi.injection.login.LoginListener.hookLoginSession(LoginListener.java:122) ~[?:?]
        at net.elytrium.limboapi.injection.event.EventManagerHook.lambda$onGameProfileRequest$0(EventManagerHook.java:77) ~[?:?]
        at java.base/java.util.concurrent.CompletableFuture$UniAccept.tryFire(CompletableFuture.java:739) ~[?:?]
        at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:531) ~[?:?]
        at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2206) ~[?:?]
        at net.elytrium.limboapi.injection.event.EventManagerHook.onGameProfileRequest(EventManagerHook.java:93) ~[?:?]
        at com.velocitypowered.proxy.event.UntargetedEventHandler$EventTaskHandler.lambda$buildHandler$0(UntargetedEventHandler.java:42) ~[velocity.jar:3.5.0-SNAPSHOT-git-5e7b36bc]
        at com.velocitypowered.proxy.event.VelocityEventManager.fire(VelocityEventManager.java:587) ~[velocity.jar:3.5.0-SNAPSHOT-git-5e7b36bc]
        at com.velocitypowered.proxy.event.VelocityEventManager.lambda$fire$5(VelocityEventManager.java:576) ~[velocity.jar:3.5.0-SNAPSHOT-git-5e7b36bc]
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1090) ~[?:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614) ~[?:?]
        at java.base/java.lang.Thread.run(Thread.java:1474) [?:?]

[WouterGritter]

This is actually a bug in upstream LimboAPI, I have opened a PR to fix this upstream: Elytrium#256

If this doesn't get merged in a day or so, I'll early-merge this here.

[R00tB33rMan]

Resolved!