Open Question: Prim/Object Mirroring

I won't update my Mirrorator until LSL gets llGetLinkPirmitiveParams()...

The code has been posted to the Script Library. It's available here.

Wah, I can't get it to work. It just says "Can't find object Object". Help help please Please!

P.S. I really really want this, this woudl be super cool! ^_^

1) potentially

2) absolutely, and it will be used as such because people do want to get free copies of nocopy objects, its already happened many many times through bugs and backdoors, this just throws the front door wide open

3) this should also be a must because you are using what amounts to an exploit to get texture keys and copy textures, regardless of actual texture permissions

4) this is no deterrent at all if people can simply comment out one line and get the 'full version'

5) its moot now (as you have released code) but this would have been workable combined with #4, but even then its still something that comes very close to basically making any mod+nocopy object 'public domain'

Yes - it's a very difficult and potentially-flammable issue. I discussed it with a couple Lindens, read all of the posts here, and held several in-world discussions before the script ever came to light.

... however, I'm going to have to go with a couple windfalls here that I forgot to mention - purely because the script is already "out there." If more valid concerns come to light, such that the script need be removed from the Script Library, I shall do it myself.

(This numbering does not address the numbers you left directly; I'm simply dividing my thoughts on the matter)

1) Addressing the concern of No Modify directly, it was actually brought up to me that many outfits rest on the laurels of "Modify" permissions to get the job done. Or, addressing your subset directly, furry outfits. After thinking the problem through, and talking with Lindens about it, I came to the conclusion that people that should know better can do this already. Such is the stipulation of leaving the objects as "Modify." This actually makes a very compelling case for the Lindens to add a new permission set for prims - "No Script." I'll be adding that to the Feature Suggestions forum.

In the short term, there are several protective measures one can take to prevent this, by anyone, in the short term. If you're very concerned about it, I wouldn't mind speaking to you, or anyone, on this issue. For my piece, I have added that extra line of security in the script itself, but as per concerns I may add additional "gimping" code as needed. Again, this is something I've done in the past with certain scripts that I've released with a potential to abuse, like my 3D Model Importer.

2) The script is not a "sure fire" thing. It has trouble in many cases, and must be added to each individual prim to be effective. Again, there's nothing new here - this has been around a while, as has "copy by numbers." The concerns that something like this makes it "easier to do," though, are valid - and again it makes a very compelling case for additional LL features if it becomes a large problem. Of course, "forcing them to find a reactionary fix" is not the intent either - but, hopefully, a proactive solution like I suggested will take place before trouble happens.

3) I will not be releasing a texture version in any way, shape, or form here, for the reason mentioned, eltee. This gives additional recourse to people that feel they may get "duped," as it's one of those things that's impossible to quote "copy by numbers."

In closing, I'd like to hear further from people that have concerns, not only for the sake of this script, but in general. That way, we can work toward a solution.

In response to the concerns brought up in this, and other, threads, I will be releasing a Universal Permissions Suite for use with No Modify objects. Expect to see this within a day or two in beta form - I just need to write documentation. The features included in my current (working) prototype:

- "Import" a Prim into the set via a handy Copy feature (No Modify prevents changes in links; this does not copy contents!)
- Use invisible prims in the set to allow users to "Add" Extra Prims with Copy!
- The ability to uniformly scale the entire object with a script (yay!)
- By Face and By Prim Support for Nearly Everything llSetPrimitiveParams allows (color, texture, position, rotation, scale, shininess, bumpmap, alpha, material, etc)
- Intuitive Dialog System using Contextual Listeners and Link Messages (no passive listens!)
- The ability to "tailor" the Permissions by removing options directly from the feature list quickly and easily
- Fully-featured Undo Queue (up to five entries; still a little buggy)
- Easily Remove the Scripts when Done with just a few clicks

Essentially, I have built limited modify functionality into No Modify, so builders with valid concerns that their objects can get copied will have a final recourse in preventing that, while preserving the ability for users to tailor the objects to their liking.