llAllowInventoryDrop

[XbabylonX]

Hello, could someone tell me if this can work only for group owners? I admit I dont understand the explanation from the wiki.

[Qie Niangao]

No.

You may be able to use the function, however, to do something similar to what you want, depending what that is. llAllowInventoryDrop, while enabled, lets anybody drop (non-script) stuff into an object's inventory. The calling script can first check to see if the agent requesting it is on an authorized list, or satisfies some other criterion, before briefly enabling the function -- but while it's enabled, it's wide open to anybody at all. Also, without bot assistance, scripts have no way to know the specific role (such as "Owner") of a group member, so that authorized list would have to be manually populated and maintained.

I don't know of a way to use non-scripted settings to relevant effect, except for group-deeded objects, where the group's non-Owner roles don't include the Object Management Ability to "Manipulate (move, copy, modify) group-owned objects" -- and then those Owners could do much more than just add stuff to the object's contents. (And group-shared objects extend such powers over the object to everybody in the group.)

(In passing: A script can now get OBJECT_LAST_OWNER for rezzed-in-world objects, but that won't work for stuff in an object's inventory, so there's not much ability to filter contents after they've been dropped into inventory. For some specialized applications, llGetInventoryCreator can be useful.)

[XbabylonX]

By this I understand that you can get the username or uuid of the person that dropped something.

So, on change and using samegroup do you think it could work?

[Rolig Loon]

---

XbabylonX wrote:

By this I understand that you can get the username or uuid of the person that dropped something.

So, on change and using samegroup do you think it could work?

---

No, actually, you can't.  Or at least not reliably.  All the script can detect is that something was added to inventory, not who put it there.  You can use a sensor or some other tool to figure out who was standing there at the time, or you can write your script to allow inventory drop only after someone has first clicked on the object (and you have therefore captured his UUID). It's easy to imagine ways to get false identification from any of those, though (two or more people standing within range, people clicking from a distance, two people adding things at once ....).  As Qie says, you can't use OBJECT_LAST_OWNER on things that were dropped from someone's inventory, and llGetObjectCreator isn't very helpful in this context.  You are stuck with getting answers that might be correct a lot of the time, but not really very reliably.

[badboymercy]

Perhaps making a hud item or similar with a briefcase or so. You put items into the briefcase and then click the "box" you wish to transfer items to, the "box" would carry a script that would generate a request key that gets whispered to the person(assuming they are whitelisted). Now with this key and the items you wish to move in the "briefcase", click the briefcase and send the code given through w/e listen channel the briefcase script is set to. The briefcase puts a key in the description of the objects and the "box" then checks all items that enter the inventory for this key, if the key is not in the description the item is removed from the inventory, alt, returned to the person who put it there. The description is cleared and each item processed will have the description cleared. I guess someone fast enough may be able to catch the secure code or so, but perhaps that could be solved by having the "briefcase" and the "box" could communicate various details and new codes in random channels to make sure that each object added is the correct or most likely to be the correct item(s). No clue, something like that. A bit of work if anything.

[XbabylonX]

Thank you all for your answers.

[Estelle Pienaar]

Make access to a parcel in the region "group only". Then place the object there?