Yes i know that it's used otherwise aswell however
- its not enabled by default so up to the users choice
- all of it is still displayed in /debug instead - just centralized and not in the chatwindow.
- to add to it you can still output it like regular without any surpression applied for important messages with LibDebug.d() which is basically a unmodified copy of the original function - if you plan to add support for LibDebug that is.
I dont think I can do anymore in terms of both user and developer friendliness. Or do you have an idea?
Btw. You can add own Message-Buffers as well. Sight, I'm just back home but I'm done for today and am to lazy to document it properly right now. Use /zgoo LibDebug to display all Public Methods which should give a basic idea what you can do - LibDebug.Buffer.DEBUG and LibDebug.Buffer.ERROR holds all debug/error messages by default.
Edit:
Hm ok, d() seems to be really widley used for Custom-Messages in many Addons as well.
I'll see if I can find an better less intrusive solution for that case.