It's possible for a packet's responsible queue to be incorrectly tracked.

2018-08-13 20:30:05 -04:00
parent e4e1b5b4fe
commit d0e2ad194f
1 changed files with 2 additions and 2 deletions
@@ -447,10 +447,10 @@ public abstract class AbstractTeamspeakClientSocket
        if (responsibleQueue != null) {
            responsibleQueue.put(
-                    packet.getHeader().getPacketId(),
+                    counter.getKey(),
                    response = new PacketResponse(
                            networkPacket,
-                            sendQueue,
+                            responsibleQueue,
                            networkPacket.getHeader().getType().canResend() ? 30 : 0
                    )
            );