mIRC auto-identify script

[EvilSeph]

Here's an auto-identify script that you can use with mIRC to connect to and auto-identify on the Malloc.us IRC network. Of course, since it is commented, you can use it to learn how to mIRC script and/or modify it to work on other networks too.

To use the script, do the following:

1. Open mIRC if it isn't already.
2. Press Alt + R or navigate to Tools -> Scripts and choose the Remotes tab.
3. If you know what you are doing, you can just add your script into the file that is currently open in the mIRC Scripts Editor or you can open a new file by going to File -> New.
4. Paste the script below while making sure to read the comments so that you know what to change (if anything).
5. Save the script and reconnect to Malloc.us or restart mIRC and it should automate the entire connect and identify process whenever you start mIRC.

[highlight=mirc];Lines prefixed with a semi-colon, like this one,
; are comments.
;This is an auto-connect on startup script written by EvilSeph to make your
; client automagically connect on startup to Malloc.us.

;This line tells mIRC what to do when it starts up
; using something called an on start event.
;
;The syntax is:
; on level:event:{
; code
; }
;
;Here we're telling mIRC to process the code in the curly braces
; when it starts up.
on *:start:{
;This next line tells mIRC to connect to irc.malloc.us on startup:
server irc.malloc.us
}

;This is an auto-identify script written by EvilSeph for use on Malloc.us
;
;When you connect to Malloc.us and your nick is registered
; a Network Service called NickServ notices
; you (i.e. sends you a private message)
; telling you to identify

;This line tells mIRC to listen for this notice
; using something called an on notice event.
;
;The syntax is:
; on level:eventarams:target:{
; code
; }
;
;Here we're telling mIRC to listen for a notice that
; contains the text "This nickname is registered and protected."
; followed by and preceded by anything since we use wildcards.
;

on *:notice:*This nickname is registered and protected.*:?:{
;This next line provides some extra security
; since the event applies to anyone and anything
; without security, people could pretend to be NickServ
; send you a notice that matches the params
; and you'd end up sending them your password.
;
;Here we check if the person who sent you the notice is
; named "NickServ". For extra security we also check
; if the server you are connected to is really a
; Malloc.us server.
if (($nick == NickServ) && (*.malloc.us iswm $server)) {
;If this security check is passed, we let mIRC send "NickServ"
; our password to identify. Please replace PASSWORD with
; the password you used to register your nickname.
.ns identify PASSWORD
}
}[/highlight]

 

[Colm]

Brilliant, I just have one question, what's the mIRC script to open a new server window and connect that to a different server?

 

[FrozenIpaq]

Couldn't you just use the default server commands on a connection? the only problem with this is when you connect to other clients but I'm able to ID myself, Op myself, and join channels all by telling the client to say blahblahblah on connection

 

[EvilSeph]

Brilliant, I just have one question, what's the mIRC script to open a new server window and connect that to a different server?

Instead of "server" on line 18, you'd use "server -m". You could even adapt the script to connect to more servers on startup and identify to more IRC networks (if they use the same services as Malloc.us) too, like so:

[highlight=mirc;;2,3]on *:start:{
server irc.malloc.us
server -m irc.secondnetwork.com
}

on *:notice:*This nickname is registered and protected.*:?:{
if (($nick == NickServ) && (*.malloc.us iswm $server)) {
.ns identify PASSWORD
}
elseif (($nick == NickServ) && (*.secondserver.com iswm $server)) {
.ns identify PASSWORD2
}
}[/highlight]

Couldn't you just use the default server commands on a connection? the only problem with this is when you connect to other clients but I'm able to ID myself, Op myself, and join channels all by telling the client to say blahblahblah on connection

mIRC does include perform support by default, but I prefer using scripts to handle my perform as it offers me more control (and security).

 

[Serideth]

Using this myself, should work fine, will soon see when I get the inevitable d/c.

 

[Moose]

Could you post the code naked? With no tags, etc. Because it's a pain to have to remove the numbered bullet points after copying the script.

 

[Colm]

Instead of "server" on line 18, you'd use "server -m".

Thanks

You could even adapt the script to connect to more servers on startup and identify to more IRC networks

Yeah, I was planning that. Thanks

 

[Slasher]

Could you post the code naked? With no tags, etc. Because it's a pain to have to remove the numbered bullet points after copying the script.

When you copy it, it doesn't copy the line numbers with it (at least it hasn't for me). I know it looks like it does because it's highlighted, but it doesn't.

 

[Moose]

When you copy it, it doesn't copy the line numbers with it (at least it hasn't for me). I know it looks like it does because it's highlighted, but it doesn't.

It does for me.

 

[Serideth]

What browser are you using?

Doesn't copy them for me in Firefox.

 

[Moose]

Firefox...

Spoiler: =(

1.
;Lines prefixed with a semi-colon, like this one,
2.
; are comments.
3.
;This is an auto-connect on startup script written by EvilSeph to make your
4.
; client automagically connect on startup to Malloc.us.
5.

6.
;This line tells mIRC what to do when it starts up
7.
; using something called an on start event.
8.
;
9.
;The syntax is:
10.
; on level:event:{
11.
; code
12.
; }
13.
;
14.
;Here we're telling mIRC to process the code in the curly braces
15.
; when it starts up.
16.
on *:start:{
17.
;This next line tells mIRC to connect to irc.malloc.us on startup:
18.
server irc.malloc.us
19.
}
20.

21.
;This is an auto-identify script written by EvilSeph for use on Malloc.us
22.
;
23.
;When you connect to Malloc.us and your nick is registered
24.
; a Network Service called NickServ notices
25.
; you (i.e. sends you a private message)
26.
; telling you to identify
27.

28.
;This line tells mIRC to listen for this notice
29.
; using something called an on notice event.
30.
;
31.
;The syntax is:
32.
; on level:eventarams:target:{
33.
; code
34.
; }
35.
;
36.
;Here we're telling mIRC to listen for a notice that
37.
; contains the text "This nickname is registered and protected."
38.
; followed by and preceded by anything since we use wildcards.
39.
;
40.

41.
on *:notice:*This nickname is registered and protected.*:?:{
42.
;This next line provides some extra security
43.
; since the event applies to anyone and anything
44.
; without security, people could pretend to be NickServ
45.
; send you a notice that matches the params
46.
; and you'd end up sending them your password.
47.
;
48.
;Here we check if the person who sent you the notice is
49.
; named "NickServ". For extra security we also check
50.
; if the server you are connected to is really a
51.
; Malloc.us server.
52.
if (($nick == NickServ) && (*.malloc.us iswm $server)) {
53.
;If this security check is passed, we let mIRC send "NickServ"
54.
; our password to identify. Please replace PASSWORD with
55.
; the password you used to register your nickname.
56.
.ns identify PASSWORD
57.
}
58.
}

 

[EvilSeph]

Could you post the code naked? With no tags, etc. Because it's a pain to have to remove the numbered bullet points after copying the script.

Yes, unfortunately that does happen in some browsers but we're working on a fix.

;Lines prefixed with a semi-colon, like this one,
; are comments.
;This is an auto-connect on startup script written by EvilSeph to make your
; client automagically connect on startup to Malloc.us.

;This line tells mIRC what to do when it starts up
; using something called an on start event.
;
;The syntax is:
; on level:event:{
;    code
; }
;
;Here we're telling mIRC to process the code in the curly braces
; when it starts up.
on *:start:{
;This next line tells mIRC to connect to irc.malloc.us on startup:
  server irc.malloc.us
}

;This is an auto-identify script written by EvilSeph for use on Malloc.us
;
;When you connect to Malloc.us and your nick is registered
; a Network Service called NickServ notices
; you (i.e. sends you a private message)
; telling you to identify

;This line tells mIRC to listen for this notice
; using something called an on notice event.
;
;The syntax is:
; on level:event:params:target:{
;    code
; }
;
;Here we're telling mIRC to listen for a notice that
; contains the text "This nickname is registered and protected."
; followed by and preceded by anything since we use wildcards.
;

on *:notice:*This nickname is registered and protected.*:?:{
;This next line provides some extra security
; since the event applies to anyone and anything
; without security, people could pretend to be NickServ
; send you a notice that matches the params
; and you'd end up sending them your password.
;
;Here we check if the person who sent you the notice is
; named "NickServ". For extra security we also check
; if the server you are connected to is really a
; Malloc.us server.
  if (($nick == NickServ) && (*.malloc.us iswm $server)) {
;If this security check is passed, we let mIRC send "NickServ"
; our password to identify. Please replace PASSWORD with
; the password you used to register your nickname.
    .ns identify PASSWORD
  }
}

 

[Andy]

Thanks for this EvilSeph, works like a treat

 

[Clint]

Uh oh!

;This next line provides some extra security
; since the event applies to anyone and anything
; without security, people could pretend to be NickServ
; send you a notice that matches the params
; and you'd end up sending them your password.

This is definitely not true--look at how you're identifying. You're using the server alias ns which is different than sending your identify command to someone named NickServ.


Clint