Closed Glucy-2 closed 11 months ago
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.
Hi, I pushed some commits to main, if you want you can already test if this fixed the issue.
Yes it's fixed, running great, thank you.
Thank you for the report and testing out the fix!
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 20Proxy:
player-info-forwarding-mode = "modern"
(invelocity.toml
)Server:
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: