As a Roblox developer, it is currently too hard to read the Attributes section once an instance has more than a handful of attributes. Attributes replaced ValueBase instances for configuration, so config-style objects easily reach 10–30 of them, all shown as one flat alphabetical list where colors, tuning numbers and debug toggles are mixed together.
The only workarounds are splitting attributes across child Configuration/Folder instances, which changes the hierarchy and every script just for editor readability, or prefixing names like Colors_WallA, which pollutes the API and keeps the list flat.
Proposal: let attributes be assigned to a named category shown as a collapsible sub-section inside Attributes, the same way built-in properties are grouped into Data / Behavior / Appearance. This is Studio-side organization only: GetAttribute/SetAttribute and attribute names are unchanged, the category is not a prefix. Uncategorized attributes display as they do today.
Expected UI: a “New category” button next to the existing “+”, a Category dropdown in the Add Attribute dialog (default none), “Move to category” in the row context menu, and collapse state remembered per class.
If Roblox is able to address this issue, it would improve my development experience because one instance could stay the single source of truth for its configuration while still being scannable in the Properties window.
Concept Images:
