The toolbar across the top of the dialog collects the debugger’s main actions. Every action has a keyboard shortcut that also works when the focus is inside the script editor.
The standard step controls:
| Action | Shortcut | Effect |
|---|---|---|
Continue |
| Resume until the next breakpoint. |
Step Over |
| Run the current line and pause on the next line in the same (or outer) stack frame; calls run to completion without pausing inside. |
Step Into |
| Run the current line and pause on the very next Lua line, including lines inside functions called from the current line. |
Step Out |
| Resume until the current function returns, then pause in the caller. On the outermost Lua frame this behaves like Continue. |
The remaining toolbar actions:
Ctrl+F10) — set a one-shot target on
the line under the editor cursor and resume; pause there when (and
if) the target is reached. Enabled only while paused with an
active editor tab. See Section 14.8, “Breakpoints”.
.lua file in a new editor tab.
Ctrl+S) — write the active editor tab to disk.
Enabled only when the active tab has unsaved changes.
Ctrl+Shift+L) — re-run the full Lua
plugin load sequence (global then personal plugin directories) in
a fresh Lua VM. Breakpoints, watches, and editor tabs survive the
reload; anything the previous Lua state had stashed in globals
does not.
Next to the toolbar the dialog header carries the Enabled checkbox; its colored dot mirrors the current debugger state — see Section 14.1, “Introduction”.