Event_proximity_say

[joligario]

May want to ignore "hail" in that if you are going to do non-target responses. Would be funny to hear 10 NPCs in PoK respond to 1 hail...

[trevius]

You may be misunderstanding what this is for. This will not effect how any current NPC scripts work. So, you won't see 10 NPCs in pok responding to a hail unless that is something that was setup specifically to be that way by the script writer. I don't think hail should be ignored. If someone wants hail to require a target, they could set it that way.

What if I wanted to write a quest where people have to go through a zone looking for an invisible NPC and the only way to find them is by running around hailing to see if they get a response?

sub EVENT_SPAWN {
   $x = $npc->GetX();
   $y = $npc->GetY();
   quest::set_proximity($x - 500, $x + 500, $y - 500, $y + 500);
}

sub EVENT_PROXIMITY_SAY {

        if($text=~/Hail/i) {
                quest::me("A mysterious voice responds from the darkness.");
                quest::say("So, you have found me at last.  Would you please [free] my soul?");
        }

#and so on...
}

IMO, the proximity say should have no restrictions, because any wanted restriction could be added by the script writer in the individual script. Proximity say probably won't be used overly much, so there isn't much reason to set restrictions on it. But, it will certainly be nice to have the option to use it now.

I didn't check the code for it yet, but I was curious if Proximity says would work even if the NPC has aggro on the player?

[joligario]

Ah, I see. Yeah, no problem then.

[trevius]

I went ahead and removed the No Target requirement for proximity says. So, now you can have a target and still trigger a proximity say, which I think makes them a bit more flexible. You can still check for a target within the script easily enough if you really don't want the player to have a target when triggering a proximity say.