If I wanted to purchase single color pants for every “non human” color, ( generally every color under the 3rd row). It would cost around 250 robux for only pants. Paying 5 Robux rather than 250 for moderated pants that allow you to have every color roblox offers seems a lot more viable for everyone.
Uploading empty or 1 colored templates to Roblox to bypass default clothing often gets denied and gives the creator a warning. When default clothing was original implemented, I uploaded (0,0,0) Black, (255,255,255) White and a blank template to Roblox and ~30 minutes later I had 3 warnings for the templates I uploaded.
If it’s doable without moderated assets, explain how? Because moderated/unloaded assets offered the most flexibility as I was able to change my skin tone to all colors without having to purchase one pair of pants for each skin tone. Unloaded/moderated assets also were the safest bet when buying “transparent” items, often times “transparent” was just scribbles over the template and then uploaded.
I just uploaded anoutfit where its only contents is a circle obscured by the head and it passed. I sincerely doubt you will have huge problems working around this without moderated assets.
Also this update, pretty sure HumanoidDescriptions aren’t a component of the standard in-game character spawn? This could change in the future, but it stands that the change isn’t relevant to your point.
Yeah, I really would like this to be a feature, my idea is that a realistic human color applied to the skin automatically changes it to where you have to wear the default shirt and pants even if its just on one limb. I just want this as a compromise as to bring back the charm of this kind of customization as this was only added to stop inappropriate content on the website, to some degree helped.
I see that works, I have some other version of that shirt though it is 100% transparent.
Though my original argument was to prevent people from paying to change their body color in “non human” colors. If they did pay to purchase a “transparent” item it would be disappointing if they had to pay again.
Something maybe I didn’t make clear in the original post is that you can still explicitly put zero in for shirt or pants and you will then get no shirt or pants. This change covers the case where you put an ID in other than zero, which you expect should be good, but isn’t, then you will get fallback defaults applied.
There are no plans to do anything like that currently. If the default shirt and pants are available in the catalog, you could get their asset IDs and use them in a HumanoidDescription when using ApplyDescription() (I don’t know if they are available though)