• Improved stacktrace readability powered by Demystifier
• Syntax-highlighted stacktraces
• Background colors by log type (e.g. warning, error, compiler error)
• Log prefixes and color-coding (only visually in editor)
• Filter logs: Hide or Solo logs by package, file, line, message...
• Collapse individual logs
• Ping script files from log
• Fully functional console hyperlinks
• Editor-only logs without impact on builds
• Fixes to source code links

Needle Console is available on the Asset Store for commercial use.
Other versions are only allowed to be used non-commercially and only if you're entitled to use Unity Personal (the same restrictions apply).

After installation, by default all logs and exceptions will be demystified in the Console.
Syntax highlighting will also be applied, and can be configured to your liking.
Settings can be configured under Edit > Preferences > Needle > Console.

Logs going into Editor logfiles will also be demystified.
Logs in builds will not be demystified (by design).

.NET stack traces output the compiler transformed methods; rather than the source code methods, which make them slow to mentally parse and match back to the source code.
Demystify outputs the modern C# 7.0 features in stack traces in an understandable fashion that looks like the source code that generated them.

We provide default syntax highlighting for Light and Dark Theme. You can also change colors to your liking.
Syntax highlighting comes with a slight performance impact when selecting a log (not when logging it).

• Adjust highlighting colors to your liking.
• Disable specific highlight types by setting the Alpha value of the respective setting to 0.
• Dark and Light Theme support

Log filters allow to hide specific logs in your project or only show the logs that matter for you right now. No need to change the way you write Debug.Log messages, it is all available at your fingertips via the console context menu.

• Hide logs by message, file, line, package or even time
• Solo logs: show only log entries that matter to you right now

Multiple logs from the same source can be collapsed into a single log.
Log history is preserved and can be seen in the stacktrace view when the log is selected.
Prevent spamming your console - keep context visible

Right click a console log to ping the source script file
Works with scripts in assets, embedded, local or registry packages

Console hyperlinks make logs with rich text usable and extendable.
By default we provide handling for urls and files.
Example to log a clickable link to Unity.com Debug.Log(<a href="www.unity.com">Open Unity Website</a>
Example to open a file somewhere on disc: Debug.Log(<a href="../project/relative/path.txt">Open some file</a>

To receive callbacks to hyperlinks you can use the HyperlinkCallback attribute.
The method must be static. Either with return type void when you don't care if any other callback is executed as well or bool to control if other callbacks are called.

The following example receives a callback when a link with <a href href="OpenNeedleConsoleSettings"> in a log message is clicked and opens the Needle console preference window.

[HyperlinkCallback(Href = "OpenNeedleConsoleSettings")]
private static void OpenNeedleConsoleUserPreferences()
{
	SettingsService.OpenUserPreferences("Preferences/Needle/Console");
}

• Log background colors can be enabled or disabled to show the severity of a log.
• Compiler errors receive special treatment and are rendered magenta so that shader programmers will feel right at home (it's great, really!)

Logs can automatically be prefixed with file- and method-name providing more context at your log output at a glance. Additionally we add a colored bar in front of the log message that shows which logs belong together / come from the same file.

Use DebugEditor methods to log messages only in Unity Editor.
No garbage or cpu cycles will be wasted in your standalone application.
It is also possible to implement a class named DebugEditor somewhere in your code to add custom functionality.
NOTE: Double clicking log entries that contain DebugEditor.Log in the console will still open the right file for you.

Sometimes, links to code in embedded/local packages don't work, so while we were at it we fixed that as well. (Case 1304954 for Unity people stepping by) Issue Tracker

• syntax highlighting has a performance impact, so if you're on a very slow machine you might want to turn it off (demystifying is highly optimized and shouldn't have a noticeable performance impact)

🌵 needle — tools for unity • @NeedleTools • @marcel_wiessler • @hybridherbst

Demystifier by Ben Adams