Passing a delete request

Not sure how to start on this one so it may be a product request but here goes:

I have several creations that when touched rez another part which (in most cases) is within the originally rezzed Prim. When the user is done with it they have to delete the main Prim and the additional Prim-rezzed prim. Is there a way to pass the delete requested received by the original Prim to the secondary prim as well so that both are deleted in one request?

Thanks as always.

A prim can only be deleted from a script within it(or an Avatar), so it all depends on the script to what request it will respond by deleting the prim. All your prims could have a script for that purpose. It would listen on a specific channel for a specific command.

Well, if they are linked, just use llDie. See --> llDie "deletes the object that contains the script. That means if the prim containing this script is part of a linkset, all the prims will be deleted, regardless of whether or not the prim is the root or a child in the linkset. To delete just one prim from a linkset, first detach it with llBreakLink."

If the prims aren't linked, then you could either link them and then delete, or you could take the long route and put a tiny script in each rezzed object that listens for the original prim to send a llDie message.

The objects are not linked and the internal one is actually constructed of multiple prims and rotates so I don't think I want them linked. The Listening thing sounds interesting but I have not worked with that function yet so I will have to investigate. Does it involve getting UUIDs?

Nope. Just write a pair of scripts. In the original object, it should look something like this ....

 
gChannel = -3456; // Or whatever negative number strikes your fancy
default
{
touch_start(num_detected)
{
if(llGetOwner() == llDetectedKey(0)) // Don't pay attention to anyone else
{
llSay(gChannel, "Die! DIE! DIE!"); // Tell the other prims to die.
llSleep(3.0); // Take a deep breath and then ...
llDie(); // Farewell ..... poof!
}
}
}
 

And in each of the other objects, it should look like this ...

 
gChannel = -3456; // Same as in the parent script
default
{
state_entry
{
llListen(gChannel,"",NULL_KEY,""); // Listen only to messages on channel -3456
}
listen( integer channel, string name, key id, string message )
{
if(message == "Die! DIE! DIE!") // Only obey this specific message ...
{
llDie(); // And then vanish .....
}
}
}
 

If you really get paranoid about some other object yelling the DIE message on gChannel, you can always replace NULL_KEY in the listen event with the UUID of your parent object, but that's such an unlikely possibility that it's not worth the trouble.

EDIT: Ah.... I forgot that you want to delete the original object as well. I have just added that llDie() to the first script.

And remember to use llRegionSay instead of llSay because it involves less processing for the sim.

I would prefer llRegionSay() for llSay() in the parent script and I would prefer the message as a filter like this:

gChannel = -3456; // Same as in the parent script
default
{
    state_entry
    {
        llListen(gChannel,"",NULL_KEY,"Die! DIE! DIE!"); // Listen only for the exact messages on channel -3456
    }
    listen( integer channel, string name, key id, string message )
    {
        llDie(); // And then vanish .....
    }
}

If you can have the child object find out the key of its parent object (e.g. have the parent announce that it is the child prim's parent on an agreed-upon channel), you could also use sensors or (preferably) llGetObjectDetails() to detect when the parent object is no longer around and call llDie().

two suggestions for listen driven prim killing.

one) have the rezzor (when it is initially rezzed itself) generate a higher negative number to use as the kill channel, and pass it to all the prims it creates via the start parameter.
[this reduces crosstalk between multiple rezzors of the same type)

two) filter with (llGetOwnerId( Id ) == llGetOwner)
this prevents someone elses rezzor from affecting yours.

if the user isn't using some kind of scripted kill, just a pie menu delete, you'll need one of the rezzed objects to run a sensor for the rezzor, and then pass it's message of death (don't put sensors in all the rezzed objects. if all the secondary objects are the same, just add a copy of the first one and insert the sensor script, and use an onRez variable in the rezzor script to make sure that one gets rezzed first, and the ones after it are the normal ones.

Ahhh, I think Void hit this one on the head, yes, the person deleting the main object will be using the Pie menu. This mean that your suggested solution is a bit beyond my abilities. So it looks like this may be a "for pay" job. If anyone wants to tackle it, please let me know.

I'd offer but I can't concentrate on my own work atm.

@wyatt:
just remember that the sensing prim should be interior to the rezzing prim (or otherwise blocked) so that it doesn't get deleted first. otherwise you need at least 2 sensing prims just in case

HI,
I tried to paste that into a script, but it gives me an error.

[/php]

gChannel = 100; // Same as in the parent script
default
{
state_entry
{
llListen(gChannel,"",NULL_KEY,"Clean"; // Listen only to messages on channel 100
}
listen( integer channel, string name, key id, string message )

{
llDie(); // And then vanish .....
}
}
[/php]

Can someone help me with this (very newbee at scripting).
Thanx!!!
Maggy

Dora helped me:

state_entry()

does the job.