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

Right protocol limits for strings in the chat packet #3434

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Outfluencer
Copy link
Contributor

@Outfluencer Outfluencer commented Feb 3, 2023

For version below 1.16.5 the limit is short.max_value, as 1.16.5 and 1.16.4 has the same protocol number we limit below 1.16.4 I made a plugin too printing debug stuff in the chat everything was working on 1.19.3 but on 1.8.9 i got disconnected without an exeption because the error was in the client. So i think we should apply the limit in bungee directly

Edit:

https://wiki.vg/index.php?title=Protocol&oldid=16681#Chat_Message_.28clientbound.29 1.16.5 262144
https://wiki.vg/index.php?title=Protocol&oldid=16317#Chat_Message_.28clientbound.29 1.16.4 32767
1.8 32767

For version below 1.16.5 the limit is short.max_value, as 1.16.5 and 1.16.4 has the same protocol number we limit below 1.16.4
I made a plugin too printing debug stuff in the chat everything was working on 1.19.3 but on 1.8.9 i got disconnected without an exeption because the error was in the client. So i think we should apply the limit in bungee direktly
@md-5
Copy link
Member

md-5 commented Jun 10, 2023

Looking at the source code I think the wiki is wrong

@Outfluencer
Copy link
Contributor Author

But i got disconnected from the server because i received too long string you can look in the client yourself the limits in bungeecord are not correct

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants