I have recently discovered the wonders of ‘Print String’ as used to place text in the output log!
(behind the times, yes I know, anyway…)
But no matter what linear color I input into the command it always comes out grey in the output log.
To clarify, the color shows when on screen but does not when placed in the output log.
Is there a way to color the text in the output log, or is this intentional?
I think it is intentional.
yes it’s intentional
i think it would be great to have it as an option. I find it quite hard to find user messages in massive output log. If user msg were colored, its easier to spot them.
Devs, could we have this functionality ?
That BP node is in KismetSystemLibrary.cpp as “void UKismetSystemLibrary::PrintString()”
There, it calls UE_LOG with the logging levels “Log”, “Verbose”, and “VeryVerbose”. It’s the levels which color the log entries, so there isn’t a way to do this w/o a custom build - which is a ton of grunt work.
An alternative is to use the “Filters” option in the top left of the OutputLog and choose “LogBlueprintUserMessages”
Ok, so I want to intentionally enable this, because I can’t easily distinguish between what I have written and what Epic outputs. Guess I can’t because Epic doesn’t care that much about accessibility (seeing as UE5 reduced icon sizes and UI scaling is still broken)?
Epic don’t even seem to care in their new 5.2 log (enabled with “-NewConsole -Log” arguments). 
EDIT: Seems certain keywords get a color, like “warning” and “error”, but there should be an editor setting to enable the color from the nodes that I set as well!
You can start your print text with words:
Error:
Warning:
It will be colored to Red and Yellow respectively.
EDIT: Uh sorry haven’t noticed a last message…