Thanks for the debug details. This seems to shows that even though the client has sent:
-> fiery.ca.us.SwiftIRC.net NICKSERV identify PASSWORD
the server is still sending:
[14:39:20] <- :NickServ!services@services.host NOTICE Ouims :This nickname is registered and protected. If it is your
[14:39:20] <- :NickServ!services@services.host NOTICE Ouims :nick, type /msg NickServ IDENTIFY password . Otherwise,
[14:39:20] <- :NickServ!services@services.host NOTICE Ouims :please choose a different nick.
[14:39:20] <- :NickServ!services@services.host NOTICE Ouims :If you do not change within 20 seconds, I will change your nick.
to tell the client that it needs to send the nickserv identify message.
As discussed before, this is the notice that mIRC looks for to know when to continue with the perform.
It looks like the server is not processing nickserv identify in a way that synchronizes with its own nickserv notices.
While a client could wait for the "mode +r" instead, again as discussed before, the +r mode means different things on different networks, so this is not reliable and would need to be set to a different value for different networks. In addition, some networks do not send "mode +r", they just send another notice.
