Epic, a feature that might come in handy for training groups that require certain clothing equipped. Epic update anyways, keep up the good work!
@TheGamer101 The avatar editor (Avatar Editor in Game No Shop - Roblox) doesn’t seem to support layered clothing. Is this a bug, or do we have to implement this ourselves?
Updated, should support layered clothing now! I had the LayeredClothingEnabled config value set to false by mistake.
OH. MY. GOD! I’ve seen this in several games awhile back, but couldn’t find the actual module! Love this!!!
This still exists somewhere deep in Roblox’s content directory since the LuaApp’s avatar editor scene is a place file and they never removed it.
API limits on how many accessories per category is completely unacceptable and spits in the face of UGC creators and multi-part accessories and that whole “powering imagination” thing. If this is the goal moving forwards with avatar limits: No. Full stop. Limits by category is quite bluntly put, pointless.
The limit rules behind the entire avatar accessory system on web is archaic and downright broken, there is no reason to continue enforcing arbitrary limits on “”“categories”""; that makes no sense. The number of tris, memory impact, etc. in any particular accessory does not care whatsoever about category, so I see no reason to enforce this archaic nonsense in new API. Setting this precedent would hurt freedom of expression on this platform severely. Until justification is provided or this is changed, this is completely stupid to me.
If you want to be smart about it, you could e.g. assign accessories an auto-generated “cost” that is proportional to their performance impact ingame, and impose a limit around that cost. This would allow people to have multi-part accessories (i.e. 2-part swordpacks, hair extensions, etc.) without making people constantly fret about an accessory limit, and without killing game performance. These accessories currently could otherwise be combined into single accessories that are more expensive ingame, but save players an accessory slot, which is not ideal from a game performance point of view. A system like this would encourage UGC developers (often non-technical people) to make low-cost accessories because players would be incentivized to buy accessories with a low cost so they can wear more of them. This leverages the economy to encourage good UGC practices.
I want to make sure that these dumb category limits are not the plan going forwards with avatars. This is not a good decision.
Repeating this here from my below post just to be clear.
Are there any plans to add a UserId
parameter to the GetOutfits
function so we can get the outfits of other users instead of just the LocalPlayer
? Currently, the only way to do this is by using a proxy to make HTTP requests to the avatar web API.
+1 to this.
As someone who has an avatar that directly uses multiple accessory types, these limitations are frustrating!
Limiting to 1 of each accessory type is problematic for many reasons:
-
First and foremost, it “sunsets” many avatars that people use on a daily basis, my own included! This isn’t exactly in alignment with Roblox’s “identity in the metaverse” path! I want to be a dragon wearing a cape, crown, armor, belt & sword. This shouldn’t be disallowed! Furthermore, Roblox avatars from 2010 had multiple of a single accessory type:
-
Secondly, this severely limits the creative possibilities for players. Roblox’s avatar teams put a heavy emphasis on making everything into accessories, to strengthen the “mix and match” aspects of the avatar creation process & to allow players to be creative with their digital identity. Because nearly everything is accessories, limiting to ONE of each accessory type effectively counteracts the entire purpose of having everything as accessories. For example, if I want to wear a cape and wings, or if I want to wear a belt and a sword, I can’t now!
-
Thirdly, this has a huge negative impact on UGC. Players will be less likely to buy UGC items since they already have one worn, and it also prevents things like pauldrons, and multi-colored pigtails! Here’s some real-world examples of UGC that is not possible with these changes:
Overall, avatars should be allowed to wear multiple of a given accessory type, on mobile, xbox, PC, and in-game. The solution here lies not in limiting accessory type, but in limiting max total accessories or max triangles.
Doing this unlocks player creativity, and doesn’t sunset my dragon:
Same here. My avatar relies on many shoulder (3+ paldurons to make a nicer robot “arm prosthetic”) and torso accesories (jacket + swordpack + belt)
Limiting accessories in this way is limiting expression which is against what roblox is promiting itself towards; creativity and self-expression.
How in the heck im supossed to express myself using only 1 accessory per 1 slot?
To be clear it’s not really a “change”, the website still works the way it did, but this new API is enforcing dumb old limits that do not make any sense. This is worrying looking towards the future; these limits are harmful and not necessary in their current form. It’s important that Roblox understands this and works towards changing them.
Back in the day these limits were dumb and still are dumb to this day. My avatar is doing fine with 10+ accesories. Let me wear whatever i want to on my avatar wihout some out-of touch decisions that nobody was told about untill now.
Heck, the reason why i wear my jacket and other “pseudo layered accessories” is simple; layered clothing sucks on blocky avatars as it was tailored especially for rtho avatars. All of this could be solved with an optional original blocky base cage.
I agree with the general sentiment in this thread about the new APIs limiting accessories per category, limits should definitely be based on triangles/memory.
In regards to the API limits, and assuming these limits will be applied to the website’s avatar editor eventually; consumers want options. It is rare that a consumer ever wants to be limited, and in this case the APIs are limiting. Players want the ability to express themselves, to get creative, they can’t do that when they are being arbitrarily limited.
Take 5 minutes of your time, join any game that allows for avatar customization, or any game centered around fashion (such as Royal High.) You will be able to find plenty of avatars that are wearing multiple accessories under the same category.
This is going to be very useful! Roblox creators can finally make more granular avatar editors in-game and provide users with much more intuitive and efficient customizability. Very happy to see this!
Any chance the beta will open up again for accessing catalog-related functionality? That’s the primary resource I need for my game at the moment.
While you are correct, the release of this API did not directly change the ability to use the advanced options for accessories in the avatar editor on the web, there are broader changes happening which may suggest these limitations are the unfortunate future. Specifically, the ability to equip multiple hair UGC items was removed from the web form leading up to this with the release of layered clothing.
The non dynamic hair that is currently available in the avatar shop, which total over 10,000 UGC hair items, can no longer be combined using the desktop, mobile, or web clients. If you try it will error or replace your current hair. I am fairly certain this limit was implemented to impose limits on new dynamic hair and upcoming dynamic eyelashes and eyebrows since these dynamic UGC items use a cage mesh and can’t occupy the same space. I believe this is all part of a larger effort to push players away from the classic R6 and R15 avatars to “modernize” the platform and attract a broader player base.
Our players do find it frustrating that the in game “Save to Roblox” can’t do multiple of anything UGC with the exception of hats. So any player looking to wear multiple UGC items must use the web, which by default is blocked for mobile users. Players wanting multiple hair UGC items must now resort to using sketchy third party mobile browsers and/or browser extensions to do it. As you can imagine this poses a greater security concern because third party software and extensions are not all trustworthy.
As for the API itself, we have had the beta up and running for a few months in our experience, Envy Avatar Studio, and with the exception of these limitations, everyone has loved what this API has allowed us to implement. A big round of applause is in order for the dev team on this API!
I used AvatarEditorService to modify layered clothing properties