Studio script editor not highlighting strings unless unfinished

Yep i’m having the same issue

This issue is also occurring for me. Very confusing when reading anything. Makes my scripts go from unreadable to pure chaos.

I know this is probably getting annoying hearing everyone saying “It’s happening to me too” but I feel as if this is very disrupting and annoying, so it should be fixed ASAP.

It’s also happening to me aswell as you can see below:

Highlighted Strings

After Update

It’s very confusing and unsettling to have to take the time to look at a script without string highlighting, especially if it’s a script you’re not used to if you’re doing code review for someone else.

i have this issue too.
this is confusing

How does an issue like this not get caught before reaching production? This seems like it would be extremely obvious to anybody who uses Studio to program, and I know for a fact people at Roblox use it.

So, what gives?


Hey @Iron_Bard, thank you for bringing this up! We’re aware of the issue and have a fix internally that will be pushed out in 1-2 weeks


I can confirm this is happening to me on my Macbook Pro 2017 15"

I noticed it after it updated yesterday and I thought it was a local cache thingy. When I remove one quote, it shows the string.

Highlighting in general has changed a lot and self is not highlighted anymore.

I am doing it on a new place, on a virtual machine and the bug properly replicates.
I don’t think this is a game-breaking bug.

1-2 weeks? That’s quite long of a time… This is going to destroy workflows for me and other developers. This is pretty much critical at this point. If this could be expedited, that would be very much appreciated. Thank you!

I understand it’s a lot more complicated than this, but anything to speed this would be very nice.

Edit: I’m not the only one who things this is a major issue:

Please don’t make us wait 1-2 weeks, it will destroy out workflows.


This is unacceptable. This is disastrous to work with - we cannot keep putting up with these ‘minor’ issues that literally impact work flows immensely. I work with config modules that are literally just dictionaries, and this change made it IMPOSSIBLE to read for me and my team - this is just one of the many issues I have. We cannot expect to put up with this stuff especially for 1-2 weeks, something needs to be done, whether it be a revert or an immediate fix.


No offense but that’s completely unacceptable. You can’t just push out an obviously broken thing that affects every programmer on the platform and go “okay we’ll fix it in a week or two”.

I ask again: How did this happen? Why did nobody notice this before it reached production? Why was it not behind a flag that could be easily reverted?


A temporary, albeit “half fix” is to change the “text color” to your string color preset.


This will also turn all text “string colored”, but if you can deal with it, this works.

1 Like

This should be fixed now (after a Studio restart).


Can confirm it’s fixed for me now.

Thank you!


Same here. That pretty green text is back. Thank you @zeuxcg and the team for the expedited fix.


Looks like it was actually behind a flag!

1 Like

…I guess my followup would be why would that take 1-2 weeks to flip.

1 Like

We’ve reverted a flag that had a regression. The 1-2 weeks was to send a patch in the next release, really sorry for the inconvenience everyone


Sorry for the earlier miscommunication. I didn’t realize we could fix this by flipping a flag, and I didn’t recognize how serious of an issue it is


This is still happening to me.

I made 2 threads about this problem.

Can you check what version of studio you are on? You can find this by going to File > About Roblox Studio