-
-
Notifications
You must be signed in to change notification settings - Fork 262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SPAWN_ENTITY listener in 1.19.4 doesn't work #2244
Comments
It seems like the AddEntity packet is now bundled in ClientboundBundlePacket. It would be nice if we could fire an event for each packet in the bundle |
In my own plugin I made it listen for bundles by default and fire a listener + monitor event for every packet inside the bundle. For cancelled packets the bundle packet is modified to remove the iterated packet. If all packets are cancelled it cancels the bundle packet itself. Pretty much all spawn packets, map packets, etc. are now inside bundles. Having such a feature in protocollib is pretty much essential as otherwise plugins will break. The algo for it isn't too complicated either but its more of a hack atm. Having every plugin register a Bundle listener and modify the packet themselves would be horrible for performance. I hope this gets added as an option or default for newly registered listeners. |
I should also clarify that the ProtocolLib build 616 does not support listening to the Bundle packet at all (it is not in this enum nor can you use the ClientboundBundlePacket packet class with fromClass(), throws because its null) Currently I dont use protocollib at all for packet handling and print a warning until this is fixed, as not even this workaround of listening for the bundle packet works because of it. |
Describe the bug
Using the latest development build. I also tried the WIP PR for 1.19.4, still doesn't work.
To Reproduce
Steps to reproduce the behavior:
Version Info
/protocol dump
https://gist.github.com/romanalexander/cf77effa4807f82b094909b90113fcb9
Server version Paper
Additional context
Logs from listening to all send/receive packets:
The text was updated successfully, but these errors were encountered: