I understand that many changes to Studio are applied using flags checked when it launches so that you can undo changes rolled out on the fly. Apparently the minimum part size is one of those that’s still relying on a flag.
Yesterday Roblox experienced a site outage and Studio was unable to connect, so it assumed all default values with no flagged changes applied. I unknowningly proceeded to open a place, write some code, and save it. What I did not realize at the time was that all parts which had a size dimension less that .2 had their size changed so that it was no less than .2
Some of the builds could be replaced using models in backup files of older versions, but I did a lot of building over the weekend on smaller details that are now going to be a big headache to fix.
Please “officially” apply the .05 minimum. Thanks.
In addition, it would make sense if the last used flags are saved and act as the default until Studio can connect to the internet and grab the new flag values properly.
I’m not sure if this is a good idea because usually the default state would be the safe state. Most likely turns the feature off. If a feature is potentially dangerous to users it makes sense to have it be turned off if the true state is unknown.
While that would normally be true, this post shows a case where the “default” state is clearly not the safe state. Because Studio turned all flags to “default” instead of the last known good configuration, Studio broke the user’s existing work.
Loading the last known good flags configuration would be a last resort: it would only happen when the user is without a network connection. It should be safe because it was safe the last time it was used.
Users expect Studio to act the same way it did the last time they used it. Cases like the one in this thread are good examples of why the last known good configuration is better than a “default” that may be outdated.