Gah! Object Privs!

Does anyone know of a good workaround to the fact that SL likes changing the permissions on things constantly? Even a script that would test things somehow?

I set out a freebie gift box, double checked the perms before logging out to make sure they were right, even pulled it into inventory to check the properties and pulled it back out. All because it was group-only land and my other account was not in the group to test the build. Then got a message about someone not being able to access it. Logging on I found that the privs were not what I had set earlier.

*sigh*

BTW, usually I build things full-priv so I can minimize these hassles with anyone I am working with. Would be nice if there was a settable perm mask for when you rez a prim for the first time.

I'm going to go out on a limb here and presume that you are refering to the permissions settings on prims as they rezzed. The default is that a fresh rezzed prim is no copy/mod/transfer is the best default as any item is "safe." One has to actually change the permissions of the prim in order to sell it or allow others to mod or transfer. If it was the other way where everything you made was full perm from the get go I would suspect that here in the forums would be a large amount of griping about "why are things full perm when i make them"

Realize that this cant be everything to everyone and that the SL platform is a constantly evolving multifaceted program with literally thousands upon thousands of itsy bitsy code thingies in there that has to work perfectly or else someone will find a bug and exploit it. If we as users want something changed there are avenues to do so be it in the jira or thru the ticket support portal.

Or we can log off for a bit and maybe watch some tele come back and try again later.

What's a "priv"? Like Eyerocker, my guess is you mean permissions (perms), but on the off chance that we're mistaken, what do you actually mean?

Oops, thinko/typo .... yes, I meant object permissions.

It is possible to script an object so that it will check the permissions of things in it's inventory, specifically checking either for what the NEXT owner will be allowed to do.

I wrote something to do just that a while ago, though I don't recall the details off the top of my head. Unfortunately it is only possible to check the current permissions; scripts can't actually change the permissions for you.

hi Zoey, try llGetInventoryPermMask with MASK_NEXT

thanks, but I've already made the script I was talking about