-
Notifications
You must be signed in to change notification settings - Fork 70
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
My players are getting kicked when I'm using ProtocolSupport #355
Comments
The players are getting that when they are < to 1.9 |
Do you mean players running a 1.8 client? |
Yes. |
I think it can affect the most olders versions for 1.7, etc. I tested only for 1.8.x. |
I thinked by doing the test it was due to the usage of the shield ? It does only with the plugin. |
Any solutions for this ? |
What version of OldCombatMechanics are you running? |
The latest |
That is completely meaningless. I would need the version printed when you run |
It's the version 1.7.4. I downloaded it on Spigot. |
We believe this is a bug in ProtocolSupport. Where did you get the information that it is an OldCombatMechanics bug? |
The 1.8 player have done a right click @I-Al-Istannen and the 1.8 player has been kicked. (sorry for my bad English) |
I have done the same and nothing happened. The shield state was (nearly) properly synced. What items did you hold in your hand? |
PaperSpigot 1.14.4 |
I don't tested Players < to 1.8.9, but in 1.8.9, it affect. |
I am on I am on I used I am using your OCM config file. I am not being kicked and do not experience any issues. Do you do anything differently? |
No, Maybe with the plugin ProtocolSupportStuff ? |
I have the version 4.29-dev of ProtocolSupport. |
What is the build number? |
Nope, no changes. Looks like a weird issue on your side. Can you try this build: It will output a few |
[11:19:09 INFO]: @nico Got packet class: class com.comphenix.protocol.events.PacketContainer PacketContainer[type=BLOCK_PLACE[class=PacketPlayInBlockPlace, id=45], structureModifier=StructureModifier[fieldType=class java.lang.Object, data=[private net.minecraft.server.v1_14_R1.EnumHand net.minecraft.server.v1_14_R1.PacketPlayInBlockPlace.a, public long net.minecraft.server.v1_14_R1.PacketPlayInBlockPlace.timestamp]]] [11:19:09 INFO]: x9nico lost connection: Internal Exception: java.lang.IllegalArgumentException: You must pass a 'Packet' object! [11:19:10 INFO]: x9nico has left the server! |
Can you also post the ones when a player connects:
|
[11:22:02 INFO]: Channel handlers: |
But I think the error comes from Protocollib. PacketContainer are in Protocollib ! |
Yea, it sees a ProtocolLib structure instead of an NMS packet. That's a new one... Might be due to the position of the listener in the chain it printed. What plugins you use require/use protocol lib? |
For AuthMe Reloaded. |
And the remove of ProtocolLib does error with ProtocolSupport. |
Not sure what you mean with that. The only difference in the handler chain seems to be that I have a Your error sounds a bit weird. I will later try AuthMe Reloaded and see if I can reproduce the error. If not, you'd probably need to remove auth me, protocollib, via version and ProtocolSupport in that order and see when it starts working... I will be away for a few hours, a christmas market is calling :) Enjoy your day and I will talk to you later :) |
I have a lots of error with ProtocolSupport when I don't have ProtocolLib. |
I can not reproduce it. I also do not get any errors from ProtocolSupport without ProtcolLib. Sounds like there is something else amiss in your configuration? Can you try ProtocolSupport, ProtocolLib, ViaVersion and OCM on an otherwise fresh "install" of Paper 1.14.4 and see if the problem persists? I am bit out of things I could do on my end, it looks like a configuration or other issue on your end at the moment. |
Hi, the problem persist. |
Can you do what I suggested in the previous post?
There isn't much I can do at the moment, as I am unable to reproduce the problem. |
I tried, and the problem is solved. |
(I have still the problem on my 1.14.4 Paper Server) |
I am sorry, but I can not debug what I can not reproduce at all. Based on your descriptions it sounds like an issue with the configuration / plugin selection on that specific 1.14.4 server. Can you see whether you can reproduce it on the fresh server by copying over your plugins one by one (or copy half of them, see if the error occurs, copy the other half if not and so on) If that does not work, you could zip/tar/whatever your server up (except for the world folders) and send it to us. Either by posting it here if it is not remotely sensitive or via a DM on Discord / per E-Mail. If I can reproduce the error with that zipped server, I might be able to effectively debug it. |
Hello, |
With a heavy heart I created yet another account at some random website, I pray to god that the website isn't as trustworthy as it looks. |
I added you as Buyer. |
Thanks for that. I found the error, but sadly it is in ProtocolSupportStuff. I will add a not ideal mitigation for the OCM crash, but ProtcolSupportStuff should fix the error on their side as well. The commit will probably land in my fork this hour, then I will make a PR which will need to be reviewed and merged by Rayzr or kernitus and then a dev build will be available from the CI. |
Thanks you :) |
Thanks you, the problem has been resolved. |
Info
Problem Description
The developers of ProtocolSupport has told me of it wasn't an error from them.
The text was updated successfully, but these errors were encountered: