You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[10:12:03 WARN]: FieldAccessException: Field index 0 is out of bounds for length 0
[10:12:03 WARN]: at ProtocolLib (10).jar//com.comphenix.protocol.reflect.FieldAccessException.fromFormat(FieldAccessException.java:49)
[10:12:03 WARN]: at ProtocolLib (10).jar//com.comphenix.protocol.reflect.StructureModifier.read(StructureModifier.java:247)
[10:12:03 WARN]: at ProtocolLib (10).jar//com.comphenix.protocol.events.AbstractStructure.getMultiBlockChangeInfoArrays(AbstractStructure.java:537)
That's what happens with ANY action with packet.getMultiBlockChangeInfoArrays(), no matter what you do.
I decided to upgrade from 5.3 to 5.4 dev, and it got even worse - now it's not even capable of packet.getBooleans() with a packet POSITION... old problem not fixed
The text was updated successfully, but these errors were encountered:
Field index 0 is out of bounds for length 0
[10:12:03 WARN]: FieldAccessException: Field index 0 is out of bounds for length 0
[10:12:03 WARN]: at ProtocolLib (10).jar//com.comphenix.protocol.reflect.FieldAccessException.fromFormat(FieldAccessException.java:49)
[10:12:03 WARN]: at ProtocolLib (10).jar//com.comphenix.protocol.reflect.StructureModifier.read(StructureModifier.java:247)
[10:12:03 WARN]: at ProtocolLib (10).jar//com.comphenix.protocol.events.AbstractStructure.getMultiBlockChangeInfoArrays(AbstractStructure.java:537)
That's what happens with ANY action with packet.getMultiBlockChangeInfoArrays(), no matter what you do.
I decided to upgrade from 5.3 to 5.4 dev, and it got even worse - now it's not even capable of packet.getBooleans() with a packet POSITION... old problem not fixed
The text was updated successfully, but these errors were encountered: