triggeraction vs player.trigger

[Tyhm]

It's resolved now, but could you geniuses (not intended sarcastically) give the wiki a page on the modern communication styles? I think the last time I checked it just had a GS1 "triggeraction x, y, name, params;" page. :-P

And yeah, I like the aspect of triggers that is "Mail this data to this player and get on with your life", I just can't stand the "Throw a dart at the board and hope it hits the right player, and you can put the target's name in the parameters and check to make sure the target's right and dismiss it if it's wrong, and maybe you can have the wrong-target forward it to the right-target but there's no guarantee" aspect. I mean, what if jailing scripts had to take the account named, get their X and Y, and trigger on those coordinates iff you're within 6 tiles?! Madness.

[Inverness]

Originally Posted by WhiteDragon

Keep in mind that triggers are considerably slower than direct public function calls. However if you do not need quick response time, triggers/events are much more useful, especially because of the interface they provide with functions such as catchevent.

catchevent() does not work for scripted triggers on clientside yet