Quote from Brontobyte
Quote from Clokr_
Quote from Brontobyte
Quote from Falkoner
I gotta admit, I think this may be more trouble than it is worth, most of these are really not that difficult to test yourself, and while the trigger firing one sounds useful, when you have over 500 triggers, imagine searching through a big list of what's firing..
It displays the trigger comment (if there is on) of which trigger is being fired.
Triggers fire inbetween game updates. So that wouldn't probably work well. It could display a list of the triggers that have been fired in the last trigger check, but a whole lot of triggers could fire at once, and with hyper triggers that would happen several times per second. It wouldn't be hard to make an util which logs the data into a log text file, but the text file would fastly grow too big.
EDIT: It could however log the last time at which each trigger fired. That could be useful.
You could maybe have it do specific searches for triggers instead of all of them at once.
If the game crashes it look through all of the triggers and figures out which one was fired last, or a bunch that were fired last that could have contributed to the crash, and also via waits. If a trigger has waits in it and other triggers run before the first one (with waits) is complete and the one with waits is the one that crashes, it should also show this.
None.