Forums Bug Reports Multiple target output

I am curious if this is intended behavior, or a bug of sorts that causes it to not show as you would expect them to in the sending client...

It would seem that when you send a message/action (/msg or /describe) to multiple targets, you do not get the default output like you would with a single target

Single target:

Results in (as expected):

However using multiple targes:

Results in this being shows where the command was entered:


Same goes for any multiple target messages:


It would seem the 'expected behavior' would be this:

Shown in #Channel1:

Shown in #Channel2 (Or second target, eg: Nick1):


That said, the message is properly sent to the targets, just doesn't show as I would think they should in the client sending the data.

This is expected behavior as mIRC does not (AFAIK) assume that /msg is sent to multiple channels if a comma is specified. Instead, it assumes you sent the msg to "#chan1,#chan2" not "#chan1" and "#chan2".

This is easily fixed with scripting, and I'd assume is not a bug

I would think that since all the IRCds that I have seen allow multiple targets, mIRC should accept this behavior and display accordingly. Should it not?

Yes of course you could write a script to catch the default /msg and /describe commands and display how you see fit, but I'm still of the mind that mIRC should do this by default.

In the original rfc, it is specified that channel name cannot contain a comma, because it's used as a list seperator (exactly the case here). It is not expected behavior at all, mIRC should not be assuming you're sending a message to such a channel because it's simply invalid. It should display the message to each valid target.