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?
i see it and I’m not staff, any clue why it popped up?
Last year, I imported a multi-sample chiptune beep instrument and was quickly disappointed by a bug, where the engine would play the full sound from the beginning for specific sample splits, even though its loop and playback regions were being set correctly…
I think the issue was that the Properties pane rounded the sound length up and you set the end of the loop region to that. A friend of mine did that recently and we had to lower the loop region end to a tiny fraction of a second before the actual sound length.
Glad that won’t be necessary anymore!
Yep! The bug was similar to what @Bergan mentioned.
There’s some number of samples in a file; so e.x. a 1-second-long audio file at a sample-rate of 44.1kHz contains exactly 44100 samples.
Internally, the audio engine tracks loop points in samples; so if you wanted to loop the first half (0.5 seconds) of that 1-second-long audio file, the loop points would be placed at sample 0 and sample 22050 internally.
But, since the LoopRegion property is in seconds, there’s a conversion from seconds → samples that happens under the hood.
Taking the same example, if you wanted to loop the second half of the file, the loop points should be 22050 and 44100 – but sometimes, floating point is weird, and this would end up placing the loop points at e.x. 22049, or 44101. The audio engine interpreted loop points that are “out of bounds” as invalid, and ignored them completely – even if it was just minor rounding errors like this 
CreateEditableImageAsync rbxthumb support is now released!
I’ve been waiting so long on the Humanoid.Seated fix. I can’t wait for it to go live.
so when will it finally be gone? every time i do playtests my console gets flooded with warnings from that storybook plugin which makes debugging an absolute nightmare
Let’s say that I save a local audio file and access it through rbxasset://.
I make sure that the file has a sample rate which is an exponent of 2. Perhaps 32768 samples per second.
If I were using a version of Rōblox older than 655, could that bug still appear with round LoopRegion values such as 1 or 0?
