Adhoc Inventory Permissions Test

Focusing on No-Copy parameters

Copy a no-copy object

1. Give attachments by dropping them on an av
   1. UserA, wear a no-copy box
   2. Attempt to drag the worn box from your inventory to UserB's Avatar
   3. (Fix: The item is not offered to the other person)
2. give attachments by dropping them on a profile
   1. UserA, wear a no-copy item
   2. Drag the attachment onto UserB's opened calling card, unopened calling card in your inventory, or finder profile.
   3. You will get an error: "Second Life: System unable to transfer inventory."
   4. The object will disappear from your inventory, but you will still be wearing it.
   5. You can drop the attachment and take it again.
   6. (Fix: The item is not offered to the other person)
3. Dupe attachments when flying offworld
   1. Attach a rocket pack and fly off the grid by flying through the corner of 3 sims and failing handoff
   2. Detach the object if it's still visible.
   3. Later, the attachment may reappear. Detach this 2nd copy.
4. Rez multiple objects while sim is lagged
   1. Go to a busy sim, such as a sandbox.
   2. Quickly drag a no-copy object to the ground multiple times before the object rezzes in.
5. Put object in folder and rez folder
   1. Make a new folder and put a no-copy object into it.
   2. Drag the folder to the ground. A container item labelled "Many Things" would appear on the ground containing the no-copy object.
   3. You can no longer rez a non-object.
6. Put object in folder and give folder
   1. Put a no-copy object into a folder and drop the folder on another user's Avatar, opened calling card, unopened calling card in your inventory, or finder profile.
7. put no-copy object into an attachment you are wearing
   1. Drag an inventory item into the contents of an attachment you are wearing. Try both ctrl-dropping it onto attachment and dragging it into the contents folder.
   2. llGiveInventory a no-copy object to your attachment, then detach and rez multiple copies of your still copyable attachment
   3. buy a no-copy object
   4. ctrl-drop it into an object you own called 'sender'
   5. attach 'receiver' object to your hand
   6. manually copy key reported by receiver into the sender script target
   7. click on sender, no-copy object will xfer to receiver (new, correct behavior is the sender will say "Unable to give inventory: Blocked by permissions")
   8. detach receiver to inventory
   9. note that you can now rez many copies of receiver, all containing no-copy object

// sender script:
key target = "UUID";
default
{
    touch_start(integer total_number)
    {
         llGiveInventory(target, "Object");
    }
}

// receiver script: 
default
{
   state_entry()
   {
       llSay(0, (string)llGetKey());
       llAllowInventoryDrop(TRUE);
   }
}

1. Put a no-copy object into a container and set the no-copy object for sale. A dupe appears in your Lost and Found. (Fix: The purchase fails silently)
2. Copy no copy object by sitting on it and shift-dragging an attachment
   1. Drag the no-copy object onto the ground.
   2. Make a box and attach it to the avatar.
   3. Sit on the no-copy object.
   4. Edit the box on the avatar, hold shift and pull-copy
3. can disable no-copy permissions with linking and unlinking )
   1. Rez 2 boxes, A and B, and turn on the next owner perms.
   2. Rez a no-copy object that you have modify permissions on. Call it C.
   3. Select C then B then A and Link.
   4. Select individual and unlink A.
   5. Link the linked set(of B and C) to A.
   6. Unlink the whole linked set.
   7. Check if it's still no-copy.
4. can copy a new no-copy object if it has not yet been rezzed
   1. Deed a next owner no-copy, yes-modify object.
   2. Deed a next owner permissive object.
   3. Link the no-copy object to the permissive object.
   4. Check if you can copy the linked object.
5. can copy a new no-copy object if it has not yet been rezzed #2
   1. UserA, create a next owner no-copy, yes-modify object and a next owner permissive object. Set them both for sale, Original.
   2. UserB, buy them. Link the no-copy to the permissive. Set for sale original.
   3. UserA, buy the object.
   4. Check if UserA is not able to copy the object.
6. can copy a new no-copy object if it has not yet been rezzed #3 (bug 1438)
   1. UserA, create a no-copy, next owner no-copy, next owner modify object and a next owner permissive object. Link them together (permissive as root).
   2. Set for sale, original.
   3. UserB, buy the object.
   4. UserB is able to copy the object.
7. make outfit can copy a no-copy object which is in your attachment
   1. Put your no-copy object into the contents of a box. Attach the box.
   2. Enter appearance and make a new outfit.
   3. The attachment will be duplicated along with the no-copy object inside.
8. can copy a no-copy object by linking it to a yes-copy object and modifying
   1. Rez the M/C/NT object (Object A).
   2. Rez a cube and set the cube's permissions to M/C/T.
   3. Link Object A to the cube so that the cube is the parent prim.

Permissions are now M/C/NT on the object. The permission checkboxes are correctly disabled and can't be changed.

1. 1. Select the "Edit Linked Parts" option and select one of the prims in Object A. Change it's twist, topsize, or another parameter.
   2. De-select the "Edit Linked Parts" option and return to the General tab. The permission checkboxes are no longer disabled and you can enable the "Copy" checkbox.
2. can copy no-copy objects via Wear / Drop
   1. Go to a sim with low (~10) SimFPS? for best results.
   2. Make a no-copy box.
   3. Right-click the box, More> Wear.
   4. Quickly right-click the box and Drop it into the world.
   5. Observe If there is a box on the ground and one in your inventory.
3. The detach process should take a couple seconds if you have proper lag.
   1. Attempt to drag the container to the ground while it is still highlighted/attached.
   2. As soon as the attachment is no longer highlighted, release your mouse button to rez it on the ground.
   3. Edit the container.
   4. Observe: The no-copy items are in your inventory, and they are also in the container.