Permissions for builders

I have done several scripts for builders, for them to include in their projects. In the past, I have sold them copy/transfer/nomod generally, trusting the builders to not just pass out copies of my work. I don't know that anyone has abused that.

But I'd like to make something a little more "secure". What I would like to see, and I can't think right now how to make it happen, is that the builders receive a copy of the scripts that are copy/notransfer. When they are ready to sell their product which includes my script, I would like to see that change to nocopy/transfer. I know that I can make a single script that is notransfer, but is required for setup, which will make the whole system notransfer. Then, when it is set up, I can delete that script. But is there a way to have the whole system go no-copy then? I want the builder to be able to copy this and use it in different builds, but I do not want the customer to be able to pass it on.

Ideas?

Thanks,
Baron

Hiya Baron! Nice to see you again.

I've been using the NDE scripts for windows, doors, tpers. And they are sent at copy/nomod/trans. However, they will NOT operate until you have changed the script to copy/nomod/notrans. Brilliant.. it allows me to put it into my builds and then I MUST change the perms to sell the build or they won't work.

Oh! That is great, I had not thought of that. I saw that I could *read* permissions, but could not change them. I'll try that! Thanks

But from NDE's pov... what's to stop you (JessyAnne) from reselling the scripts? I think that's the issue Baron is trying to solve...

Maybe with the new function you can find out the creator of the object that contains the script - I haven't installed the new viewer so haven't tried out the new function either. You'd have to hardcode the key of the person you're selling it to, but it'd prevent them from reselling just the script.

Personally I write custom scripts that I hand over full perm. I don't care if they resell it as long as I was paid enough money for writing it.

Well, I've got a couple of other things to go in place to help . . . but that was enough to satisfy. Basically, I know that almost anything can be worked around if one tried hard enough. For obvious reasons, I don't want to go into everything here, but one thing I do is check to see who owned it last. If it wasn't me (or the client who is actually requesting this function), then the script knows that it is either an end-user or it was gotten illicitly.

Mainly, I'm trying to make it so that an innocent buyer realizes if the seller did not have permission to distribute it.

I've got to admit that it's impossible for me to determine whether or not a customer is actually selling the -scripts- themselves. In fact, I caught a business (Dawn3D) selling NDE Doors against the reseller-agreement just last week. Security can only go so far. However, I still believe that builders are in need of resellable doors, windows, teleporters, etc.

BTW...the forced permission setting is achieved through an llGetObjectPermMask(). It has dramatically decreased the "cheating" I had previously experienced with my products. It's not only good for myself--but the customers who are honest and actually pay for the product appreciate that competitors aren't getting a free 'black-market' version.

Really, the only way to prevent the kind of cheating the OP is worried about is to hard-code in the key of the reseller, and if the script is not in his works (ie, as the creator), it won't work (or does a llDie()).

Doesn't work too well for vended scripts, unless you do something like sell a no-transfer demo version for them to build with, then have them come directly back to you and request a resellable version that you supply directly.