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

Multiline chat messages are scrambled in legacy server versions #3343

Open
1 task done
bedwarshurts opened this issue Jan 4, 2025 · 2 comments
Open
1 task done

Comments

@bedwarshurts
Copy link

bedwarshurts commented Jan 4, 2025

  • This issue is not solved in a development build

Describe the bug
In legacy server versions (I tested on paperspigot 1.8.8) if you have protocollib and a plugin that hooks to it (tested with 2 different plugins) commands that output multiline chat messages result in the lines being scrambled

To Reproduce
Steps to reproduce the behavior:

  1. Use legacy server versions
  2. Install protocollib
  3. Install a plugin that depends on it (not all plugins result in this bug im not sure what exactly causes it, I tested with itsmyconfig and interactions)
  4. Use a command that outputs multiple lines
  5. Observe

Expected behavior
The lines get printed in order

Observed behavior
The lines get printed in random (scrambled) order

Screenshots
Here I am using the itsmyconfig plugin to showcase the issue. HOWEVER this bug happens with other plugins installed that hook to protocllib, I also tested with the "interactions" plugin.

Version Info
https://pastebin.com/6nV2PZb6

Additional context
No more context

@spring-dependency-management

That paper jar is from july 2015, why not use an old version of protocollib from 2015?
Could be beneficial for protocollib to drop support for these old versions to prevent breakage 🤔

@bedwarshurts
Copy link
Author

That paper jar is from july 2015, why not use an old version of protocollib from 2015? Could be beneficial for protocollib to drop support for these old versions to prevent breakage 🤔

I use a fork thats still being supported. Despite that, I will agree with you that using such a legacy version is not optimal. I just have a UHC server and my players want legacy world generation which I havent found a way to achieve in newer server jars.

I fully understand if the protocollib team doesnt wanna work on this. However since 1.8 is advertised as still being supported I thought reporting it was worth a shot.

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

No branches or pull requests

2 participants