booky
If anyone here still experiences these problems, please try using https://github.com/retrooper/packetevents/actions/runs/15746891009?pr=1251
> > If anyone here still experiences these problems, please try using https://github.com/retrooper/packetevents/actions/runs/15746891009?pr=1251 > > Same issue! > > ``` > [08:36:38 INFO]: LinsaFTW lost connection: PacketEvents 2.0 failed to...
@Bram1903 @rafi67000 @Alulom should be fixed, if you can still reproduce this please comment and i will take a closer look again
would be nice if someone could provide minimal reproduction steps
didnt realize it was a proxy-specific issue cant reproduce this on velocity with modern or legacy forwarding
I did only test with 1.21.11 server and 1.21.11 client, I'll test with a 1.21.10 server later today
I've reproduced the issue and it should be fixed now This was caused by our synchronized registries not "norming" registry key names and ViaVersion stripping the registry key vanilla namespace,...
please ensure you have an up-to-date version of packetevents (see https://ci.codemc.io/job/retrooper/job/packetevents/) and test which plugins causes this error message, this issue is not caused by packetevents itself
whats your backend server software + plugins?
The problem is that packetevents currently doesn't really support mixed lists with like vanilla does in recent versions Nbt list tags no longer have an assigned nbt type in vanilla,...