Insert a part into ReplicatedStorage (insert in workspace and cut/paste into ReplicatedStorage or create through command bar), select it, and press Ctrl+G to group it. The model is moved to workspace. This is a no no. If a part is parented somewhere, it’s parented somewhere for a reason. Studio shouldn’t steal my parts and move them away from where I want them when I group them. If I group a part in ReplicatedStorage, the model should be parented to ReplicatedStorage. If I group a part parented to ServerStorage, the model should be parented to ServerStorage. Stop moving around my parts!
Edit: If I group multiple parts that have different parents, the resulting model should be parented to the parent of the first item in the selection.
Right now behavior is set to find the closest common ancestor that is a model and then parent the new model to that.
However, I think the desired behavior is just that it finds the most common ancestor and parents it to that instead. This does mean if you group a model inside of a folder like this:
It becomes:
Whereas a regular model would look like this:
To:
However, it also means that you can group things in literally any ancestry group (i.e. ReplicatedStorage), and you can still maintain that parent.
Does removing the constraint that the common ancestor must be a model break anyone’s workflow? (this solves this issue).
