What's the best way to get an accessory type?

Help and Feedback Scripting Support
#1

So accessories are split into various categories: Back, Face, Front, etc…

image|215x 250
image|215x 2501098×1032 52.7 KB

What’s the best way to find out what type an accessory is is from its CatalogID?

For example:

local accessoryId = 106690045
local accessoryType = "???"
local desc = humanoid:GetAppliedDescription()
desc[accessoryType] = accessoryId
humanoid:ApplyDescription(desc)
3 Likes
Is there any way to distinguish an accessory from being a hat, eyewear, shoulderwear, etc?
#2

MarketplaceService:GetProductInfo returns a table of information about the item with the given ID. One of the keys of this table is "AssetTypeId", which is assigned to a number that identifies the asset type of the item. The number given follows this article on asset types:

local marketplaceService = game:GetService("MarketplaceService")
local accessoryTypes = {
    [8] = "HatAccessory",
    [41] = "HairAccessory",
    [42] = "FaceAccessory",
    [43] = "NeckAccessory",
    [44] = "ShouldersAccessory",
    [45] = "FrontAccessory",
    [46] = "BackAccessory",
    [47] = "WaistAccessory",
}

local accessoryId = 106690045
local info = marketplaceService:GetProductInfo(106690045)
local accessoryType = accessoryTypes[info.AssetTypeId]
local desc = humanoid:GetAppliedDescription()
desc[accessoryType] = accessoryId
humanoid:ApplyDescription(desc)
12 Likes
Is there a way to differentiate between accessory objects?
#4

You can build a list using

local lst = {}
for i, v in pairs(Enum.AssetType:GetEnumItems()) do
lst[v.Value] = v.Name
end
2 Likes
#5

This wouldn’t work. The EnumItem names differ from the asset type identifiers.

#6

Forgot to use v.Value XD but it should work. The names will be the same.

Or using

local tbl = {
[Enum.AssetType.HairAccessory.Value] = Enum.AssetType.HairAccessory.Name, 
...
}
#7

Ah, I was looking at the article rather than the API reference page. Still, the Enum’s “ShoulderAccessory” differs from HumanoidDescription’s “ShouldersAccessory” (which it shouldn’t). Other than that, I believe this should work.

1 Like
#8

I am not sure if that “ShouldersAccessory” should have been “ShoulderAccessory”.

#9

File a Feature Request to have this rectified. It was most likely an unintentional typo.

#10

No need I have passed this on.

1 Like