beasty-debug-logger / getting-started.md

Getting started

From an empty project to a classified log in the Beasty Console, in about two minutes.

Requirements

  • Unity 6000.2 or newer.
  • No dependencies. The package references no other asset and no external library.
  • The logging API works in the editor and in builds, on every platform. The Beasty Console window is an editor tool.

Import

Import the package from the Package Manager, under My Assets. It installs into Assets/BeastyComponents/BeastyDebugLogger/:

  • Scripts/ — the logging API. This is what ships in your build.
  • Editor/ — the Beasty Console window. This never ships.

Nothing to configure. There is no settings asset and no scene setup.

Your first log

Add this to any MonoBehaviour:

using BeastyDebugLoggerConsole;

BeastyDebugLogger.LogInfo("Save file loaded.");

Enter Play Mode. The line appears in Unity’s own Console, in green, with an info tag in front of it.

Open the console

The window is at Tools > Beasty VN > Diagnostics > Console.

Note The window lives under the Beasty VN menu even though this package has no dependency on Beasty Visual Novel and works fine without it. The menu path is shared; the code is not.

What you see:

  • A toolbar: Clear, Collapse, Clear on Play, Error Pause, and a search field.
  • A second toolbar of filter toggles, one per level, each showing how many entries of that level have arrived. Click one to hide that level.
  • The list, one row per entry: the level glyph, the time, the message.
  • A detail panel below it. Select a row to read the full message and its stack trace.

The console does not replace Unity’s Console. It listens alongside it, so it shows every log in the project, including plain Debug.Log calls from your own code and from third-party packages.

Next