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

Console colors are not available [≥1.20.1 - 2020] #1402

Closed
4 tasks done
shuiqing2046 opened this issue Jul 29, 2023 · 3 comments
Closed
4 tasks done

Console colors are not available [≥1.20.1 - 2020] #1402

shuiqing2046 opened this issue Jul 29, 2023 · 3 comments
Labels
invalid Missing/invalid data upstream Issue is caused by or better fit for upstream (Paper, Spigot, etc.)

Comments

@shuiqing2046
Copy link

shuiqing2046 commented Jul 29, 2023

Spark link

null

Expected behavior

null

Observed/Actual behavior

≥ purpur-1.20.1-2020 console colors are not available

1.20.1-2019
IMG 20230730024417

1.20.1-2020 ~2022
IMG 20230730024620

Steps/models to reproduce

null

Purpur version

Console color available version: ≤1.20.1-2019

Console color unavailable version: ≥1.20.1-2020

Agreements

  • I am running the latest version of Purpur available from https://purpurmc.org/downloads.
  • I have searched for and ensured there isn't already an open issue regarding this.
  • I ticked all the boxes without actually reading them
  • My version of Minecraft is supported by Purpur.

Other

No response

@granny granny added invalid Missing/invalid data upstream Issue is caused by or better fit for upstream (Paper, Spigot, etc.) labels Jul 30, 2023
@granny
Copy link
Member

granny commented Jul 30, 2023

    • I ticked all the boxes without actually reading them
  1. spark link is required for a reason
  2. this is an upstream issue, but i've pushed a hotfix for purpur in the mean time while we wait for a proper fix from upstream 41b121b

@granny granny closed this as completed Jul 30, 2023
@Huge-mistake
Copy link

KyoriPowered/ansi#29
PaperMC/Paper#9546
Shouldn't this be a mistake, it's intentional?

@BillyGalbreath
Copy link
Contributor

I agree, it is a mistake for Paper to be making those kind of assumptions based on a flimsy environmental variable that has proven for over 30 years to be unreliable for determining color support. At least they could have assumed the opposite where most terminals in 2023 can and do support the full range of 24bit colors, not 16 or none.

For those that want their true 24bit colors back and happen to be using one of terminal softwares that do not set the environmental variable the way paper team is assuming it should be, you can simply add the net.kyori.ansi.colorLevel system property flag to your startup script. For example:

java -Dnet.kyori.ansi.colorLevel=truecolor -jar purpur.jar nogui

truecolor will get you the full 24 bit colors. If you're in the 1% of users with a terminal that doesn't support 24bit colors there are also indexed256 and indexed16 values to that flag to get you 256 and 16 colors, respectfully, rather than being forced into a none value with the recent paper/kyori changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid Missing/invalid data upstream Issue is caused by or better fit for upstream (Paper, Spigot, etc.)
Projects
None yet
Development

No branches or pull requests

4 participants