k, sandy, that's nice bump
Just wandering, if we keep adding events (expecially unsollicited events), how much noise is this gonna get, and how much extra-cpu requested.
To tell the truth, it'd be nice to extend the aggro event to a 'come in range' event, hence move it from attack.cpp to Mob::AiCheckCloseArrgo. It can then be used for more social quests, for NPC to hail friends, or potential customers, not just aggroed mobs.
There definetly is need for a 'here-is-info-related-to-positions-on-the-map' event. EVENT_AGRRO is ok, but, while you're on the topic, why not a EVENT_INRANGE, with setNextRange, just like you did for EVENT_HP. That was nice.
Threaded Mode
