Thanks for this tutorial. Really helped me while testing an update to my Editor Themes plugin! It now switches UI theme based on the script editor theme chosen. If anyone wants to try it out (and has enabled the flag), you can grab it here: https://www.roblox.com/library/1858434956/Editor-Themes
It’s pretty satisfying to see it all change together. If you haven’t enabled the flag for UI Theme then it just acts as usual, affecting only the script editor colours.
Here’s a quick video of it in action for those who don’t want to mess around with their Studio variables: https://youtu.be/mJf7rcjVlj4
I’m saying you should mind that stuff like that could happen any time you force a feature on, because you don’t know why it’s disabled.
If the dark theme currently had a ~1/150 chance to completely trash all of your AppData when you open Studio with it on, a detailed guide on how to enable it wouldn’t help.
Please beware of unintended consequences when changing Fast Flags on Roblox Studio. We do not encourage developers changing Fast Flags themselves for a variety of reasons. Here’s a topic that provides more details about what Fast Flags are and the dangers of altering them yourself: Warning About Developers Using Fast Flags
I can’t say anything about the first one since I don’t use widgets, but for the second one I can say that you can not change the color of that from within studio or by changing any settings in studio.(At least to my knowledge)
I don’t see why UI code would affect place data in studio, but I want to make sure before working on my game. I plan on keeping this FFlag enabled (my eyes love the dark theme).
You should not assume it is safe to toggle fflags. If you’re working on a particular game/file that you can’t afford to lose / get corrupted, then don’t have any fflags toggled while working on that file. Use at your own risk.
The concern lies more in FFlags that do stuff with data that is saved to the site.
I recall one time when Roblox was working on Color3 support for Parts. I had enabled the flag and saved changes to my place, and then the color data got corrupted. It is especially dangerous with stuff like DataStores.
Ultimately the point is this: Roblox has FFlags in place to guard against potentially faulty code. If you circumvent those protections, we cannot be held liable to any data loss or errors that you might run into. That doesn’t mean you are 100% guarenteed going to lose data if you enable something early, but just exercise caution if you don’t know what something actually does.
I’m not actually part of the Studio team so I can’t really speak on their behalf, I’m just providing information where I feel it would be helpful, based on what I know and what I’m allowed to talk about.
The dark theme is purely a visual feature, so at worst you might just run into a crash that somehow relates to it.
I’ve been using the dark theme for a few weeks now and I haven’t seen any serious/blocking problems with it, so it should be fine.
I wish I had my macbook right now to help you, have you tried viewing the package contents and creating the ClientSettings folder there? (Package contents of studio of course)
