Cat Log: The ultimate logging tool for Unity

Hello everyone,

I'm excited to share with you a tool that has made debugging and logging in Unity easier and more efficient - it's called Cat Log.

Cat Log is a powerful asset that provides detailed information about each log message, including the file name and line number, so you can easily understand what's happening inside your Unity application and fix issues quickly. It also includes the option to write logs to files, which is useful for debugging builds even when you don't have access to the Unity editor.

Customizing your logging experience with Cat Log is a breeze. It offers custom inspector and runtime scripting options that allow you to enable or disable different types of logs, and change the format, color, and tags of log messages without writing any code. You can log various types of messages (e.g. information, error, warning, and assert), and automatically include the caller file name, line number, and time. You can also log messages to files and decide whether to have all logs in one big file or separated into smaller files based on log type. Plus, you can disable certain types of logs or all logs for builds, and customize the color and tags for log messages.

If you want to create a completely custom logger that fits your specific needs and preferences, Cat Log allows you to do so by completely overriding the log methods. This flexibility makes it an incredibly powerful tool for improving your logging experience in Unity.

I'm confident that Cat Log will be a valuable asset for anyone looking to streamline their debugging and logging process in Unity. If you have any questions or suggestions, don't hesitate to get in touch with me through this thread, on Discord, or via email.

Asset Store Link
Online Documentation

Give Cat Log a try and see the difference it can make for you!

Best,
Zappy

 

if the code reports an error, for example “ UnassignedReferenceException: The variable xxx of xxx has not been assigned.”, can you record and write it to a file?

 

It doesn't automatically handle and log exceptions unless you put a try catch block or use a custom exception class. Usually you would put asserts before running any methods, that way you will always catch anything unexpected and you can decide if you want to raise an exception or not.

You can create assert, warning or error logs easily with this asset. For asserts and errors you can choose if you want to throw an exception after the log has been logged (to the console and/or to a file if you've configured file logging).