Hey, so I'm working on my map and I'm getting a "Trying to access value outside bounds of array" error, or something along those lines. I've tried finding the error for about an hour now but no matter what actions I turn on/off the error still pops up eventually. I am wondering if there is any way within the editor to see the source of an error that fires, such as the line that caused it or the section it is coming from. I know what function/trigger is causing it to fire because the error already gives me that information, but I am trying to get more specific information on the error so that I can narrow down its position. The problem here is that I am working with multiple arrays and it is challenging to discern which one is actually giving me the issue. Any help here would be greatly appreciated. Thanks.
Blizzard recently announced that a the next patch will include a trigger debugger that will do exactly what you want. In the meantime, I'm not aware of any other way to pinpoint the cause of your problem.
Maybe you can try printing out an in-game message of the index values as they're being used in that trigger. That way you'll be able to see if anything comes up negative or greater than the size of your array.
Hey, so I'm working on my map and I'm getting a "Trying to access value outside bounds of array" error, or something along those lines. I've tried finding the error for about an hour now but no matter what actions I turn on/off the error still pops up eventually. I am wondering if there is any way within the editor to see the source of an error that fires, such as the line that caused it or the section it is coming from. I know what function/trigger is causing it to fire because the error already gives me that information, but I am trying to get more specific information on the error so that I can narrow down its position. The problem here is that I am working with multiple arrays and it is challenging to discern which one is actually giving me the issue. Any help here would be greatly appreciated. Thanks.
@DaveSilver: Go
Blizzard recently announced that a the next patch will include a trigger debugger that will do exactly what you want. In the meantime, I'm not aware of any other way to pinpoint the cause of your problem.
Maybe you can try printing out an in-game message of the index values as they're being used in that trigger. That way you'll be able to see if anything comes up negative or greater than the size of your array.
Thankfully I was able to find the source of this error since posting the original question but thanks anyway Khaztr.
Also, that is awesome news to hear about the next patch. I am now super excited for it.