perhaps just built into the 3 rather than new
if no color is sent, then just default, but if a color is sent, use that color
1 Like
Bump for implementation.
However, if you see this thread and are still waiting on this feature, maybe you could use like the suggested above with emojis. But with these emojis preceding a print specifically.
Hello World!
Hello World!
Hello World!
Hello World!
Hello World!
Hello World!
Hello World!
Hello World!
I use it like so,
print("🔵 Traceability| State Changed with"..tostring(Index)..". To: "..tostring(Value))
7 Likes
Bump! This would be extremely useful for debugging especially when handling masses of code. I’m working with OOP programming principles right now, so it’d be very convenient to have various colors labeling where things are happening and what they’re doing.
2 Likes
I support using those ANSI escape chars for this, or reserving extra characters on the range they’re using for the robux and premium icons.
A more verbose idea is either to support rich text, or a table with character locations.
3 Likes
Bumping, this would be super useful. It’s been 7 years, how do we still not have this?!?!?
4 Likes
Dang it’s been 7 years since I posted this! It might be worth mentioning that in the modern day, we have rich text which goes beyond what this post even described, but it’s still not accessible in the output!
9 Likes
It would be really cool if implemented!
1 Like
Maybe add support for RichText?
Though this will leave out studio’s output window.
12 Likes
Bump again, this would be super cool for my data saving and loading system to differentiate different prints. For example, a print that says “Connected to database” would be green, and the print that prints out the player’s data would be blue.
3 Likes
Bump, print with color would be great! Maybe a filter by color3 option for it as well in output. Debugging would be easier as (personally) I work on a lot of commissions and the output is insanely full. But to filter and immediately see it (or scroll until I find the color I put) would make it sooooooo much easier. This would be great and we already have color3s for text so why not output?
3 Likes
Bump this once more! The thing is we can’t even use ansi codes in terminal. It’s like roblox doesn’t want us to have more than 4 colors. Ansi codes, usage of Color3 in terminal outputs or rich text addition to console would be great.
2 Likes
fr, bump from me too!!!
hope an engineer reads this
2 Likes
bumpy bumpity bump
yes please do this!1!!!
my idea:
local LogService = game:GetService("LogService")
--[[ new function! LogService:Print(color: Color3, settings: {
Bold: boolean,
Italic: boolean,
Underline: boolean,
Strikethrough: boolean,
} | boolean, message: string)
parameters:
color: The color of the message
settings: Table with settings OR true which enables everything and false which
disables everything
message: The message to print
]]
LogService:Print(Color.fromRGB(0, 255, 0), false, "Hello there! :D")
6 Likes
Rich text is already great - could we have support for that? (w/o font size, that would be a mess)
1 Like
too much work just to print, color duplication, instead
local logger = LogService:Logger( -- all your settings go here )
logger.log('ThemeName which ya choose in settings', 'hello world')
2 Likes
bump I feel like if this was implemented one day, it would have an optional second parameter for color 3
print("Hello, World!", Color3.new(1, 1, 1))
1 Like
This wouldn’t work because prints can have as many parameters as you want. For example, the code you posted already “works”:
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.
3 Likes
Whoops I forgot about that. However like abcreator said, Plugin security would not be the way to go
1 Like
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” … )