Doesn't it work that you put down just no_sensor?

hmm... I might miss something. But if anyone knows about this, please tell me that.

default
{
    state_entry()
    {
        llSensorRemove();
    }
    touch_start(integer total_number)
    {
        llSensorRepeat("", "", AGENT, 2.0, PI, 1.0);
    }
    no_sensor()
    {
        llSay(0, "Nobody is here.");
        llSensorRemove();
    }
}

Put this script into a prim and touch it while you stand near by it. Then you walking away, it should say, "Nobody is here". But it didn't work.
But I found it work when you put down a vacant sensor event like below.

default
{
    state_entry()
    {
        llSensorRemove();
    }
    touch_start(integer total_number)
    {
        llSensorRepeat("", "", AGENT, 2.0, PI, 1.0);
    }
    sensor(integer num_detected)
    {

    }
    no_sensor()
    {
        llSay(0, "Nobody is here.");
        llSensorRemove();
    }
}

Does this make sense?

I suspect it's some kind of bug... perhaps in the way the bytcode is assembled, as the event trip for a sensor is only installed if there's a sensor() event, which no_sensor() relies on.

But no... it doens't make much sense.

if a prim in a forest says "nobody here" and no one is around to hear it, does it really make a sound?

I ran into this a week or two ago myself, when making my vehicle return to my inventory (lost & found folder) if I were killed while piloting it. (by using warpPos to fly off the world)

I wouldn't really call it a bug - more of an annoyance.

So that s what all those extra voices in my head are!!!!!!!!!!!!!!!!!