-
-
Notifications
You must be signed in to change notification settings - Fork 180
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
Payload may not be larger than 32767 bytes #3450
Comments
I've encountered the same problem with the mod version:
|
I just encountered this in ATM 8 as well. |
Confirmed, just hit bug as well in ATM 8. |
Also just encountered the bug in ATM8 (with various Items such as Create Waterwheels and Supplementaries Clock Block). |
Same issue in Yao Pack 3 |
Getting this in ATM9 aswell, while trying to craft either a chest or a clock |
Same issue in Vault Hunter 3rd Edition when "Using the auto-populate feature (of JEI?) to put the cover recipe into the crafting grid." Running Refined Storage version 1.10.4 on Minecraft 1.18.2 |
This Bug/Error will continue in ATM 9 ..... When i make the Powered Spawner on the Mod EnderIO i'll be kicked from the server |
same happens here on a self made pack on 1.20.1, but it only happens with recipes that include planks so i guess maybe it's something related to the big number of planks variations that is created by mods like chipped and biomes oh plenty? (both are present on my pack, but i'm not sure if it's related in any way) edit: adding the Packet Fixer mod fixed it! |
Describe the bug
Using JEI to + click recipe for cover into crafting grid kicks player out of server. The result is a io.netty exception about payload size. The same feature can auto populate and craft the cover using a normal crafting table without issue.
How can we reproduce this bug or crash?
What Minecraft version is this happening on?
Minecraft 1.19.2
What Forge version is this happening on?
43.2.0
What Refined Storage version is this happening on?
1.11.4
Relevant log output
The text was updated successfully, but these errors were encountered: