Log inGet started
What it does

runtime

Merged Runtime tab — three collapsible sections (Luau VM, Engine memory, Heap history) that replace the older split Luau-VM + Memory tabs. The Luau VM section shows the heap and per-script timing; the Memory section shows CPU/GPU/ECS counters; Heap history is a bounded 120-sample sparkline. Refreshes at 5 Hz to match the faster of the two predecessor tabs.

Exports

  • M.build(_state) -> any — build the zui widget tree for the tab.
  • M.onCallback(callbackId: string, _data, _state) -> boolean — handle Force GC, Snapshot.
  • M.label: string — tab title.
  • M.refresh: number — refresh cadence in seconds (0.2).

Usage

local Runtime = require("@builtin::modules.engine.editor.system_tools.tabs.runtime")
local widget = Runtime.build(state)
Runtime.onCallback("runtime-luau-gc", nil, state)

Notes

  • The Luau VM and Memory sections default to open; Heap history defaults to closed (it's supplementary).
  • Heap-history is sampled every build (5 Hz when the tab is active), capped at 120 samples. Older samples slide off the front.
  • "Force GC" calls the luauGcCollect global and invalidates the VM snapshot cache so the next refresh shows the post-GC heap.
  • Per-script rows sort by avg_update_ms descending; the sort field is module-local and not currently surfaced as a control.

Interface

What this asset declares: the schema it conforms to, what it exposes, and the rendered structured payload.

This asset doesn't declare a schema or structured payload.

Sub-parts

Everything contained inside this part. Assets are composite children (clickable cards). Files are leaf payloads. Expand any row to view its source.

0items
This part has no composite children. See the Files segment for its leaf payloads.
This part has no leaf payloads.

Problems

Everything affecting this asset right now: its own problems, anything wrong inside it, and problems on its direct dependencies.

0problems
No problems reported. This asset, its contents, and its direct deps are clean as of the latest commit.
⌬ZeroMind agent review · awaiting first pass
Findings
Reviewer findings (handle · model · tag · quoted note) appear here once the per-pass review log lands. Today only the rolled-up agent_score is exposed.
usability—
did it work as advertised
quality—
authoring polish + cohesion
performance—
frame & memory budget held
agent review score
—
/ 100
awaiting first pass
usability × 0.40
+ quality × 0.35
+ performance × 0.25
± compat factor

Usability ratings

Did the part work as advertised when consumers tried to drop it in. Separate from upvotes: those are taste; this is "did it function".

—%no reports yet
Sign in to report whether this part worked for you.
Discussion

Scoped to this part · feeds back into the world's score.

0comments
Sign in to post.sign in
No comments yet. Be the first.