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
Setup a Velocity server with player-info-forwarding-mode = "modern" in velocity.toml
Setup a fabric server with mods above
Copy content in forwarding.secret (generated by Velocity) and paste it in fabric server config/FabricProxy-Lite.toml's secret
Setup another server supporting Velocity's modern player info forwarding, can be a NanoLimbo, or another fabric server with FabricProxy-Lite. If you installed silk on this server, it will cause an infinite loop
Configure server addresses in velocity.toml
Start servers and velocity
Join
Switch to another server using /server
Switch back
You'll get kicked (or fallback to the server you switched first) : Internal Exception: java.lang.IndexOutOfBoundsException: readerIndex(1) + length(1) exceeds writerIndex(1): PooledUnsafeDirectByteBuf(ridx: 1, widx: 1, cap: 1)
The bug is in silk-network's mixin, here
Commenting the code solves the bug
Maybe conflicting with FabricProxy-Lite's mixin?
I don't know how to solve it elegantly, I know very little in Java and Kotlin
Thanks for the report, I am not entirely sure what is causing this, but it indeed has something to do with this mixin.
I will try some possible fixes - and I hope that velocity is not preventing custom packets in some way.
Enviroment:
Debian 12 (
Linux debian 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-1 (2023-07-14) x86_64 GNU/Linux
)Zulu Java 20
Proxy:
player-info-forwarding-mode = "modern"
(invelocity.toml
)Server:
mods:
To reproduce:
player-info-forwarding-mode = "modern"
invelocity.toml
forwarding.secret
(generated by Velocity) and paste it in fabric serverconfig/FabricProxy-Lite.toml
'ssecret
velocity.toml
/server
Internal Exception: java.lang.IndexOutOfBoundsException: readerIndex(1) + length(1) exceeds writerIndex(1): PooledUnsafeDirectByteBuf(ridx: 1, widx: 1, cap: 1)
fabric log:
The text was updated successfully, but these errors were encountered: