Price history
Recorded standalone sale prices and the latest available store price, in USD. Historical dots use the sale start date and its recorded offer price. Prices can change during a sale; this is not a daily price log. Bundle prices and upcoming offers are excluded. History covers up to the 100 most recent recorded offers.
Lowest recorded standalone price in this history: FREE. The latest store price is FREE, matching the lowest recorded price shown here.
View 2 recorded prices
| Sale start / price check | Price | Observation |
|---|---|---|
| FREE | Latest store price | |
| FREE | Unity First Price 2026-06-20 2026-06-27 |
Sale and bundle history
The 1 most recent recorded offers including this asset. Past offers may no longer be available. Bundle prices cover a package, not this asset alone.
About LAC Debug Logger
- Tools, Systems & Learning > Development Tools & Automation
LAC Debug Logger — Tag-Based Unity Logging & Console Filter
LAC Debug Logger is a lightweight Unity debugging tool that replaces scattered Debug.Log calls with a structured, tag-based logging system. Filter Unity console output by category, write structured log files for Editor and builds, and manage everything from a focused editor window — without touching your code or recompiling.
Whether you are tracking AI behaviour, physics interactions, UI events, or any other game system, you define the tags, and the logger only passes what you need to the Unity Console right now.
Tag-Based Console Filtering
Define unlimited custom log categories (tags) in the editor window
Toggle any tag on or off instantly — active tags appear in the console, inactive ones are silently dropped
Bulk controls to enable or disable all tags in one click
Untagged log calls always pass through, so third-party and legacy code is never silenced
Structured File Logging
Write log output to .txt files in the Editor, standalone builds, or both
Each entry includes timestamp, severity, scene name, and tag for easy filtering in any text editor
Choose a custom save path via folder browser, or default to Application.persistentDataPath
Automatic 5 MB file rotation — active log is archived before a new one starts
Flush on application quit, flush when buffer reaches a configurable entry limit, or call DebugLogger.Flush() from code at any time
Clean API — Drop In, No Setup
DebugLogger.Log("Pathfinding complete", "AI");
DebugLogger.LogWarning("Overlap detected", "Physics");
DebugLogger.LogError("Missing reference", "UI");
DebugLogger.LogVerbose("Frame data", "AI");
Editor Window (Tools > Debug Logger)
Add, remove, enable, and disable tags without leaving the Editor
All / None bulk tag toggle buttons
File logging toggles, file name, save path, and buffer settings in one panel
Settings persist in a ScriptableObject — version-control friendly, Inspector editable
Minimal & Non-Intrusive
Zero runtime overhead when file logging is disabled — no allocations, no background threads, no global hooks
Severity filtering is handled by Unity's own Console buttons — no duplication
No third-party dependencies, no reflection, no editor-only scripts leaking into builds
Ideal for teams using categories like AI, Physics, UI, Network, Audio, Player, or any system-specific tag that helps isolate signals from console noise during development.
LAC Debug Logger is a lightweight Unity debugging tool that replaces scattered Debug.Log calls with a structured, tag-based logging system. Filter Unity console output by category, write structured log files for Editor and builds, and manage everything from a focused editor window — without touching your code or recompiling.
Whether you are tracking AI behaviour, physics interactions, UI events, or any other game system, you define the tags, and the logger only passes what you need to the Unity Console right now.
Tag-Based Console Filtering
Define unlimited custom log categories (tags) in the editor window
Toggle any tag on or off instantly — active tags appear in the console, inactive ones are silently dropped
Bulk controls to enable or disable all tags in one click
Untagged log calls always pass through, so third-party and legacy code is never silenced
Structured File Logging
Write log output to .txt files in the Editor, standalone builds, or both
Each entry includes timestamp, severity, scene name, and tag for easy filtering in any text editor
Choose a custom save path via folder browser, or default to Application.persistentDataPath
Automatic 5 MB file rotation — active log is archived before a new one starts
Flush on application quit, flush when buffer reaches a configurable entry limit, or call DebugLogger.Flush() from code at any time
Clean API — Drop In, No Setup
DebugLogger.Log("Pathfinding complete", "AI");
DebugLogger.LogWarning("Overlap detected", "Physics");
DebugLogger.LogError("Missing reference", "UI");
DebugLogger.LogVerbose("Frame data", "AI");
Editor Window (Tools > Debug Logger)
Add, remove, enable, and disable tags without leaving the Editor
All / None bulk tag toggle buttons
File logging toggles, file name, save path, and buffer settings in one panel
Settings persist in a ScriptableObject — version-control friendly, Inspector editable
Minimal & Non-Intrusive
Zero runtime overhead when file logging is disabled — no allocations, no background threads, no global hooks
Severity filtering is handled by Unity's own Console buttons — no duplication
No third-party dependencies, no reflection, no editor-only scripts leaking into builds
Ideal for teams using categories like AI, Physics, UI, Network, Audio, Player, or any system-specific tag that helps isolate signals from console noise during development.