I am posting this here first in case there was a change in the way of "Step through" debugging in the McLua editor in the Hobby version.   Perhaps there was a post some where that noted a change, or there is a bug...

I put this simple function in the McLua and under debug, If I push run, it executes no issues.
But, if I run the debug in the step-through mode, as soon as you hit the F5 key to step through, it crashes the McLua.exe (get the McLue.exe has stopped working).  I have also tried putting just the "Testfunc()" by itself and commenting out the rest of the InEditor func. Again it will run with debug run, but not step through.
 
Can someone put this below func in your McLua editor, and see if you can step through it? I have tried breaks at each line as well, but the crash happens after you exit the function...

function Testfunc()
    local inst = mc.mcGetInstance();
    mc.mcCntlSetLastError(inst, '***  Testing  ***');   
end

if (mc.mcInEditor() == 1) then
    Testfunc();
end

--Thank you for looking/testing,

HIYA SCott, YES you broke it(;-). IT crashes here as well.   Here I developed a strategy of SAVING the file before you try to debug it that way WHEN you crash and loose it you have a backup to reload and try again.

That bug has been around since day one.

 Some scripts that appear just fine  crash the editor while others cause no problems.

Now that is just ME and HERE speaking. Take it for what it is worth.

(;-) TP

I have been debugging scripts that way since alpha, and for me it has not been crashing till lately......  Did the RC module, and my Multi-tool path screen using the debugger that way, and never once crashed.........

so, I guess a bug creeped in as of Hobby (latest version)? Maybe I was extremely lucky.... until now?

I think it is more that the editor does not know HOW to deal with some errors YET.

(;-) TP