This is literally just internal studio plugin, we get it
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
tnavarts is stravants alter ego
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.
Very interesting! What would the benefit be of using a react-lua UI as opposed to making UI the usual way in studio?
Itâs really great that Editablemesh is 40% faster!!
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
This is very interesting! I really appreciate the info, and will look into this!
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.
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!
By that you mean time from clicking on something in toolbox to it showing up in the world?
Yes, especially with very large amounts of parts, such as maps and such.
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
Late for the discussion:
This is the first 2025E version of RĆblox.
Any update on âAdded support for rbxthumb ContentIds in AssetService:CreateEditableImageAsync
â from Release Notes for 654 | Documentation - Roblox Creator Hub?
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?
Is it possible to use the Roblox UI internal components for our games?
Iâve tried it couple months ago but I couldnât set-up the âcontextâ
I couldnât find anything specifically mentioning it, but does this fix editable-mesh occlusion culling issues?