llReturnObject(key id)

We need some way to reduce the various atacks that occur. I know that better land tools would be better, but they will take time.

I sugest adding llReturnObject(key id) where the object must be over land owned by the script owner.

The rest of the features like, "Return all objects", "limit prims", ect... could then be made using scripts.

This gets re-suggested often. I think it's time to get it a page on the features vote thinger - just, this needs to have a required permission to function. Lest someone rez that cool freebie they found in a sandbox and fill thier Lost & Found folder with thier house and furnishings, ya kno?

Okies, I did it:

here y'all go: Prop. 1016; llReturnObject(key id) -- Return objects to thier owner via script.

Could you add the link back to this discussion thread from the proposal?

I think people are missing how this could be usefull for a lot of situations.

1. Renting scripts can limit prims or return them all when the rent has expired.
2. Security scripts can remove grey goo atacks and weppons.
3. Clean up scripts can return objects after checking there "Allow list".
4. Security Scripts can return objects that impact passive scripted walls.
5. Security Scripts can return objects owned by avitars on there "Ban" list.
6. Security scripts can return the agents objects at the same time they teleport the agent home.

I agree that some kind of security should be in place....but i wouldn't be as specific about how to implement it. As much as the Lindens get blamed for all the bugs in SL....they do have an insider's view about what's more feasible and less abusable.

Consider, if you will, a device marketed as a "security system", purporting to clear your land of those annoying little prims. When you rez it, of course, you're EXPECTING it to return/delete stuff, so you grant it the permissions to do so. You then sit and watch as the object returns all the scripted buggers.....along with every other prim on your land.

There needs to be a way to prevent that. And a blanket permission to delete stuff, just ain't gonna cut it. That's why i voted for a similar proposal (#127, which puts forth the same idea without trying to mandate how it be done.