Just one comment. Having to enable it, then reset it is sort of putting the cart before the horse. Thankfully, since execution of the clients own operations are suspended while script executes, this hasn't been a real problem. From the logic standpoint though, its backwards, since, in theory, you could have a condition where the reset happens "after" the trigger fires, if somehow, for some reason, the reset and the enable do not happen in the same script execution.
Its very minor, probably never going to come up, etc., but it is, as I said, a tad backwards. More to the point, if anyone should ever create a thread system, which can allow non-synchronous execution (i.e., it can respond to triggers, etc., but not execute commands that send things to the mud, say for storing database info, updating character stats on a web page, or other situations that currently may cause too much lag, then it "will" be a problem, since in parallel execution, it is actually possible to have to script enable a trigger, it fire, then reset it. Its a potential future bug, should someone mod the client to allow such a threading system at some point. |