No modrights should *not* allow script dragging

Well then the solution seems to be leave scripts alone inside no-mod objects, because if someone wants to give someone else a script they can both look at and move around, they can just give it to them raw.

where did you get the yip yip? i want one


On Topic: *REMOVED*

Yip Yip Yip Yip Yip Yip Yip Yip

That doesn't work for SELLING the script Moleculor. I'm not going to hand sell a script to every single person I come across, nor am I going to agree to something that screws with $L1 boxes that contain multiple items with a variety of permissions set on them in a no mod box. (because if it was mod, you could modify it into what we mentioned before, and if it's no mod under your system, you can't use anything you bought).

Strife:Eckhart Dillon, but he really should be doing his own advertising ( I bought one from him).

Okay, you've made that abundantly clear. But as I said, nobody is stealing from you, they are just hurting your feelings. So please leave the "they stole from me" out of future arguments for your case.

It seems that all you want is more control over what happens to your scripts after you set them loose into the world. A scripting solution that removes the script from any item that you didn't create as well has already been presented. Does this not provide the answer you are looking for? Or is your only answer to take something that is working fine for everyone else and break it for them just to keep you happy? Because if that is the case, no amount of pleading, complaining, ranting and/or raving is going to help you.

I see how some people need it to behave as is. The solution should be finer grained access control.

We need a check box which says "don't let user drag this script off of object..."

In theory, the current behaviour is like letting someone delink and take a part an object they own. You can't so why can you drag the scripts around?

It doesn't make sense to me, but I guess after you've lived so long with something you start to rely on the craziness..

Also, can't see how onrez would do anything. All my objects need to rez..

And what is the point of llGetCreator() in the current state, btw? I'd really like to know..

i haven't tested that script that was posted before but what it's supposed to do is get the key of the creator of the object. so if you ran that function in the state_entry of the default state when they put the script in there own object it would self destruct the script. IE it would *solve* you problem.

string creator_name ="Your Name";
key creator_key = "put-your-key-here";

secureIt()
{
    if (llGetCreator() != creator_key)
    {
        llWhisper(0,"Sorry this script only works in objects created by " + creator_name);
        llRemoveInventory(llGetScriptName());
    }
}

state default
{
    state_entry()
    {
        secureIt();
        //put all your code here
    }
    on_rez(integer a)
    {
        secureIt();
        //put all your code here
    }
}

*edit for word*

or you could be really mean and kill their object too (llDie). I think as I pointed out before, a simple to attain finer method of control would be allowing a no mod/no copy/no transfer option for future owners instead of requiring one of them. I also think that solution would make just about everyone happy, except maybe one person :/

I have to agree in part with the permission system. I don't think it's totaly right to give out objects that are no-trans, no-copy & no-mod.