Line by line debugging for greed?

Hey is there a way I can set a breakpoint for my code? The hover debugger is great but I really need to see values at specific times in my for loop. I’ve been using a combination of the hover debugger and just “base.say” Is that the preferred method right now?

I’m working to get the statement counter working again in this level soon, after which you’ll be able to not only see statements per call and number of calls from the spell debug toolbar, but you’ll be able to step through your program’s execution once more. Not sure we’ll be able to performantly get the values snapshotted after each statement working again, but perhaps that’ll be in, too.

What is the the spell debug toolbar?

1 Like