A name conflict is still possible with the
Folder and a character. It has been suggested in this thread to register usernames to prevent this, which I don’t think is reasonable.
CollectionService when there will only ever be one tagged item is not idiomatic, and can mislead someone into thinking they can add the tag to more objects without an issue, which may not be true.
ObjectValues are another option, but this is also awkward. It should be easy to safely refer to a child of
Workspace, even for new developers.
I don’t think this is reasonable, and the naive approach is actually unreliable. Developers would have to set
false and manually set and respawn
I’m not sure why you think my suggestion would be a significant change. It would mostly impact code which is already bugged, and which uses very old coding practices (to be fair, checking if
Workspace may be more common). In terms of breakage, I think there would be a far higher impact from the ordering update without this change.