Highlight or mark objects in the explorer that have custom attributes or tags assigned to them

As a Roblox developer it is currently too hard to identify which instanced objects either play a functional or visual role in your game hierarchy.

The problem

Games in Roblox are created by combining objects into assemblies of instances. This means that many objects, such as cars, houses, terrain made out of parts, monsters and so on exist out of, for example:

  • Many (nested) BaseParts and Models
  • Scripts, ModuleScripts or LocalScripts
  • Instances that modify physics behavior (HingeConstraint, BodyVelocity, and so on)

However, this complicates the problem of assigning behavior to objects in the game, because most of these objects are created out of many (grouped) instances. So let’s we have a game where players deliver mail to houses. Players can interact with the post box of a house and this feature is programmed by assigning attributes and tags to the post box of a house. The post box might be a descendent of the following Models:

image

Now the big question is of course, which objects do you tag or give attributes to? In the current moment it might be clear, but if you return later you might have forgotten! It could have been the PrimaryPart of the PostBox model, or maybe the PostBox model itself, or maybe even the HousePlot model!

If you are working with other developers, or even if you are working on a project on your own during weekends, being able to see quickly which objects are tagged or have attributes assigned to them heavily reduces confusion!

My suggestion

Instances in the explorer should be highlighted in some way to tell the developer that they have either tags or attributes assigned to them. This could be done through color coding or maybe even by using a bold font. So in the following example, the second ‘Part’ instance would have at least one tag or attribute assigned to it.

image

This makes it easy to find back and identify that this object has custom behavior attached to it.

19 Likes

image
I disagree with this part right here - this is really hard to tell that the part has an attribute attached to it. I think instead, to be more clear to the developer, that there should be an icon right here indicating that the part has an attribute attached to it:
image

This icon will only be visible if an instance has attributes, if there are no attributes the icon will not be visible. This makes it clear to me when I’m quickly traversing the datamodel in the explorer which instances have attributes and which do not. If the name is simply highlighted, that’s harder to see and I will end up wasting a few seconds trying to figure out if an instance has an attribute or not.

EDIT : The icon would be before the instance’s name, not after

5 Likes

During the attributes beta I found myself also seriously wishing I could see which instances had attributes at a glance. There’s a tremendous amount of unimportant instances in my game, I should be able to identify the important ones with programmed behavior based off attributes immediately.

I would prefer this to be communicated through a little icon in the corner of the class icon, or prepended to the instance name in the explorer.

7 Likes

Thanks for the feedback. We are reviewing options on the best way to find/indicate what instances have attributes.

11 Likes