Yes, it switched me to Searinox with the underscore and ghostkill did not switch it back. mIRC has Searinox set as a secondary nickname, when it is not possible to use the primary nickname it switches to it. GKNP didn't change it back to Searinox. The problem is actually reproduceable whenever I manually restart my network adapter in device manager. My guess is it has to do with mIRC not having any IP to bind to. True, adapter resets are not something that can accidentally happen like network dropouts, but still...
Not all cases seem to be handled properly. This is what happened after I reset my network adapter.
Welcome to the XXXXXX IRC Network Searinox_!~Searinox@XXXXXXXXX
Yes I meant reading the servers.ini for the password. Your little identify on connect addition fixed the problem though. Now the password is being sent before attempting to autojoin and +r channels are opening. I was not using any autojoin script, just mIRC's builtin autojoin.
This is great, now I can keep all my passwords in just the .hsh file. Thanks for the quick fix!
This addon is not the only one of its kind but after many searches it is the only one I've found that truly detects and corrects all possible scenarios of nick change, including internet dropout plus IP change. Awesome work you have there.
However I have a suggestion.
Think you can add a checkbox of sorts called "use password from mIRC settings" so that it uses the server password(s) stored in mIRC's settings? It's kind of redundant to have to input the password in both mIRC and NickProtection.
I would be using the password in NP alone but I can't because your script sometimes sends the password AFTER mIRC autojoins channels, so channels that require registration won't open, making me to still rely on mIRC's builtin password system.
Bottom line is a single password system is better. Either fix the script to register the nick BEFORE autojoin or add that checkbox I mentioned.