Permisions for Packaging Items

I've created this scripted object thats super nifty and ... well ... supernifty, and it comes with a couple different parts and a notecard. I've got it boxed up in a box with an inventory giver script so it does the requiste "here's your stuff" when you open the box, and that works great.

I've already looked at the thumbnailed permissions thread
-------------------------------------------------------------------------------=

(...underlining just in case...) it talks a little bit about setting permissions for objects stored within other objects, but I'm looking for what the "standard practice" is. The objects within the package are mod nocopy transfer. Script perms are defaulted which ... I hope means no-mod no-copy, alright, I'll need to doublecheck on that.

Question 1: What perms do I set the box to if I want to give it away to people as a gift, or give to a partner so she can give the box as a gift to her friends? (and if I give it to my partner, how can I set it up so she can make infinate copies for herself, but the copies she makes are mod no-copy trans - would she need to individually set the perms on each copy she makes or just once on the full-perm copy I give her?)

Question 2: What if I want to sell it? Does the fact that it contains stuff inside with their own unique perms change the basic settings for selling an item (i.e. mod no-copy trans in this case and setting a price)

Question 3: How do I pack this up for sale on slexchange and slbotique? If the sites provide detailed instructions on this don't bother answering, I'll do the RTFM routine

And ... question 4: OK, I'm totally at sea with this concept about how to sell my supernifty thing without getting bit in the rear over something I forgot. I'm assuming there are some standard references on *how*to*do*this*right* - so ... well, where are they?

Thanks much! Hope I didn't scare anyone off with 2-year-old-asking-questions bit. The items in packages material just isn't covered in the stickied thread, so I'm hoping what I learn here will work its way into it.

making something that you can give, the seller able to copy, then transfer one as no-copy, is pretty tough. there might be some scripty stuff you can do (i'll defer that to someone else) but even then you're asking for trouble and run a strong risk of someone getting a full perm version, or able to distribute (i.e. resell) infinitely.

if you want to be safe, make it no-trans or no-copy, but not both, using the standard permissions.

same applies to listing on the web sites. btw, those sites both use in-world boxes that you package your item boxes into, then list them on the sites. they have instructions.

I set my sale boxes to "give contents" with the relevant permissions in the objects inside (like modify/copy). For no copy stuff, if you're giving a box with stuff in (the box is just a container) I *think* the box itself needs modify permissions, because moving (no-copy means no copy...) contents out of it would change the box as an object, which is "modifying" it. I've had this problem with trying to pull/delete walk anim scripts from no-mod shoe prims. It's not a problem with copyyable contents because dragging them to inventory doesn't change the box.

To make something you can give, you don't need to set any permissions at all- your stuff is your stuff typically. It's the next owner who gets stuck with the permissions. Set the box as no-copy/yes-transfer- it will assume the most restrictive permissions of the contents anyway.

http://rpgstats.com/wiki/index.php?title=Permissions

Says there is no scripty way of changing permissions on objects currently implemented, though I have had HUDs which change from copy/no-transfer to no-copy/no-transfer when rezzed in world.

For you to give the items to someone else who can pass them on infinitely, you need to provide copy and transfer permissions to that person, and hope they go through reseting all the permissions back. Alternatively, you can make a kind of vendor that, on touch, gives your friend (and only your friend, by key) a single copy at a time of your object (no-copy/yes-transfer). So they can stock up with a few at a time from your dispensor.

Q3 is indeed covered by the website information when you register as a merchant.

Q4 is something I still fuss over- especially when I've changed permissions on something to let a friend/alt have full access to it- forgetting to change permissions back would be pretty bad. It's easy to spot when you made them too restrictive (like accidentally putting a no copy script into a copy/notransfer item) because you'll get complaints

Good luck with your super nifty object!

Thank you very much. Ace, that was quite helpful!

*looks for the rating button ... DRAT!!*