PlayerListPacket issue with +70 players single instance

[junior badger]

When we reach an amount of 70 players, waterdog starts kicking with the next reason to each player join because the software sent many entries on the PlayerListPacket.

[junior badger]

I maded this code to do tests without players

i tried with 100 and not problem, but my server as minimum have 300

fixed it using Player#getSession().sendPacketSync, but obviously it is bad for performance

[junior badger]

And using Utils#splitArray

[flint eagle]

Just for the PlayerListPacket?

Wait.. is it a waterdog or a pnx problem?

[junior badger]

Both

But mainly for waterdog, they cant receive that packet because is very big

So to prevent that, split the packet and split the entries to send it sync to prevent make it as batch

[junior badger]

We got the same issue on pmmp due to the amount of entries🤌

[flint eagle]

You can split the packet?

Could you send the code for that?

[real seal]

The PlayerList packet is like an update packet. You specify the type (add/remove) and then create entries of players which should be added or removed

We just need to reduce the entries of a single packet

[junior badger]

Yep but if you add the packet to the queue, it is sent into a batch, so same issue, you need send it inmediatly

[summer quail]

waterdog has a lot of problems