I know this script debugger and I use it for a lot of time. It slows the game 10 times and can not be turned off (unless you exit the game and run it without debug mode). So, it can help only with initial base building. If you have an error in later game then you are forced to wait for 2-3 hours. Also it can't detect crash bugs. When crash happens, debugger crashes too and even does not show you the reason.
(beware of bragging geeks)
The speed doesn't slow down on mine enough to notice...
What I started doing last night is I start World builder on the right side screen, and work on scripts. then after I compile a build I leave it open, and on the left side screen I run ZH with the debugging tool turned on. while it runs I go back to world builder and start working on it again. I just leave the Debug tool running until it hits a critical problem. Then I just close the debugger, I run the next compile, shuffles some files around to keep a history of every build, and start up the debugger again. I only have to stop scripting to watch when it gets to an important spot.
Doing it this way has been great. I can watch the problem scripts while I fix them at the same time. Much smoother. Also, I played around with partial exports and imports, and they work well. If I have a good copy of Robot USA AI, then all I have to do is export just that sript set and save it seperate. If only certain generals are giving errors, those general's can be deleted, then imported from an old version without loosing work on other generals.