Error in console: https://pastebin.com/dMp55TnS

Timings report: https://timings.aikar.co/?id=dd06da32ba574898a409a5ffd9b5339a

I installed ViaVersion today for the 1.15 release.

For what it's worth, this issue is happening again in 1.19 with the current viaversion and protocollib versions installed on paper 1.19-8.jar server. Sorry for bump if it's annoying anyone but this is exactly the same issue I'm fairly sure so figured would be good to have history on it.

For what it's worth, this issue is happening again in 1.19 with the current viaversion and protocollib versions installed on paper 1.19-8.jar server. Sorry for bump if it's annoying anyone but this is exactly the same issue I'm fairly sure so figured would be good to have history on it.

yes i too have the same issue with purpur 1.19... i am attaching the error message..
protocollib error.txt

For what it's worth, this issue is happening again in 1.19 with the current viaversion and protocollib versions installed on paper 1.19-8.jar server. Sorry for bump if it's annoying anyone but this is exactly the same issue I'm fairly sure so figured would be good to have history on it.

yes i too have the same issue with purpur 1.19... i am attaching the error message.. protocollib error.txt

Can't say anything about the issue of DeSinc because of missing information, your "issue" is just related to an outdated version of ProtocolLib. Use the latest development build from https://ci.dmulloy2.net/job/ProtocolLib/lastSuccessfulBuild/ to get 1.19 support :)

For what it's worth, this issue is happening again in 1.19 with the current viaversion and protocollib versions installed on paper 1.19-8.jar server. Sorry for bump if it's annoying anyone but this is exactly the same issue I'm fairly sure so figured would be good to have history on it.

yes i too have the same issue with purpur 1.19... i am attaching the error message.. protocollib error.txt

Can't say anything about the issue of DeSinc because of missing information, your "issue" is just related to an outdated version of ProtocolLib. Use the latest development build from https://ci.dmulloy2.net/job/ProtocolLib/lastSuccessfulBuild/ to get 1.19 support :)

!!!! I looked FOR MINUTES and didn't find anything anywhere, not on the github not on the mod page, WHAT!!
Anyway thanks mate for pointing me in the right direction 👍 wish they made it easier to find this page to get the dev builds but I suppose they don't want just anyone getting them

this is a known issue with via and protocol lib where if a plugin requests the entire buffer, this error occurs. been meaning to ask the via guys why that happens, will probably do so after the 1.15 update

Just had this issue linked to me, is there any example code for replicating this?

@MylesIsCool In this instance, it looks like it's caused by the plugin PacketLimiter, but realistically any listener with the option INTERCEPT_INPUT_BUFFER (or maybe ASYNC if that doesn't do the trick) should cause this behavior

Is there a ETA for this? Some people are using this to prevent protocollib based protection plugins from detecting their exploits and asking for cash to fix.

https://pastebin.com/NYfQqfNk

I got a similar error these days in the console

I also got this error

https://pastebin.com/ZY45Kz7a

same

This is my error:
https://pastebin.com/diVPbfXj

^ This is the plugin that sleeps the main thread for 5 seconds in onLoad() with loadbefore: ViaVersion
DebugViaVersion.zip

Steps to reproduce:

1. Fire up server with ProtocolLib, ViaVersion and custom plugin installed
2. Connect after server has binded to the IP, but before ViaVersion loads (you'll have plenty of time because of the custom plugin)
3. After successfully connecting, try re-logging or connecting with another client. You'll see that it doesn't work

Here's an interesting way of consistently reproducing the same error with Via, or probably any other injector, and ProtocolLib: Login with the client before Via has been loaded (for example by sleeping the main thread for a few seconds in a loadbefore to give a greater time window), and wait until you are connected. Any incoming packet from other clients trying to connect, as well as the first client after disconnecting, will throw the ClassCastException.

Tested this on a 1.8.8 Paper server with a 1.8.8 client, only PL, Via, and a plugin sleeping the thread before Via loads installed - this method in particular doesn't work on a 1.15 server however, since it does not handle connections before the server has properly loaded. In this sense, I'm not 100% sure if this leads to the same cause as given in the thread

Hello,
I'm also getting this error. I used @MedicOP method of re creating the error. It's accurate and I was able to re create the error. I was wondering if there is a fix for this or an eta on a fix?
Thanks, PrePay.

@kennytv @MedicOP thank you guys, was able to reproduce it locally. I'll look into a fix now