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
Color codes inside the console have stopped working for a while on my machine. I very well remember this
working correctly before, and it does work with other server platforms (e.g. Spigot).
Tested with commit be008ff. Perhaps this has been broken since a commit that upgraded the logging library, such as #859.
Alright, we may have to wait until a new jansi comes out (as I see some progress on similar issues related to colors in the latest dev release), or for Glowstone to be upgraded to jline3 (though I believe jline3 just doesn't support colors on Windows last I checked).
I found two workarounds for this issue on Windows:
1. Windows 10 has a registry key to enable ANSI escaping by default. A step-by-step guide can be found here.
In summary, setting the registry DWORD HKEY_CURRENT_USER\Console\VirtualTerminalLevel to 1 will enable ANSI escaping by default for CMD. In PowerShell, it appears to simply ignore escaping (just shows plain color). Note: the regkey may not exist by default, so you will have to create it yourself.
2. Use an alternative console emulator that supports ANSI escaping. My personal favorite is cmder.
Color codes inside the console have stopped working for a while on my machine. I very well remember this
working correctly before, and it does work with other server platforms (e.g. Spigot).
Tested with commit
be008ff
. Perhaps this has been broken since a commit that upgraded the logging library, such as #859.I am using Windows 10.
This is what I see in in CMD:
Similarly, in PowerShell:
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: