How do I revert the updated / next gen Toolbox:
to the old one:
or is it not possible
2 Likes
It’s probably controlled by an FFlag, but also… why? It barely looks any different to me, only the Categories section sticks out
1 Like
Its far laggier than the old one, sometimes switching categories doesnt work, and Im just used to the old one.
1 Like
I still have the old one personally. I’ve checked into beta features and saw nothing about the toolbox so I don’t know why your looks like that.
One more thing, I tried opening roblox studio with an alt account, and that account had the old toolbox instead of the new one. So only my main account has the updated toolbox
Roblox frequently uses A/B testing and phased rollout, meaning that certain features are gradually released over time to a higher and higher percentage of developers/players. In a case like this, you have simply landed out of the testing group, while OP has landed inside of it.
Do beta features not exist for a reason? Why wouldn’t they use that?
2 Likes
I agree, a game engine is not something you should A/B test.
1 Like
It’s more for changes that shouldn’t have any visible behaviour differences. There are hundreds of these, and none of them provide any major functional benefit to developers and are mainly refactors or bug fixes or performance improvements. You can search “rollout” on this file:
These are rolled-out in this way out of an abundance of caution, so that they can easily disable the new code and fall-back on the old code dynamically without having to send out a full update in case there are unforeseen consequences. These are policies that they’ve developed over decades of making mistakes and fixing them painfully through downtime.
2 Likes
I understand that, but I still think A/B testing a game engine is kind of odd. Beta opt-in exists for a reason.
I swear people will hate on anything 
Go through the settings and look through there, if there is no setting in there then probably not.
Roblox is not just a game engine, it is a platform. Only one version of the engine can be online at a time, unlike other engines where developers can simply use an older version if they have any problems with an update. It may be “odd”, but it’s a necessity. A/B tests shouldn’t be noticeable most of the time anyway, 99% of the obvious FFlags will never even get an Announcement or bullet point in a Release Notes because they are just code maintenance.
But this is just bad UI design. You can’t even see what you’re typing if you’re not using the whole screen…
Also for people saying disable next gen studio preview and next gen explorer. They have nothing to do with it. I have them turned off and still have this awful UI pushed into my face.
Also they made the blue checkmarks white now…
