skTrace

[0.1.5] - 2026-08-05

• Added /sktrace loops, a live view of the loop and while sections running right now: what each one is, where it lives (script:line), the iteration it's on, how fast that number is climbing, how long it has been going, and how many copies of it are running at once. It's built for the loop that "just keeps going" - the one you'd otherwise hunt down by scattering broadcasts through your code. A counter that keeps climbing and never clears is your runaway, and the row turns amber, then red, as it starts to look like one.

• Added a Loops panel to HTML reports, listing every loop seen running during the capture with its peak iteration count, peak concurrency, and whether it was still going when the report was written. The panel stays hidden when no loops were observed.

• Added frozen-server detection for the case the loops view cannot cover. A loop with no wait inside never yields, so an infinite one pins the server's main thread and nothing in-game - not even /sktrace loops - can run. skTrace now watches for that from its own background thread and, once the server has stopped ticking for loop-hang-seconds (10 by default), logs the responsible loop's script:line to the console, the one surface still alive during a freeze. It is detection only: it never stops, kills, or interrupts anything. Turn it off with loop-hang-detection: false.

• Loop watching is on by default and safe to leave on: unlike line-level-profiling, it only reads the iteration counter Skript already keeps for every loop and never rewrites how a script runs. Loops are found once, when profiling starts, and sampled about once a second on skTrace's existing tick task, so there's no new scheduler task and no per-iteration cost. Only loops that span ticks (that is, contain a wait) can be observed - a no-delay loop finishes inside a single tick, leaving nothing to see. Disable the whole feature, including the startup scan that finds loops, with loop-watching: false.

• Fixed skTrace claiming per-trigger timing was unavailable on your Skript version when it was working fine. If a capture ever started at a moment when no event triggers were loaded (every script is commands or every N seconds, or scripts had not finished loading yet), the warning latched on and stayed on for the rest of the server's life: every later /sktrace start repeated it, and every report was stamped with it, including reports whose Triggers table was fully populated. An empty registry is now recognised for what it is, "nothing to hook yet", and the check is re-run on each capture instead of being decided once.

• Fixed every Skript command collapsing into a single report row called simple event "simple event". Skript builds a command's trigger on a generic event whose own label is that placeholder text, so all of them shared one name, and sharing a name meant sharing one set of timings: three commands showed up as one row, at the line number of whichever unrelated trigger happened to be registered first. Each command is now its own row, named after the command (command /home), and other triggers that use the same generic event fall back to the event line you actually wrote.

• Fixed /sktrace reset quietly ending per-trigger and per-function collection for the rest of the capture. Only event-level timings kept recording afterwards, so the Triggers and Functions tables stayed empty until the next script reload or profiler restart, with nothing to indicate why. Collection now resumes immediately.

• Fixed /sktrace reset not clearing function times, so after a reset the Functions table showed lifetime totals next to a freshly reset window.

• Changed the console output of /sktrace start. The hook-install detail (registry scan, per-field dump, hooked counts) is now off by default, since it repeats on every capture and every /sk reload and says nothing an operator can act on. Set debug-logging: true in config.yml to bring it back, or run /sktrace diag, which dumps the same Skript internals on demand. Genuine problems are still logged as warnings either way.

All Verified against Minecraft 26.2 on Skript 2.16.1