New Naming Convention for Layered Clothing Cage Deformers

Hello Developers!

We are making slight changes to the naming convention used for cage deformers to better align with existing naming conventions used for Attachments and Motor6D in avatars. This change only applies to caged avatar bodies and layered clothing accessories, and is meant to improve the readability of hierarchies displayed in Explorer.

Currently, cage deformers are named the same as their parent mesh part. For example, a “Head” mesh part currently has its WrapTarget deformer named “Head”. The issue is that this naming convention is unique to cage deformers. All other children in the Head mesh part have additional text appended to their names specifying the purpose/function of the node. For example, all attachment nodes of the Head mesh part have the suffix “Attachment” appended to their instance names. The same happens with Motor6D for accessories.

Now, we are naming cage deformers following the same principle used for other children nodes:

  1. We are appending “WrapTarget” to instances of cage deformers corresponding to body parts (see Figure 1)
  2. We are appending “WrapLayer” to instances of cage deformers corresponding to layered clothing accessories (see Figure 2)

Untitled (3) Untitled (4)

Figure 1: (left) Current naming convention for LC body parts; (right) New naming convention to more clearly indicate that the child node is a WrapTarget instance.

Untitled (5) Untitled (6)

Figure 2: (left) Current naming convention for LC accessories; (right) New naming convention to more clearly indicate that the child node is a WrapLayer instance.

This naming convention update should not affect existing experiences that support layered clothing, since developers are likely using the following to access cage deformers in their Lua scripts, instead of directly referencing them by name.

`part:FindFirstChildOfClass("WrapTarget")`

or

`part:FindFirstChildOfClass("WrapLayer")`


Please let us know if you have any questions or concerns.

Thank you.

65 Likes

This topic was automatically opened after 10 minutes.

pretty cool, not the biggest change as you stated. But a decent one.

3 Likes

Not a huge change, but i’m excited for what people’ll be doing with this later on.

2 Likes

Roblox already did better, but it still good. Good work Roblox!

2 Likes