Console

The Console shows editor messages and your scripts' log output. It is where import results, save confirmations, compile errors, and api.log calls from a running game appear.

What logs here

Editor messages - a running record of what the editor did: imports, saves, scene changes, compile results, object creation/deletion, and errors.
Script output - during Play, api.log(...) from your scripts writes here (in a shipped game the same call goes to the browser console). See the ScriptApi reference.

The Console keeps a rolling buffer of the most recent lines and auto-scrolls to the newest as they arrive.

📸 Screenshot - save as img/editor-console.png

The Console panel after an import and a Play session: a few editor messages, some script api.log lines, with the filter box, "clear on play" and "time" toggles, and the copy/clear buttons in the bar.

Controls

The bar across the top:

Control	What it does
Filter…	Show only lines containing the typed text (case-insensitive). A ✕ clears it.
clear on play	Auto-clear the console each time you press ▶ Play - start each run with a clean slate.
time	Prefix each line with the time it was logged (`HH:MM:SS.mmm`), enough precision to order rapid logs.
⧉ Copy	Copy the currently shown (filtered) lines to the clipboard, formatted exactly as displayed. Flashes ✓ copied.
🗑 Clear	Clear the console.

The filter is transient (it resets between sessions), but the clear on play and time toggles are remembered across reloads.

During Play

Because api.log routes here during Play, the Console is your primary debugging window while testing in the editor. Pair it with clear on play so each run's output stands on its own, and time when you need to see the ordering of fast events. For collision and physics debugging alongside it, see the Viewport's F4 overlay and Physics debugging.

Console ​

What logs here ​

Controls ​

During Play ​

See also ​

Console

What logs here

Controls

During Play

See also