diagnostics-and-logging

Centralize Unity debugging by replacing Debug.Log statements with the ReportHub system, which routes logs consistently across the application. You categorize logs using ReportCategory tags and control their visibility via a CategorySeverityMatrix.

You can adjust log levels at runtime without rebuilding by applying runtime overrides to specific ReportCategory tags. This dynamic severity matrix adjustment allows you to temporarily increase log verbosity for targeted features causing unexpected behavior.

Sentry integration for remote error tracking works by routing logged exceptions and errors from the ReportHub system directly to Sentry. This captures application issues remotely while an exception tolerance mechanism prevents scene errors from crashing the application.

Organize Unity logs by tagging systems with LogCategory entries and manage their visibility through a CategorySeverityMatrix. This categorization and severity configuration ensures only relevant diagnostic information is surfaced based on your configured log levels.

Scene errors can crash Unity applications, but you can prevent this by utilizing an exception tolerance mechanism. This diagnostics and logging feature catches scene errors and reports them through the ReportHub system instead of terminating the application.

The diagnostics and logging Skill supports dynamic log routing for specific Unity features by assigning them a LogCategory, such as VOICE_CHAT. You can then use chat commands to temporarily override log verbosity for that category to pinpoint root causes.