Description
I am aware that the Accessory Adjustment is a WIP feature. But I wanted to see the removed hardcoded accessory boundary constraints, and realized an issue with one of the Assets.
The reason this bug report was made, is because I have the strong belief that Roblox eventually doesn’t know about it. And that this issue may unawarely still persist when Roblox releases it, if it’s not addressed.
This is not about OriginalRotation
not existing yet. I assume Roblox knows about that as well? If not, feel free to ask what I ment I guess
The Hat
Instance is deprecated and really old, inherited by the Accoutrement Class (so :IsA
is not excluded by it when filtering for “Accountrement”). But there seems to be left over accessories on the Catalog, that still use the Hat
Instance. These unpredicted Instances could eventually cause an unexpected appearance. In this case, I encountered a problem for the Accessory Adjustment.
This Shield of the Sentinel - Roblox created by Roblox, seems to be a Hat
instead of an Accessory
. And there might be more.
It has no Attachment Logic, unlike Accessory.
Due to that
A few things occur.
On a newer version of the Accessory Refinement, with the XYZ on the 3D view. It crashes the Universal App. (DataModelPatch Asset Version 9383)
[FLog::Error] Error: CorePackages.Packages._Index.Scheduler.Scheduler.forks.SchedulerHostConfig.default:117:
------ Error caught by React ------
attempt to index nil with 'Part1'
------ Error caught by React ------
CoreGui.RobloxGui.Modules.AvatarExperience.AccessoryAdjustment.Components.AdjustAccessoryView:220
The second thing, is that it has absolutely no effect on the Adjustment thing, due to the Accessory being a Hat
Instance.
Re-production Steps
- Obtain DataModelPatch Version 9383, or a version that has Accessory Refinement with the XYZ 3D View and the Blue Selection Sphere.
- Obtain Shield of the Sentinel - Roblox and put it on your Avatar
- Enable Back Accessories on the API of the Avatar Rules
accessoryRefinementTypes
, either through Proxy Debugging or production… (idk why there’s unfinished thing on production API) - Enable Accessory Adjustment and new Humanoid Flags.
- Play around with that specific shield in the accessory refinement
Note that you will crash, the version that doesn’t crash, is the version that doesn’t have that glowing ball.
Expected Result
Accessory moves. Accessory doesn’t cause a crash on the Universal App.
Actual Result
Old Hat
Instances seem to cause unexpected problems.
Side note. Hat
Catalog Instance conversion to Accessory
when? Since there’s R6 to R15 conversions being worked on. I have the feeling that Hat
may be part of this as well, but eventually has been gone forgotten.