Skip to content

Console Log Editor

The Console Log in Scriptum’s Editor Mode provides a powerful, isolated log stream dedicated to Scriptum execution feedback, including evaluation results, errors, and runtime logs — all separated from Unity’s noisy default console.

It’s your private channel for scripting output, system feedback, and debugging info, focused only on what Scriptum is doing.

What Does It Show?

Scriptum’s Editor Console Log captures:

  • Evaluation results from editor scripts
  • Runtime warnings (e.g., bad bindings, failed reflection)
  • Errors from code execution (syntax errors, null refs, etc.)
  • Feedback from built-in commands

It helps you debug and iterate without leaving the Scriptum environment, and without sifting through Unity’s general console spam.

Execution vs Unity Logs

By default, Scriptum mirrors Unity’s error logs (warnings and exceptions only), so if a Unity system error happens during a Scriptum eval (like MissingReferenceException), you’ll see it in the Editor Console Log too.

This ensures that contextually related errors appear where you're coding.

Unity errors shown in the Scriptum Console are passive mirrors — you can toggle this behavior.

Preference Control

If you want to filter out Unity’s logs and only show Scriptum’s own execution logs:

Go to Preferences → Editor
and disable the toggle:
Mirror Unity Logs

With this off, Scriptum’s Editor Console becomes a pure sandbox — no Unity noise, just the logs you care about.