04-08-2014, 03:11 AM
If "F5" is fixing it for you, it means ZBS is in a breakpoint (and the second F5 is telling it to Continue). That is regular wanted behavior for regular Lua debugging - as soon as you start the script, you want the execution to halt and to give you a chance to set up breakpoints.
With MCS it's not so great behavior, so I used a configuration value debugger.runonstart to govern whether the debugger should break immediately or not. I'm not sure now what the default is, so if it's wrong for you, you may want to set it to the other value. In ZBS, select menu Edit -> Preferences -> Settings: System (or User) and ZBS will open the settings file for you, there you can set the value; I've got it set to true on my dev machines.
With MCS it's not so great behavior, so I used a configuration value debugger.runonstart to govern whether the debugger should break immediately or not. I'm not sure now what the default is, so if it's wrong for you, you may want to set it to the other value. In ZBS, select menu Edit -> Preferences -> Settings: System (or User) and ZBS will open the settings file for you, there you can set the value; I've got it set to true on my dev machines.