unity-console

Capture Unity console logs by starting a buffer capture before entering play mode and stopping it when finished. This isolates the specific runtime messages and errors generated during your play session for debugging.

Yes, you can filter captured Unity console logs by message type, specifically Log, Warning, and Error. You can also apply result limits to narrow down the retrieved entries and focus only on the relevant issues for your debugging session.

Export Unity console logs to a file by capturing the console buffer during your test session and using the export function. This saves the filtered entries and provides counts by message type for reporting and automated CI analysis.

Manage Unity Editor console settings by toggling features like collapse, clear-on-play, and pause-on-error directly. This streamlines your debugging workflow by automatically organizing the console output and halting execution when runtime errors occur.

Yes, this Unity console log capture is designed for automated test sessions and CI log collection. You can start capture before running tests, reproduce issues, and then retrieve and export only the Error entries for triage.

Clearing the Unity console before starting a new debugging session removes old entries from the buffer. This ensures that the captured logs only contain messages from the current play mode or test session, preventing confusion during error analysis.