Leaderboard

While the basic idea is valuable, AutoIt doesn't bend easily to such exhumation. I'm just giving my opinion: a much robust way to code routinely serious programs is to properly handle errors at the moment they occur (such as a file locked by another process, I/O error, any unexpected error cause). All "internal" errors (like the classical index of array out of bound) are not errors in my view, but programming mistakes. Instead of making your code massively complicated and harder to maintain by using "where did I goof in fact?" post-mortem technique, place your focus in checking invariants. I almost never saw any use of _Assert in code published here, but this is a much safer/cleaner way to explicitely check subtle conditions you have doubts on hard-to-chew logic. Once you get confidence that your code is correct (it doesn't seem like, but "correct" is a very strong word in algorithmics), it's very easy to comment out all _Assert lines (edit: or comment out _DebugStartup). Note that this still doesn't prove your code correct: that would require formal methods that are even one (huge) step higher in abstraction. EDIT: btw, there is a good visual debugger in the example scripts. Hope you don't mind a diverging opinion!

I think you need to provide a small working version of the script. If this works initially there will be not much to find just by looking at the code pieces above. It may also be a flash specific problem.

I would pass all variables I need in a function as parameters.