Feature Request #1768
Add queue for not (yet) handled packets due to missing information
Currently, when the server receives a CLIENT_UPDATE packet for a client id it does not know, it will discard the new information and request a CLIENT_INFO packet for the id in question.
This is the case with every packet that holds a client or company id.
Better practice would be to add the packet to a queue which gets re-handled once the respective info packet has arrived.
a possible solution for handling the queue would be
1HashMap <Integer, Queue<Packet>> clientQueue; 2HashMap <Integer, Queue<Packet>> companyQueue;