Fancy properties on prims will not stop copying.

It won't work because at the level this is working the permissions don't /matter/.
It can access all the parameters of the prims themselves, so any flags set can just be ignored while duplicating the settings. Not unless the protocol is rewritten will the copier be slowed down.

This does not copy the contents either.

It simply polls all the prims for their texture, shape and link data, and creates new prims, and links, shapes and applies the texture to them.

I'd bet that it's NOT a true copy -- it's like looking at a shaped prim on the ground, placing down a cube, and then twisting it into the same shape. The copy that's been created is a new item, not truly a copypaste of the original. But the texture ID is.

Essentially... the prims are created. Only the textures are truly copied.

If I could trust anyone from libsecondlife to verify this, I'd ask. But frankly, I have no love nor trust for this.

Strangely enough, the tempation to go look at the code just to answer such questions is very strong . I am quite experienced in software dev, and fairly confident that I could answer the question by looking at the code. But if I did, I feel that there are too many people that would become mistrustful of me It's just not worth that risk, imo.

But somebody else out there will do so, perhaps even a Linden (aren't there Lindens that are familiar with libsecondlife?), and will post a definitive or at least largely credible answer. Surely somebody is trying to do so already?

heh