-
Notifications
You must be signed in to change notification settings - Fork 38
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
1.21 Inventory handling kick on Protocolize 2.4.0 #243
Comments
Hey, this should be fixed in the latest build of protocolize :) |
Hey. We updated, and we're observing some kicks related to looms now.
Relevant logs:
|
Hey, sorry for the late response. This issue should be fixed with the next release tomorrow morning on https://exceptionflug.de/protocolize |
Hi, just tested the version you provided and i get this error
|
I have the same issue. |
I still get the error with an anvil, this happens when trying to enchant something with a book in my case,
|
Same issue here. |
Getting this error as well:
|
Any update on this?
|
Same issue here, I'm running latest in velocity |
if you have |
I have the same problem, when riding a boat it bounces off, or when using ecoenchanct's special enchantment book it bounces off as well. I'm using |
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
You should not be kicked at all.
Screenshots
If applicable, add screenshots to help explain your problem.
We do not listen for any events related to items. Here is the exception:
Proxy environment
Please let us know which Proxyserver and what version you are running.
Please also let us know which other plugins are running on your proxy server.
Velocity 3.3.0 with Geyser. Bedrock players were not connected when this error occurred.
Minecraft versions used
If applicable, tell us the used minecraft client AND server versions that are involved in this problem.
Client: Java 1.21
Server: Java 1.21
The text was updated successfully, but these errors were encountered: