playerdata send packet
dinobossytnew opened this issue ยท 4 comments
Provide more info using this form:
- This issue is not solved in a development build
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Version Info
Provide your ProtocolLib install info with /protocol dump
through pastebin.
Additional context
Add any other context about the problem here.
Have the same error, here some datas:
Describe the bug
Sometimes if a player is changing the Server in my Network it get kicked with the error Message from above.
To Reproduce
Change from one Server to another inside a Bungeecord Network, if your unlucky, you get kicked with the error message.
Expected behavior
Not get kicked...
Version Info
https://pastebin.com/RKsBAdwg
Hope this helps to get this solved quickly.
Have the same error, here some datas:
Describe the bug Sometimes if a player is changing the Server in my Network it get kicked with the error Message from above.
To Reproduce Change from one Server to another inside a Bungeecord Network, if your unlucky, you get kicked with the error message.
Expected behavior Not get kicked...
Version Info https://pastebin.com/RKsBAdwg
Hope this helps to get this solved quickly.
Try to use dev build of ProtocolLib v5.1.1 from here:
[1.8-1.19.4]: https://ci.dmulloy2.net/job/
[1.20.*+]: https://ci.dmulloy2.net/job/ProtocolLib/669/
Notice for 1.20 and 1.20.1 users:
Please, use 1.20.2 to confirm your issue with ProtocolLib.
Why not the last build for 1.20.2?
Last build (673) have critical issue at this moment; #2601
We have some more Problems with 1.20.2 thats why we are not updating currently.
I changed the Protocollib Version back to 699.
The Problem on Testing is that this issue is rare, even after 30 switched i could not get it again.
I now will see if in the next days this issue is comming again with the 699 Version.