Editor Event Console And Asset Debug Dashboards

The event console and asset debug dashboards are the editor surfaces for understanding what the toolchain saw, what it projected, and which authored assets depend on each other.

Purpose

Use these panels when validation output is too broad, an editor action routes focus to a specific asset, or a performance/dependency/reward/tilemap issue needs a visual inspection surface.

Steps

Open the event console when an authoring action emits warnings, repairs, route payloads, or validation summaries. Filter by category, severity, or focus target. Use route/focus payloads to jump from an event to the relevant editor surface.

Open asset debug dashboards when the question is about asset graph shape, content browser rows, dependency fan-out, reward data, tilemap imports, or performance rows rather than a single validation error.

Expected Outputs

The event console should show normalized event rows with category, severity, source, message, and optional route/focus data. Asset debug tabs should show stable rows that can be refreshed without changing editor state unexpectedly.

Dependency dashboard rows should make upstream and downstream relationships visible. Performance rows should identify expensive or suspicious authoring assets. Reward and tilemap dashboards should expose the authored ids that runtime validators later consume.

Common Mistakes

Do not use the event console as a permanent data store; it is a retained projection of editor events. Do not add a dashboard tab that silently reparses assets differently from validation. Do not emit events without actionable source or focus information when the author needs to fix content.

Recovery Paths

If the console is empty, confirm the emitter is publishing into the shared event model. If focus routing fails, inspect the route payload type and target id. If a dashboard row disagrees with validation, compare the data loader used by the dashboard with the validator or bake gate.

If performance rows are stale, refresh the asset debug view and confirm the content browser is looking at the same asset root.