temporary rezzer won't stop rezzing

nevermind

One easy way to beat that is to forget about using a sensor. It can be laggy anyway. Make an 8m diameter transparent cylinder to put your rezzer script in, and then write something that looks like this

default
{
     state_entry()
     {
          llVolumeDetect (TRUE);
     }

     collision_start(integer num)
     {
           llRezAtRoot(llGetInventoryName(INVENTORY_OBJECT,0) , llGetPos(),ZERO_VECTOR,ZERO_ROTATION,0);
     }
}

ETA: Pffft! The OP took his question away. FOR THE RECORD, though, he wanted to know how to make a rezzer create one object whenever an av comes within range.

Hmmm... A sensor is supposed to create lag, so here comes a low lag solution without listener to rez an object if an AV comes within range.

The script for the rezzer:
-------------------------------------------------------------------------
integer isREZZED = FALSE;
key ObjectKey = "";

default
{
state_entry()
{
llSensorRepeat("", NULL_KEY, AGENT, 4.0, PI, 5);
}

sensor(integer total_number)
{
if (!isREZZED)
{
llRezObject(llGetInventoryName(INVENTORY_OBJECT, 0), llGetPos(),ZERO_VECTOR,ZERO_ROTATION,0);
isREZZED = TRUE;
}
}

no_sensor()
{
if (ObjectKey != ""
{
llGiveInventoy(ObjectKey, llGetInventoryName(INVENTORY_OBJECT, 0));
ObjectKey = "";
}
isREZZED = FALSE;
}

object_rez(key id)
{
ObjectKey = id;
isREZZED = TRUE;
}
}
-------------------------------------------------------------------------

And in the rezzed object:
-------------------------------------------------------------------------
default
{
changed(integer change)
{
if (change & CHANGED_INVENTORY)
{
if (llGetInventoryType(llGetObjectName()) == INVENTORY_OBJECT)
{
llDie();
}
}
}
}
-------------------------------------------------------------------------

In words: The rezzer script must know if the object is already rezzed. It also stores the key of the rezzed object so, when it's time to clear the place, it gives a copy of the object to the rezzed object. And when the rezzed object realizes what it has in its belly, it explodes... sort of...

ETA: The OP deleted his question... So I delete every mention to him.

also remember that every few cycles llSensorRepeat can grab avatars outside it's range IF that range is near a sim border... llSensor called from a timer does NOT exhibit this weird behavior.

Bingo! Stumbling across that snippet of information has made my day

guess I should note that on the wiki... some thing you just find out the hard way (I ran face first into this bug on my av sensor)

ETA:
wiki annotated, and it's back up