Skip to content
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

1.21(.1) players can't join in bungeecord. #983

Closed
ImZowi opened this issue Sep 8, 2024 · 1 comment · Fixed by #996
Closed

1.21(.1) players can't join in bungeecord. #983

ImZowi opened this issue Sep 8, 2024 · 1 comment · Fixed by #996
Labels
bug Something isn't working

Comments

@ImZowi
Copy link

ImZowi commented Sep 8, 2024

Describe the bug
When 1.21.1 players join to the server, this get kicked with "EncoderException : java.lang.IndexOutOfBoundsException: writerIndex(1673) + minWritableBytes(1) exceeds maxCapacity(1673): PooledSlicedByteBuf(ridx: 0, widx: 1673, cap: 1673/1673, unwrapped: PooledUnsafeDirectByteBuf(ridx: 1673, widx: 1673, cap: 1673)) @ io.netty.handler.codec.MessageToByteEncoder:125" because packetevents 2.5.0 in bungeecord. This only occurs with 1.21(.1) version, any other versions can join without problems.

Software brand
Bungeecord: NullCordX 3.8.7
Backend: Purpur 1.20.4

Plugins
Plugins: Apollo, AutoGeyserUpdate, Bungee-Reconnect, ChatSentinel, CommandForward, EaglerXBungee, Floodgate-bungee, LiteBans, LuckPerms-bungee, Matrix, nLogin, nuvotifier, packetevents-bungee, SkinsRestorer, tebex.

How To Reproduce
Join with any client with the version 1.21(.1) to the server.

@ImZowi ImZowi added the bug Something isn't working label Sep 8, 2024
@ImZowi ImZowi changed the title 1.21.1 players can't join in bungeecord. 1.21(.1) players can't join in bungeecord. Sep 8, 2024
@Giuseppecri
Copy link

I had the same problem as you you have to download an older version of bungeecord

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants