Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

You can't nest disparate permissions

Spins Stovall
Registered User
Join date: 11 Jun 2006
Posts: 2
06-13-2006 00:11
Hello,

I just wanted to make sure I'm reading all the posts on permissions correctly. If you have an object with "no modify, no copy, no trans", then you may *not* have any children objects embedded in that object that have "yes modify".

The reasoning is that I assume those permissions are inherited to the child object (or the code just checks the parents permissions and stops if it sees no modify).

The only bummer is that for my scenario it doens't work well. In this example I have a prim and embedded into it is a configuration notecard and a script. I would like folks who buy this prim to:
* Be able to modify the configuration notecard
* Not be allowed to modify the size of the prim
* Not be allowed to modify or read the notecard.

The closest I can get is to allow the prim to be modified then I can make the notecard modify and the script no modify. But the problem is that the prim can be mucked with.

Does anyone have a solution to this problem? The closest I could think would be to have the prim be modifiable and then have the script resize the prim either on start up or on a timer.

thx
-Spins
BamBam Sachertorte
floral engineer
Join date: 12 Jul 2005
Posts: 228
06-13-2006 09:07
If the prim is modifiable then the owner can do much more to it than change the size. It would be very hard for you to restore it back to the intended shape.

Try using llAllowInventoryDrop(). The owner doesn't need mod rights to drop in a notecard if you set this to TRUE. You would need to have a script that gets inventory change events, deletes new items that aren't notecards and treats notecard drops as new configuration notecards.

The problem with this solution is that anyone can drop a configuration card on the object and your script will have no way to know whether the owner drops the card or someone else. You may solve this by requiring that some magic cookie be present in the configuration card that only the owner will know.
nand Nerd
Flexi Fanatic
Join date: 4 Oct 2005
Posts: 427
06-14-2006 15:17
In addition to BamBam's solution you could check the creator of the notecard, however this still isn't fool-proof as anyone with a notecard created by "the owner" could modify it and drop it into the prim.
_____________________
www.nandnerd.info
http://ordinalmalaprop.com/forum - Ordinal Malaprop's Scripting Forum