Second Life Forums Archive

Moleculor Satyr

Fireflies!

Join date: 5 Jan 2004

Posts: 2,650

03-04-2004 22:41

A No Copy, No Transfer, No Modify object can be taken.

This is a bad thing.

(Yes, I know about Lock, but how the freakin 'ell am I supposed to edit my own object if it's locked?)

_____________________

</sarcasm>

Cienna Rand

Inside Joke

Join date: 20 Sep 2003

Posts: 489

03-05-2004 07:16

You can't make a No-Copy, No-Transfer, No-Modify object. Either Copy, Transfer, or both must be enabled.

If a no-transfer can be transfered via drop, grant modify perms, then they take then that could be undesirable yes.

_____________________

You can't spell have traffic without FIC.
Primcrafters (Mocha 180,90) : Fine eyewear for all avatars
SLOPCO (Barcola 180, 180) : Second Life Oil & Petroleum
Company
Landmarker : Social landmarking software
Conversation : Coming soon!

Moleculor Satyr

Fireflies!

Join date: 5 Jan 2004

Posts: 2,650

03-05-2004 12:08

Then what the freakin' 'ell do I have in my inventory? And ask Ananda Sandgrain if it's possible to take one of these. I took her Cache object last night at the elven meeting.

_____________________

</sarcasm>

Julian Fate

80's Pop Star

Join date: 19 Oct 2003

Posts: 1,020

03-09-2004 15:25

Are all those permissions actually set or is that part of the name? I've seen people who have items with (no copy) in the name because they were made pre-1.2 and the (no copy) is the creator's suggestion to the buyer.

Pete Fats

Geek

Join date: 18 Apr 2003

Posts: 648

03-09-2004 16:30

This is the way I understand this (Ama correct me if I'm wrong

)

Say you have object foo with script bar and texture alltohell in it's inventory. Permissions for these 3 are set to:

foo - full mod, full copy, full xfer
bar - no mod, full copy, no xfer
alltohell - no mod, no copy, full xfer

Once that object is taken to inventory, it will be called foo (No Modify)(No Copy)(No Transfer). The only relation that I have seen from 'child' permission to their 'parent' is in the naming of the parent.

So AFAIK, given the above, you could retexture foo, not edit the code in bar, and if you tried to drag the texture out, it would leave the inventory of the object.

Gah...I even confussed myself with this one.

Welcome to the Second Life Forums Archive

Bad Thing

Bad Thing
Moleculor Satyr Fireflies! Join date: 5 Jan 2004 Posts: 2,650	03-04-2004 22:41 A No Copy, No Transfer, No Modify object can be taken. This is a bad thing. (Yes, I know about Lock, but how the freakin 'ell am I supposed to edit my own object if it's locked?) _____________________ </sarcasm>
Cienna Rand Inside Joke Join date: 20 Sep 2003 Posts: 489	03-05-2004 07:16 You can't make a No-Copy, No-Transfer, No-Modify object. Either Copy, Transfer, or both must be enabled. If a no-transfer can be transfered via drop, grant modify perms, then they take then that could be undesirable yes. _____________________ You can't spell have traffic without FIC. Primcrafters (Mocha 180,90) : Fine eyewear for all avatars SLOPCO (Barcola 180, 180) : Second Life Oil & Petroleum Company Landmarker : Social landmarking software Conversation : Coming soon!
Moleculor Satyr Fireflies! Join date: 5 Jan 2004 Posts: 2,650	03-05-2004 12:08 Then what the freakin' 'ell do I have in my inventory? And ask Ananda Sandgrain if it's possible to take one of these. I took her Cache object last night at the elven meeting. _____________________ </sarcasm>
Julian Fate 80's Pop Star Join date: 19 Oct 2003 Posts: 1,020	03-09-2004 15:25 Are all those permissions actually set or is that part of the name? I've seen people who have items with (no copy) in the name because they were made pre-1.2 and the (no copy) is the creator's suggestion to the buyer.
Pete Fats Geek Join date: 18 Apr 2003 Posts: 648	03-09-2004 16:30 This is the way I understand this (Ama correct me if I'm wrong ) Say you have object foo with script bar and texture alltohell in it's inventory. Permissions for these 3 are set to: foo - full mod, full copy, full xfer bar - no mod, full copy, no xfer alltohell - no mod, no copy, full xfer Once that object is taken to inventory, it will be called foo (No Modify)(No Copy)(No Transfer). The only relation that I have seen from 'child' permission to their 'parent' is in the naming of the parent. So AFAIK, given the above, you could retexture foo, not edit the code in bar, and if you tried to drag the texture out, it would leave the inventory of the object. Gah...I even confussed myself with this one.