Some of the things we brainstormed was options for alternate macros like Core or IHC's macros, but more user feedback is needed for us to know what are good options for the output colors and if there is any "Role" type variable that needs to be shown in the /status to accompany those macros. Releasing something like this as a plugin was done out of necessity for @Sic because of the limitations of the ingame socials. It didn't have space for all the code we were trying to put into it, and we wanted reports from each user to come in on a single line, better still. This allows us to do it with a simple /command instead of having to hit a social hotkey with black magic through some form of /bct /bca /bcg or whatever those dannet queries are.
Support for Dannet, I don't use Dannet. I don't know how to use Dannet. There's information, I'm just not in a hurry to learn it with my plate piled high. EQBC is currently the best known method of using this for me. It was mentioned "well all you have to do is -something something something listeners something query etc something-" but I don't know how to do that stuff :-)
I'm mostly expecting to expand on it using eqbc to provide a list of information desired by the user. That information can be expanded on if said information is something that would be globally desired information.
Moar Commands? Sure, I don't mind adding more commands. Just have to find a name to call it that matches what it does that doesn't also conflict with any aliases or existing command. You should outline what you'd like the command to do in as much detail as possible. Think of it like it's a decision tree. If this is valid, then do this thing, otherwise do this other thing, and then split off each of those, etc. Could be several decision trees like we have with /status where it checks a bunch of things and only outputs some information based on the results of the initial query. White board your idea, take pictures, draw us all the circles so that we can finish drawing the owl.