Quote:
Originally Posted by Stefan
Update: fixed it, will work fine with the next npcserver update.
|
Well please post when Valikorlia should restart to have the npcserver update.
Also I noticed that you seem to have changed the behavior of trigger(), if this was intentional than I'm very annoyed because that's not something you should change without warning. Example:
#1. trigger onSpecial() with trigger("Special", ...): FAIL
#2. trigger onSpecial() with trigger("onSpecial", ...): SUCCEED
#3. trigger Special() with trigger("Special", ...): FAIL
#1 is how it used to work, #2 is how it works now, and #3 shouldn't work either way, but you would think it would if #2 does.
I assume you've changed this to eliminate the inconsistency with functions that use event names and whether the "on" prefix is part of the event name.
Note: This is all on the same object, if it behaves differently when triggering other objects then I'd like to know.
Edit: #1 works fine when triggering to a different object, I guess doing #1 on self makes the event catchable by catchevent()?