You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
Spark link
null
Expected behavior
null
Observed/Actual behavior
≥ purpur-1.20.1-2020 console colors are not available
1.20.1-2019

1.20.1-2020 ~2022

Steps/models to reproduce
null
Purpur version
Console color available version: ≤1.20.1-2019
Console color unavailable version: ≥1.20.1-2020
Agreements
Other
No response
The text was updated successfully, but these errors were encountered: