llSetAvatarClothing JiraRequest

Alot of people want this, do you? if so vote for it

Login to the jira using ur sl username and pass and hit vote on the left hand side

https://jira.secondlife.com/browse/SVC-354

This will alow us to make stuff like

Working Wardrobes
Outfit Creators
Hud objects
Preview Clothing for vendors
alot of other things

For the teck specks

Permissions must be given under all cirumstances to prevent exploiting this

llSetAvatarClothing(key Avatar, integer bodypart, key UUID, vector Color);

integer bodypart could include,
CLOTHING_SHIRT,
CLOTHING_PANTS,
CLOTHING_SHOES,
CLOTHING_SOCKS,
CLOTHING_JACKET,
CLOTHING_GLOVES,
CLOTHING_UNDERSHIRT,
CLOTHING_UNDERPANTS,
CLOTHING_SKIRT.

Another Good Command Would Be.

llRemoveAvatarClothing(integer bodypart);

way not make it

llRemoveAvatarClothing(key agent,integer bodypart);
*giggles*

i think i see the blue box

Random Foo wants to undress you.
Do you accsept this

[Yes] [No]

Actually, I think it's a great idea... I wanted to code up a HUD to quickly change my outfits between different "mixes and matches" I use on different occasions.... but there's no LSL functions to wear/unwear clothing, just attachments.

if this is aproved it could be a big leap in avatar apearance's, using the code would alow you to make up sets of clothes u think go well together, even sell boxes that u click and it makes u ware the outfit <for the big clothes shops ect>

I think part of the problem with this is that, currently, an avatar can only wear clothing present in their agent's inventory. Script has no access to an agent's inventory, only its associated object's. You propose using the UUID key of a clothing item and then applying it to a given avatar, identified by its agent's UUID. Will this allow avatars to wear clothing items their agents don't "own?" What's to prevent circumvention of permissions by just passing around UUIDs of clothing items?

[Edit to add: Also, the "integer bodypart" parameter is redundant anyway, since clothing items are already specified to a body part.]

[Edit 2: Oh, wait... you're talking about the UUID of a *texture*, not a clothing item. In effect, you want to dynamically generate a clothing item through script.

In that case, for one, you'd need to supply a list parameter which contains properties specific to the clothing item beyond just texture and color, such as length, collar height, etc, similar to how llSetPrimitiveParams takes a list of properties unique to the prim type.

Secondly, this is just *begging* for abuse. As things are now, it's not too terribly difficult for someone to steal another's clothing designs (the steps of which I will not elaborate on), but it would necessarily involve re-uploading ripped textures. What you're proposing would circumvent that necessity. All a clothing thief would need to do is sell a script that references the original creator's existing textures. ]

Perhaps attaching clothes from the objects inventory would cause less problems?

This would also depend upon how the asset server handles the clothing. The easy way to go about this would be to implement a "contents of prim running the script" only, in much the same way as an animation (i.e. no UUID support). This would also address the concerns above about abuse of the UUIDs (i.e. passing around known UUIDs against creators wishes).

Issues may arise with regards to permissions as (in my experience) there has been no standard for the permissions of clothing (some are no-transfer to allow for sorting into multiple folders (i.e. building up outfits) which would suit this application however others go for no-copy to facilitate resale and/or returns).

Were this to be implemented retailers who have sell no-copy clothing could exchange for no-transfer although this could be quite a bit of work on the retailers part.