This is another object ordering request, like this thread.
ReplicatedFirst and ReplicatedStorage appear above some server-specific services. This splits up all the client-specific objects which make it more difficult to navigate.
There is another negative attribute of the current order, too: ReplicatedFirst is above ReplicatedStorage. ReplicatedFirst, along with StarterGui, StarterPack, and StarterPlayer, is a service that runs LocalScripts that are inside it. In addition to that, scripts in ReplicatedFirst often need to work with scripts in StarterPlayer or the other two services listed in order to start up the game on the client-side. Separating these similar services from each other by ReplicatedStorage, which does not run LocalScripts and which (in my case) often contains many ancestors that are often expanded, makes navigation messy and editing rough.
Expanded I normally have more than this expanded, so it becomes an even bigger pain to move between ReplicatedFirst and the three other client-code-running services. It would be too big to get a screenshot of the separation then as it wouldn’t fit on my screen. It would be even worse if I duplicated this tree and moved the Server items over to ServerStorage (like I should do) and left that open, too.
It looks like items that are grouped together are alphabetized, which would explain the logic behind the current positioning:
I’d argue that the whole hierarchy should be alphabetized, but to have Workspace at the bottom of the hierarchy would be absurd.
As long as we’re moving things around, Lighting should be next to Workspace and HttpService should be next to the group of server-related items (and have its own icon).
Or perhaps just allow us to reorder the topmost elements of the hierarchy?
Good idea. I would like it if ServerScriptService and ServerStorage were moved up to above ReplicatedFirst because I have the same issue you do, but wouldn’t that be a little weird? Workspace is essentially ReplicatedStorage but one that renders its contents. Lighting is what used to be used for what ReplicatedStorage is now. Workspace and Lighting are both partially clientside services like ReplicatedStorage (which can also be used by the server). Wouldn’t it be odd to split them up? Let’s say we moved ServerStorage/ServerScriptService down to the bottom past all of the client services – wouldn’t that make them harder to get to even though the client/server services were grouped?
HttpService should have its own icon
Agreed
HttpService should be next to the group of server-related items
Disagree. HttpService is used in the explorer almost never. It’s good that it’s at the bottom so it’s not wasting space.
Or perhaps just allow us to reorder the topmost elements of the hierarchy?
You can do this already by modifying the explorer index of objects/services in Studio’s ReflectionMetadata.xml, but the problem is that it’s overwritten each time Studio updates. Unless you have a custom Studio launcher, it’s very painful to keep your changes. If Studio supported modding, then we wouldn’t really have an issue – I’m thinking something as simple as the launcher using the ReflectionMetadata.xml/Ribbon.xml (or using something additive like the ClientAppSettings file – actually this would be preferred since I often run into issues where I need to manually update my ReflectionMetadata to keep up with updates) files in /Versions instead of the Studio folder when launching if they exist.
