For developers that have important models that need to be updated, this is problematic. If the issue is being downplayed to “Developers can’t update a couch model” or “Developers can’t update a sword model” (common examples intended to be unimportant), this isn’t the case.
My inventory does not render in its entirety as of this toolbox update, and as I hinted at previously, I needed to make an important update to one of my models to address an exploit vulnerability as soon as possible.
I tried poking around at the toolbox plugin, forking it, and modifying it (Roact is confusing, but that’s a different topic), and was unsuccessful. I ended up toggling the ToolboxWithCMSV2 Fast Flag that @ForbiddenJ mentioned earlier, and was able to publish my model.
If it does then this shouldn’t have passed the QA check before shipping this update to the public.
There will always be updates that weren’t tested fully, or an issue went unnoticed, or was overlooked, and was shipped anyways. With that being said, there should always be a way to reverse the update to a previously working state for some time after being shipped, for those that do experience these problems.
I’m not sure if there’s always a Fast Flag that can do this, such as ToolboxWithCMSV2, but there should be, otherwise I would’ve been left to wait who knows how long (because this isn’t considered “critical”), or to fumble with Roact and fix it myself.
I mean after all, this was a pretty fundamental change to the system that publishes models, it wasn’t like updating a font or the style; it was an overhaul.