Colors in the output window

This wouldn’t work because prints can have as many parameters as you want. For example, the code you posted already “works”:

{2C04A79D-893C-4403-A2BD-94487A03122E}

If this feature was added in this way, it could break some people’s debugging.

The feature should be locked behind PluginSecurity and inside a method in LogService, such as LogService:PrintRich(...: string)!

3 Likes

It wouldn’t make sense to lock this behind PluginSecurity as a lot of use-cases for colored prints are in modules that’d be running in play mode.

4 Likes

Whoops I forgot about that. However like abcreator said, Plugin security would not be the way to go

2 Likes

This would definitely improve quality of life.

Like the OP said, it would be helpful to see at a glance which module or script your output is coming from without having to remark out feedback from everything else you’re not working on.

I would suggest a separate implementation of print ( printc maybe? ) that either took a BrickColor argument ( or even just a numeric index to a BrickColor ) , i.e. printc( 40, “your text” … )

Bumpity bump or whatever its called

Personally a fan of the richtext idea, as it wouldn’t cause the issue that blueberry has stated, and would also not require getting another service (which isn’t really that annoying, but why shouldn’t the functionalities of the print function be usable using just the print function?)

I need this yesterday.

It’s irritating knowing that warn() and error() both add to my games analytics, on top of that error() simply halts a script when I almost always don’t want it to.

Having the extra accenting on hand for when I’m using a large amount of printing would be a life saver. Additionally, it would make the console look way prettier for usage by regular users when reporting bugs (going back to the above issue of error() halting especially) because I could easily put in my own custom error handling and decorate it as needed (various colours meaning different actions being done, or different sides of the server/client boundary breaking)

If none of that is a good enough reason, you can’t exactly argue against just being able to put cool coloured ascii art in for anyone who looks in there.

tbh, it whould be really useful and, it dosent seem that hard to imploment, since the only thing you need to do is the same as print but, provide a Color to the TextColor3, and then, the same as print, the 2nd arg should be the string, done, not that hard, idk why roblox havent added it already

1 Like

Bumping this again because it’s long overdue and seems like such a basic feature. Why can’t we have this? It would make debugging and sorting our prints sooooo much easier.

And no, it should not be locked behind PluginSecurity or anything else. That would be dumb and defeat the entire point of the feature.

fr, like, ‘warn’ and ‘print’, is so boring like, what if we want debug, like, ‘blue’, ‘green’, ‘lime’, because, it whould be nicer to debug where it was fired and, whould make the console, atleast, useful, and, generaly, even I, a <17, can make a ‘printwithcolor’, but, Roblox cant? thats so, bs, like, its not hard, it whould only take like, 2 days, max, like, its easy, whould help devs alot, with debugging, and, def should not be PluginSecurity since, what is the danger of printing colored-text in the console?

even big exploits make their own functions to make this posible, since, they have access too the CoreGui, where the Console is stored

1 Like