That won’t be necessary. The feature will be carried out to all players in the future, after all. And, while it isn’t live, people can just use version 2.
Yes, you’re right. But right now it’s awkwardly handled and developers should be able to quickly update without a weird Topbar even temporarily when Roblox decides to fully roll it out.
Roblox also has a problem of rolling out features in percents too, so it may not be out for everyone at the same time.
It’s a major release version, meaning backwards compatibility is not guaranteed. I agree with your second statement, though (but it is probably an issue of players not updating their Roblox installation, even though it should be automatic).
I’ll be creating a ‘Classic’ theme just for this! It’ll determine and apply the theme based upon the topbar insert local hasOldUI = GuiService.TopbarInset.Height == 36.
Roblox should be announcing a topbar beta today/shortly so developers can then opt into that to begin testing in-game too!
Other things I’m still working on:
Complete dropdown theming support
Fix smart aligning of captions and dropdowns
Completing the scrolling behaviours within Menus and Dropdowns
I’ve designed v3 so that the majority of it is backwards compatible with v2. The only significant non-compatible change is the new theme system, and a few methods which have been removed.
I know how to use a module and a script lol, my question was if it was possible to require the module without having the actual model inside the main model, so that it would minimize the scripts within this product
This is a good question: I plan to support auto versioning for v3 by converting the Icon into a package. Package updating currently hasn’t been rolled out but it’s designed this way in hopes it eventually does:
require(MainModuleId) is being removed entirely hence why best to avoid:
its not only require(MainModuleId) that gets you under fire
we had a module ( which was a package ) that contained themes for maps and stuff and they were based on the place ids
and that got the module and the publisher banned under malicious code guideline , took us a while to get it backup and stuff . any mention of ids will just get you under fire