The screen output to be correct, as in equal to that of running the server without any terminal multiplexer, as well as with tmux:
tmux
Purely alacritty with alacritty in $TERM
What behaviour is observed:
screen misinterprets the output somehow and breaks the output. This applies to both UTF-8 mode (-U option), as well as non-UTF mode (no -U).
Steps/models to reproduce:
Send a message with RGB colours to the console. The colours in the examples are #a2aeab and #ff681f. I used EssentialsX nicknames & chatted to get the colours into console.
Plugin list:
None are necessary, however for the sake of setting a good example:
[20:40:27 INFO]: This server is running Paper version git-Paper-498 (MC: 1.16.5) (Implementing API version 1.16.5-R0.1-SNAPSHOT)
[20:40:27 INFO]: Checking version, please wait...
[20:40:28 INFO]: Previous version: git-Paper-484 (MC: 1.16.5)
[20:40:28 INFO]: You are running the latest version
This only applies to the console; the log file and ingame chat are both correct.
This issue is rejected by the Paper team and is only present to let others know of the issue, such that someone else potentially PRs a workaround that must not affect the other correct cases.
What behaviour is expected:
The
screen
output to be correct, as in equal to that of running the server without any terminal multiplexer, as well as with tmux:tmux
Purely
alacritty
withalacritty
in$TERM
What behaviour is observed:
screen
misinterprets the output somehow and breaks the output. This applies to both UTF-8 mode (-U
option), as well as non-UTF mode (no-U
).Steps/models to reproduce:
Send a message with RGB colours to the console. The colours in the examples are
#a2aeab
and#ff681f
. I used EssentialsX nicknames & chatted to get the colours into console.Plugin list:
None are necessary, however for the sake of setting a good example:
Paper version:
Anything else:
This only applies to the console; the log file and ingame chat are both correct.
This issue is rejected by the Paper team and is only present to let others know of the issue, such that someone else potentially PRs a workaround that must not affect the other correct cases.