When in the editor go to the preferences, then Test Document, then make sure to have the Debug window checked. When you will encounter an error, the game will pause and allow you to check what is wrong and go to that specefic line in the debug window.
The errors are pretty self explanatory. One of them is an array out of bounds error (index larger or less than array size). The other is a random point in region failure (region null, 0 dimensioned or too complex so a point cannot be found).
Random point in region works by getting a random point in the bounding region and then testing if it is inside the region repeating at most 32 times before failure. For very complex regions with huge bounding boxes and proportionately very small valid area then there is a very small chance of success. For anything but the most simple primitive regions I recommend having a fall back point in case of failure.
As Scbroodsc2 mentioned, use the Trigger Debugger to analyse what is going wrong. Be aware that it works completely in Galaxy script (what GUI compiles to) so some programming experience is recommended. If you have any C or C++ experience understanding Galaxy script should be no problem.
ty yea it is super cool. hammincourt will launch the 4 drone sets next to have their lasers dodged. but applying the secret laser dodging formula is proving difficult and only the corner values will respond... so he is jumping rope until the values can be found.