Duplicate another persons prims, creates problem ...

I'm just wondering if I'm the only person with this trouble, or if I'm doing something wrong.

As a club manager, I have edit rights to the club owner's objects so that I can redesign the club for events, fix problems, etc. Last night I discovered something odd, and wondering if there's a way around it.

If I select his object, then shift-click-drag the position arrows to create a copy, it copies fine. The object that moved with the arrows retains the original information such as owner, creator, group, and perms. The object that remained in place, however, has the original creator, me as the owner, and my current group. But, I have no perms. I can move it, but I can't retexture, unlink, etc.

I can do anything with the object with his name and original info. But the one that lists me as the owner now ... I can't do anything.

Bug?

Am I doing something wrong?

Is there a way around?

Does the prim you're copying have "next owner can modify" checked? If not that is probably your problem... the copy is the one that's left behind...

Yes, it does have "next owner can modify" checked ....

Odd. The drag-copy method can be a bit confusing, as the original gets moved and a copy gets left where the original was. What I found works best is to select the items, drag-copy, then select the ones left behind, drag them somewhere else to work with, and then re-select the originals and do an "undo" to put them back where they came from. That way, your friend's build remains entirely his content.

As for your copy... It may have something to do with scripts in the linkset. While the prims you copied may have been full-perms, if there were scripts or other things embedded within the prims that were NOT full-perms, the new linkset gets the more restrictive permissions.

shift-click-drag:
original moves and copy gets created at the original place.
copy changes its owner and can have less permissions for the next owner.
original can be moved back by "undo".

A lack of some object`s-inventory permissions can overwrite the objects permissions after the owner of the object changes, this is often via no-modify of scripts in objects.

When an object is deeded to a group, it changes its owner and can lose permissions by this, too.

OK ... thanks for the info. I'll keep trying to figure this out. The objects are unscripted. Not sure, but i don't think they are deeded to group. Just prims.

I'll play around with my alt and see if I can replicate the issue with things I'm building and know 100%.

Figured out the logic behind the problem ...

I logged in my alt on one screen, me on another. My alt created a plain cube, no scripts, no nothing. Set to full perms. I could edit / copy / etc ... both the copy and the original.

I had my alt create the cube again, trying various perms ... if "Next owner can ... MOD" is not checked, then it creates the problem. I can still copy the item, but I can only modify the original. I can't modify the copy, because now I'm listed as the owner ... aka the NEXT owner ... and can't mod it.

So, on the one hand, it keeps the avatar from passing items from one to another. But on the other, if I want to continue or modify a build someone else has started and want to just copy a wall / floor / ceiling/ etc ... to save time and keep exact dimensions and such ... it sucks because I can't mod the copy. I have to build from scratch instead.

But, at least now I know the issue at hand and that information allows me to work around it within the constraints of SL.