Unknown Channel Mode Parameters mess up other known mode parameters

[GoogleCodeExporter]

I was going to document this issue on a "Known unfixable issues" wiki page, but 
I'll ask here for any advice

In cases where a channel mode is set and one of the modes is unknown its 
possible for PircBotX to report the wrong information.

Consider this mode change on the Freenode IRC Network

{{{
MODE #quackbot +fk #quackbot2 test
}}}

To freenode, this means setup channel forwarding to #quackbot2 and to set the 
channel key to test. However PircBotX doesn't support the channel forwarding 
mode. The result of this is a SetChannelKeyEvent with a key of "#quackbot2", 
which is wrong.

Can anyone think of a way to fix this?

Original issue reported on code.google.com by Lord.Qua...@gmail.com on 18 Jun 2011 at 4:11

• Blocking: #28

[GoogleCodeExporter]

Original comment by Lord.Qua...@gmail.com on 19 Jun 2011 at 10:26

[GoogleCodeExporter]

The server sends information regarding whether or not what channel mode takes 
parameters or not, as part of a reply with the numeric 5 (RPL_ISUPPORT).

http://code.google.com/p/pircbotx/issues/detail?id=77 I reported an issue 
regarding the parsing of this information here.

Original comment by RayKay...@gmail.com on 6 Jul 2012 at 8:45

[GoogleCodeExporter]

Is this only specific to freenode/ircd-seven?

Original comment by entityreborn on 2 Jan 2013 at 10:31

[GoogleCodeExporter]

This affects any server that uses unknown modes

Original comment by Lord.Qua...@gmail.com on 2 Jan 2013 at 10:32