For some reason UnionOperations / MeshParts are currently sorted on top of Models in the explorer. This is a weird behavior because these are still individual pieces whereas models are collections of pieces so it doesn’t make much sense.
Example of strange behavior:
It would be ideal if they still were ordered above parts, but below models!
Yeah, it does feel weird, doesn’t it?
I’d put it in this order (up to down) specifically:
I remember this being suggested back when the Trello board was still a thing; for some reason it didn’t get implemented and was put in the ice box? Anyway, this would be nice. Container-style objects should always sort before others.
Agreed, it is a bit awkward how it is at the moment tbh.
Support. Find this frustrating too.
Or maybe MeshParts, UnionOperations and Parts should all have equal priority and just sort by name.
I also wouldn’t mind if little things like this were configurable somehow, as it can streamline workflow for some devs.
You can accomplish this behaviour using Reflection Metadata in the meantime; however the documentation on it was removed from the rbxwiki about a month ago.
Optional orders would actually be perfect!
As nice as options would be for everything in existence, that sounds overkill for something like this and out-scopes what would be a simple change into a larger task.
We need a default that makes sense and is easy to use.
True.