CollisionGroups cannot be set in studio when outside of workspace

[aaron_mccoy (PleaseDontBanAaron)]

If you set the CollisionGroup manually in studio to a non-Default CollisionGroup for an Instance not under Workspace, it will give you this error:

This will cause the CollisionGroup to be invalid until it is placed in Workspace where it will magically fix itself.

I’ve confirmed with the help of another developer, so it seems to be more than just a fluke.

I’m not sure if this is some weird broken state, or if the error is appearing incorrectly, but there’s no reason setting a collision group outside of workspace shouldn’t work in studio

Addendum: just found out someone else posted the same bug report, oops

Collision Group ID is not updated when changing collision group outside of workspace

If you change the collision group of a part that is not inside workspace (E.g. in ServerScriptService) by changing it in the properties panel using the collision group name, the underlying collision group ID will not be changed automatically, causing studio to show this warning, which cannot be resolved by following the instructions. [RobloxStudioBeta_E3eZz0QyWO] The moment this part enters workspace, the ID is updated automatically and the warning is gone. Expected behavior Updating the col…