booky

please try the latest packetevents snapshot build on both your proxy and your backend server

I can't reproduce this when switching servers on a velocity proxy (with AntiHealthIndicator installed) Please replace your packetevents plugin with the following jar which contains more error logging: https://github.com/booky10/packetevents/actions/runs/9305783370/artifacts/1553109827 (built...

@jordoncodes @IkyMax Please replace your packetevents plugin with the following jar which contains more error logging: https://github.com/booky10/packetevents/actions/runs/9494611327/artifacts/1596816328 (built by github actions, use the one without "-default.jar" or "-sources.jar") Then try...

The build of packetevents logs every error, you can safely ignore the `io.netty.channel.StacklessClosedChannelException`-messages This just means some plugin (or packetevents itself) tried to kick the player more than once

I've fixed the incorrect sources link for now, fixing the redirect isn't a high priority as we want to transfer the repository to another organization anyway

If you dont shade, dont call the packetevents init methods Also make sure that packetevents is part of your plugin.yml dependencies

Yes. @retrooper this should be added to the docs. The whole "Creating Your PacketEvents Instace" page only applies when shading.

@MIKAZE3 please send the actual stacktrace and ensure packetevents is up-to-date

Does this error still occur with the latest version of packetevents?

@SergioK29 are there any other errors? do you have any other plugins installed? also see the comments above, they may solve your issue