By MoeEpsilon on Nov 30, 2008Ok, I'm not looking for a high rating or for comments about how it could be more automated or anything, I just wanted to post a simple nick identifier that anyone on mIRC could use, which is the same one that I used to use before I expanded it to auto-join and all that. It takes a couple minutes to set up, but after that it's very simple. This if for servers with anope services
First, This script does NOT go in your remotes section of script editor, it goes into your aliases tab. This script activates by pressing an F-key (i.e. F1, F2, F3, etc).
The below snippet is custom for a few of the servers I go on. To make this script work for you, you replace the text "PeerCommons", "FanNet" and "StrikeX-Network" in the snippet below with the names of the servers you use. Then replace the text "" with your nicks password you use on that server. After you finish adding the server names and your passwords, connect to the server and hit the F1 button and it will identify you.
Oh, and another thing, if you don't know the name of the server your using, in any channel on that server type //say $network and you will know its name.
/F1 {
if ($network == PeerCommons) { /ns identify <password> }
if ($network == FanNet) { /ns identify <password> }
if ($network == StrikeX-Network) { /ns identify <password> }
}
Well the reason I didn't want it in my remotes is because my remotes has too many scripts in it, my aliases is practically empty except for two custom scripts. If someone wants to change it to remotes, they know how to do it.
Also, if you read the beginning, I said change the servers to the ones you use, and remove the ones I added, I was just using mine as an example -.- I also said I wasn't looking for advice on how to make it more automated with variables, hence the name "Simple Nick Identifier". The only useful bit I actually found in your comment was changing 'msg Nickserv' to 'ns' and I mean come on, how many people visiting this site care about whether that is typed or not or don't know to that themselves?
Or you can make it go into your Remotes tab, by changing
/F1
to
alias F1
What would be better is to perhaps change it into an on CONNECT script?
Example:
on *:CONNECT:{
if ($network == PeerCommons) { msg NickServ identify <password> }
if ($network == FanNet) { msg NickServ identify <password> }
if ($network == StrikeX-Network) { msg NickServ identify <password> }
}
You can also shorten the script by changing
msg Nickserv
to
ns
I also would suggest is to add an on LOAD script to set a default nick and password for each specified server by using variables, and an input-dialog at start.
Not everyone uses the same server as you, too.