Setting Object Privs ?

Is this possible from a script ?

Obviously from a list of privs you already have but I'd like to set the "next Owner" privs and the only function I've found says you need God Mode ?

I'm pretty sure I'm not a god ?

Correct. Residents cannot do this from scripts. Lindens might be able to, but there isn't much information about it, nor would such information likely be very helpful unless there's a plan to open that system up to residents in the near future.

Thanks, is pretty annoying as it would greatly simply product release.

You could ensure the perms were set correctly

You could also strip permissions with a script then now couldn't you... All I'd need to do is drop a script in that releases all the permissions, hence the reason those don't exist.

It's silly to assume that such a function wouldn't have appropriate protections. In particular, it could only allow a reduction in privilege, not an increase. For example, it's ok to turn off 'next owner can copy', but it's only ok to turn it on if the current owner already has copy privileges.

Yeah, the reason they don't want to is because a simple mistake could open up a lot of problems and countless security features would need to be added to prevent an exploit from ever happening. Coding something critical like that is quite stressing and even with thorough testing can leave holes open.

Yes, I want to set privs for the next owner from a subset of what I have.

As different objects I've giving them have different privs, the most relaible way to get it right would be to set it.

I have 3 classes of object in the package

copy, xfer - for them to hand on to people you interact with them
copy noxfer for their base station
no copy, xfer for the license server to control their access

That's what next owner can: permissions are for, you set them once, and as you vend copies, it sets the appropriate permissions. I don't really see the need to do the same thing from within a script.

Need to, no you don't.

Want to yes. I understand the privs. When you are trying to build new releases of a product here each part has different next owner priv requirements, the ability to set them correctly in a script would greatly reduce product release screw ups.

For example it set descriptions on the containers by scanning the versions of the scripts included. That way I can always name the object with the correct version number. This is the same idea.

Whether from script or GUI, what would REALLY help to decrease the number of accidents is to have some kind of recursive method for the case where you want to set permissions on an object and all the contents of all its prims' inventories and for each of them that is an object, all the contents of all of its prims' inventory items, etc.

I can't tell you how much time I have spent rezzing, unpacking, re-packing, taking, and checking scripted object systems, and I bet many of you have had the same experience. "All I want to do is turn off transfer permissions on everything in this build." Arg! Pain in the ass when you need to maintain both full permission (for sharing with trusted colleagues) and correctly distributable versions. Now setting the same permission on absolutely everything in a build may not always be the correct thing to do, and you'd have to have some kind of warning system for when you CAN'T change a permission on some nested item, but it would sure be a huge first-step usability feature.

permissions are pretty complicated, you have the object permissions, then the permissions of any objects contained within the contents of an object. At times, you may want the script itself to be no modify, yet a configuration notecard, to be full perm, so I don't think it would be as cut and dry as you seem to want. Personally, I check, double check, and then triple check permissions before I set it out for sale so that I don't have the issues you seem to have.

I did use to manually check permissions but found that I would always fail, particularly when it came to making things that originated from someone else's build. I really can't be bothered to faff about checking every single damned prim in an object.

In the end I ended up writing my own self-propagating script to do it, which can be found here: http://ordinalmalaprop.com/forum/discussion/24/example-automatic-inventory-permissions-checker/

Well, what would be REALLY nice is a tree view of an object, its prims, the contents of all those prims, etc. And a table of permissions check boxes to the right. See the attached image for an example.

Yeah I guess checking them automatically is the best I can do