on 1:connect: { .ns identify [nick] [password]

easier way...if you have \"Raws\" in your script, just put \" on 1:connect: { .ns identify \" or else just put wherever you want

else {

Yep, that\'s true, sailoreagle.

not very effective , what about when you use two registred nicks with different passwords and you change them costantly while connected ?

Or you could use /msg nickserv@services.dal.net, /msg chanserv@services.dal.net, etc... :P But I wasn\'t on about /ns vs /nickserv vs /msg nickserv, I was on about the different ways services are configured to ask you for your password and the way even a simple identify command can vary from network to network.

For example, networks like DALnet don\'t allow /msg NickServ, /msg ChanServ, and /msg MemoServ, instead you use /ns, /nickserv, /cs, /chanserv, /ms, and /memoserv.

The one problem I can see with this snippet is that not all networks\' services ask you to identify to your nick that way... also, that way you\'ll perform the identify command every time nickserv asks you to identify, no matter what the nick is. So you could be trying to identify to a nickname that doesn\'t belong to you. I\'d use an if statement to check whether the nick you\'re using is one of the ones you have registered, and if so, perform the identify command, if not, do nothing.