tnavarts is stravant backwards, so maybe?
9 Likes
Sorry for the long post, I just wanted to document what I discovered in case they do remove this plugin!!
(P.S If any of these images look blank, they were either deleted or you gotta click them!)
I looked into storybook. It looks like some kind of development tool for coreUI, or something of the sort. A Storybook is some tree, and it looks like it works kinda similarly to making UI.
Clicking through these on the left shows a lot of UI you can find around studio, and roblox mayhaps as well I assume.
And yes, this plugin does appear to be internal. They seem to have not heeded the warning…
And on the right, you can find some sort of test field where it may show this GUI type, or something of the sort
Selecting “View Source” seems to open the ModuleScript that is associated with the Storybook you are previewing-- In this case, the ColorSystem
Clicking “Run Tests” seems to fail. (At least on this story book) with an error like this.
Lastly (What I found most interesting) is when you click “Explore”. It doesn’t do anything visually, but if you have the Properties window open, you will see it selected an invisible frame.
I found when it is selected, you can hit Ctrl + C to copy it, and paste it into a screenGui, which looks interesting.
Spam right-clicking and selecting “Go to reference object” on the parent of the selected invisible frame, and copying it into a screen GUI also lets you copy the entire storybook plugin UI
These properties here…
Look like they are testing configs, that emulate settings you can configure yourself in the roblox settings. Things like “Preferred Transparency” and “Reduced Motion” are both settings you can use.
Going through all the Storybooks I can is fun. There are a lot of interesting things to find! (all of the images below are what the story book looks like default. They have some interesting placeholders!!)
I clicked on this
And got this popup. Some assets, and a username. Maybe someone can look into the users if interested.
Once again, apologies for the long post~ You can find the plugin yourself in studio as of today, so feel free to look through it! It is very interesting.
26 Likes
This is literally just internal studio plugin, we get it 
10 Likes
Thanks for the feedback. I guess being fascinated with something and sharing what I found is excessive. I will be sure to try to appease to you more in the future
18 Likes
tnavarts is stravants alter ego
8 Likes
Hi friends :D. Yes, this is one of our internal plugins that we accidentally enabled for everyone :p. It’s a reference library for many of our internal UI components :).
Storybooks are a a concept borrowed from web development. If you’re interested in adopting storybooks for your own UI development, there are some great open source storybooks such as flipbook that you can check out!
Note that you can only make stories if you are using a UI library like react-lua or Fusion. Most of Roblox’s UI is built using react-lua. If you want to learn more about react-lua, I recommend checking out my guide (also published as a staff article).
I wouldn’t read too much into the stories that are listed in the plugin. Even if you are wanting to reverse engineer our UI as we’re in the middle of revamping a bunch of things so what you’re looking at may already be out of date.
26 Likes
Very interesting! What would the benefit be of using a react-lua UI as opposed to making UI the usual way in studio?
10 Likes
It’s really great that Editablemesh is 40% faster!!
9 Likes
I talk about it briefly in the introduction of the react-lua guide!
TLDR; it’s really nice way to add structure to large/complex/dynamic UIs. The main disadvantage is the relatively steep learning curve. Especially if you aren’t already familiar with the concepts or building UI with only code.
There’s absolutely nothing wrong with building UI the usual way in studio. I would consider looking into react-lua if
- you are already familiar with it and know that you want to use it
- you find your current UI code has become really complex and hard to update/maintain
12 Likes
This is very interesting! I really appreciate the info, and will look into this!
10 Likes
fyi, you were able to enable this plugin prior to them accidently enabling it for everyone by patching studio to be in internal mode, so none of this is new.
8 Likes
How would you have done it originally? I have never heard of this plugin before, and looking it up only shows community made plugins that do the same thing.
Can be done with external tools, but to me it doesn’t count as it wasn’t natively accessible to people as it is now. Interesting!
7 Likes
By that you mean time from clicking on something in toolbox to it showing up in the world?
7 Likes
Yes, especially with very large amounts of parts, such as maps and such.
10 Likes
also declarative ui frameworks generally help a lot with avoiding ui bugs, ie animations being weird because u clicked on the open/close button too fast and so now the menu u had open is now just stuck on screen, and other stuff like that
and are also pretty performant, although not as performant as just not using a framework and dealing with instances directly, but with a declarative ui framework its a lot easier to make performant ui code
6 Likes
Late for the discussion:
This is the first 2025E version of Rōblox.
5 Likes
Any update on “Added support for rbxthumb ContentIds in AssetService:CreateEditableImageAsync” from Release Notes for 654 | Documentation - Roblox Creator Hub?
1 Like
A pet peeve of mine with these release notes is how fixes are often put into the wrong category. Is this a mistake or is there something I’m missing?
4 Likes