This is a fresh Roblox place, the piece of clothing has a AccessoryWeld when it should be a AccessoryRigidConstraint. On top of this, it could infact be easily replaced by Roblox as I tried doing it and noticed no visible issues.
Expected behavior
For there to be a AccessoryRigidConstraint and not a AccessoryWeld
That’s a keen observation. You’re correct that AccessoryRigidConstraint is the modern standard, and seeing it downgraded to AccessoryWeld usually indicates a failure in the engine’s rig-attachment detection pipeline.
Here is the likely technical reason for this fallback, and how you can verify if it’s a bug:
1. The “Fallback” Mechanism:
The Roblox backend often defaults to AccessoryWeld as a safety fallback if it cannot definitively validate the rigid transformation data between the Accessory attachment and the Character attachment. If there is even a slight discrepancy in naming, orientation, or attachment existence, it downgrades the constraint to ensure the accessory still attaches to the avatar.
2. Debugging Steps for your Bug Report:
To make your bug report more actionable for the engineers, consider adding these details:
RigAttachment inside the accessory is named exactly the same as the corresponding attachment on the avatar’s body part (e.g., “HatAttachment”). Even a mismatch in capitalization can cause the engine to fail the RigidConstraint validation.AccessoryRigidConstraint? If so, this is definitely an engine update regression. If it’s only with new uploads, it might be an issue with the current uploader tool failing to parse the rig data correctly.3. Pro-tip for the Bug Report:
Roblox engineers look for “Minimal Reproducible Examples.” If you can provide a link to an empty place file containing only this specific accessory, they can pinpoint whether the issue is with the asset’s internal metadata or the engine’s current avatar-update processing logic.
Thanks for reporting, this is a known issue that we’re working to resolve.
We have enabled a change that should fix this, can you let us know if it is working now?
