Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New bot function proposal to outfit a bot from prim inventory #9

Open
Vinhold opened this issue Apr 29, 2019 · 0 comments
Open

New bot function proposal to outfit a bot from prim inventory #9

Vinhold opened this issue Apr 29, 2019 · 0 comments

Comments

@Vinhold
Copy link

Vinhold commented Apr 29, 2019

This proposal is to extend current bot functionality to provide an instanced bot's appearance based on items provided for it in a prim/object inventory. This will make bots a lot more useful and have many applications.
Proposed Additional Functions: *

botOutfitAdd(botID/botOutfit-Name, "contentsName"[,attachmentpoint])
Where botID is the integer ID of the instance existence of a bot OR string botOutfit-Name to be applied to.
contentsName would be the item name in the object inventory. Item must be there, and must have the same owner as the prim. (I do not know of any possible case where the owner would have any content in the object that was not also owned by the same.)
[,attachmentpoint] This does indicates where that item is to be worn or attached. I would suggest this be an optional parm where it is not self evident as in the case of attached items using the attachmentpoint number or its constant name.
This function will not copy any item to the owner's inventory. It merely assigns the referenced item to be worn by the bot instance that uses the designated bot outfit name. A bot does not have any inventory. It only requires the inventory item UUID and AssetID to wear or attach the item. The item UUID reference for this proposal may come from owner's inventory or an object's inventory.

botOutfitRemove(botID/botOutfit-Name, "contentsName") This would remove the item from the bot outfit assignment based on the prim inventory item name if it was found to be worn on the bot outfit. NOTE: some worn items may only be replaced such as skins, standard clothing etc.. Attached items may be removed. Proposal would apply this function to attached items only.

botOutfitSaveAs(botID/botOutfit-Name, "newOutfitName"); This function would provide a way to save the current botID outfit or outfitName as a new bot outfit. The limit of 40 max bots per owner would apply.

  • suggestions posted to me by Appurist. Comments are mine.

The proposed functions would include permission checks, but since can only be applied by script to an object which is the owner's, and the inventory also belongs to the same owner, this is a bit redundant. If the items may be worn by the owner, they may also be applied to the owner's bot outfit designated. There are no options for applying these functions to someone else's inventory items or content in an object that is not also owned by the same owner. So the permissions only applies to the owner of their own contents.

Since these functions would make it possible to create outfits for bot use as defined products that may be exchanged or sold, the functions in the scripts may only apply in the context of the active owner. The object inventory may be worn by the new owner's bot. Any items that a bot is wearing may not be transferred by script to the new owner's inventory anyway. I do note that there is no way to prevent object inventory from being copied to the new owner's inventory. Bot worn items are a one way direction from owner to bot. These functions extend that to also include an object's inventory, making possible use of vendor models showing worn products, ride-able creatures with bento shapes, breedables of any description, and a lot more applications. What may be done with an avatar could also be done with a bot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant