Forums Bug Reports /anick bug when nick is occupied on connection

Hi.

This is a really old bug. 5.9 - 6.35 probably.

The /anick command behaves incorrectly when during connection your nick was occupied and mirc used the anick to connect.


How to reproduce

1. Assume your main nickname is 'blah' and your alternative nickname is 'blah2'.

2. To reproduce the bug, your main nick ('blah' in this example) should be occupied on the irc network you connect to.

3. Connect to the irc network. mIRC will tell you that 'blah' is occupied and set the nickname to 'blah2'.

4. After you connect, execute '/anick blah3'. Woila!


What happens

/anick changes your nickname on server.


What should happen

/anick should change your extra nickname in mIRC memory. It should not touch the nickname on server.

Sorry, but I must disagree.
Based on your example, the active connection is using the alternative nick, therefore changing the alternative nick via the /anick command should change the nick on the active connection. Likewise, if the active connection was using the main nick, then using /mnick should change the nick.

If it is so, how can i (in scripting) find out whether mIRC is using alternative or main nick? And what is the difference in behavior between nick and anick/mnick commands?

You can compare $mnick and $anick with $me.

Thank you RusselB and qwerty.

I'd rename the subject of initial post but it won't let me. :(q