That is a normal part of client development though. There are many server features that mIRC has added support for over the years without which there would be issues. If a server adds an important feature, like IRCv3 message tags, it should be implemented in the client. The reason for my post was to confirm that issue referred to was IRCv3 message tags and that support for this had been added to the next version. As for /parse, this is not something I want to add support for due to the number of issues it would cause.