This uses Ibis.Message.parse to create the message which means it supports

everything in a normal message assuming you can pass it into the command input

field.
I also cleaned up the indentation on the query command.

Tried with no parameters and verified nothing was sent. Then sent messages with invalid commands as well as a TAGMSG with the @+typing=active tag to a channel from the status window and verified it was sent and that another client recognized the typing tag.