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
EDIT: The command registry was a misconfiguration of another plugin, but this console error is still happening. Doesn't seem to cause any major issues though. Just leaving this up incase it's something anyone cares to look into.
Describe the bug
PacketEvents throws an exception while handling registry synchronization when a player connects to a PicoLimbo server through Velocity. The error occurs during the configuration phase and results in the player STILL connecting to the PicoLimbo server, but command registration doesn't seem to work at all.
The exception indicates a failure to read the minecraft:timeline registry, caused by an UnsupportedOperationException inside PacketEvents.
Main Backend: Paper (latest version supporting Minecraft 1.21.11 / 26.1)
Limbo server (Error appears when moving player to here): PicoLimbo (Docker image)
Plugins
Proxy (Velocity):
PacketEvents
TAB
Velocity Scoreboard API (channel injection present in stacktrace)
If needed, I can provide a full plugin list.
How To Reproduce
Start a Velocity proxy with PacketEvents 2.12.0 installed
Connect a Paper backend server
Configure PicoLimbo as a fallback/limbo server
Join the proxy with a modern Minecraft client (1.21.11 / 26.1)
Trigger connection to PicoLimbo (e.g., during server switch or fallback)
Observe console error.
Expected behavior
PacketEvents should properly handle or safely ignore the minecraft:timeline registry during synchronization without throwing an exception or preventing command registration.
Screenshots/Files
Relevant stack trace:
[WARN]: PacketEvents caught an unhandled exception while calling your listener.
java.lang.IllegalStateException: Error while reading registry minecraft:timeline
...
Caused by: java.lang.UnsupportedOperationException
at StaticAttributeType.getValueCodec
Multiple plugins inject into the Netty pipeline (TAB, scoreboard API), but even after updating them to latest releases - error still occurs. It seems PacketEvents is the source of the exception (Or possibly an issue with PicoLimbo, but this was not happening before moving to 26.1 versions of PacketEvents and PicoLimbo).
EDIT: The command registry was a misconfiguration of another plugin, but this console error is still happening. Doesn't seem to cause any major issues though. Just leaving this up incase it's something anyone cares to look into.
Describe the bug
PacketEvents throws an exception while handling registry synchronization when a player connects to a PicoLimbo server through Velocity. The error occurs during the configuration phase and results in the player STILL connecting to the PicoLimbo server, but command registration doesn't seem to work at all.
The exception indicates a failure to read the
minecraft:timelineregistry, caused by anUnsupportedOperationExceptioninside PacketEvents.Software brand
Plugins
Proxy (Velocity):
If needed, I can provide a full plugin list.
How To Reproduce
Expected behavior
PacketEvents should properly handle or safely ignore the
minecraft:timelineregistry during synchronization without throwing an exception or preventing command registration.Screenshots/Files
Relevant stack trace:
Full stack trace available here: error.txt
Additional context
minecraft:timeline) introduced in recent versions.