DeluXe Whois

By N3M3S1S on Aug 06, 2010

Using mIRC's raw numeric events, this script modifies the information that is shown when you do /whois or /whowas. Shows more info on the user.

;DeluXe Whois II - By Neo Nemesis
;whois script

raw 311:*: { echo -a  $+ $color(whois) $+ - | echo -a 12*!*14 DeluXe Whois II 12*!*4 ( $+ $2 $+ )12 *!* | echo -a 4Hostmask: $+ $color(whois) *!*@ $+ $4 $+  | echo -a 4E-mail: $+ $color(whois) $3 $+  | echo -a 4Fullname: $+ $color(whois) $6- $+  | halt }
raw 307:*: { echo -a 4Registered: $+ $color(whois) $4- $+  | halt }
raw 319:*: { echo -a 4Channels: $+ $color(whois) $3- $+  | halt }
raw 312:*: { if (%whowas != $true) { echo -a 4Server: $+ $color(whois) $3 $+  | echo -a 4IRCd: $+ $color(whois) $4- $+  | halt } | elseif (%whowas == $true) { echo -a 4Server: $+ $color(whois) $3 | echo -a 4Date: $+ $color(whois) $4- | unset %whowas | halt } }
raw 317:*: { echo -a 4Idle time: $+ $color(whois) $duration($3) $+  | echo -a 4Sign on: $+ $color(whois) $asctime($4) $+  | halt }
raw 313:*: { echo -a 4IRCop: $+ $color(whois) $5- $+  | halt }
raw 310:*: { echo -a 4Helpful: $+ $color(info) $3- $+  | halt }
raw 309:*: { echo -a 4Language: $+ $color(info) $3- $+  | halt }
raw 325:*: { echo -a 4Language Filter: $+ $color(info) $3- $+  | halt }
raw 301:*: { echo -a 4Away: $+ $color(info) $3- $+  | halt }
raw 318:*: { echo -a 12*!*14 End of /whois 12*!* | echo -a  $+ $color(whois) $+ - | halt }
raw 314:*: { %whowas = $true | echo -a  $+ $color(whois) $+ - | echo -a 12*!*14 DeluXe Whowas 12*!*4 ( $+ $2 $+ )12 *!* | echo -a 4Hostkmask: $+ $color(whois) *!*@* $+ $4 $+  | echo -a 4E-mail: $+ $color(whois) $3 $+  | echo -a 4Fullname: $+ $color(whois) $6-  | halt }
raw 406:*: { echo -a  $+ $color(whois) $+ - | echo -a 12*!*14 $2 there was no such nickname. 12*!* | halt }
raw 369:*: { echo -a 12*!*14 End of /whowas 12*!* | echo -a  $+ $color(whois) $+ - | halt }
raw 344:*: { echo -a 4SSL: $+ $color(whois) $4- $+  | halt }
raw 334:*: { if (interests isin $1-) { echo -a 4Interests: $+ $color(whois) $4- $+  } | elseif (location isin $1-) { echo -a 4Location: $+ $color(whois) $4- $+  } | elseif (occupation isin $1-) { echo -a 4Occupation: $+ $color(whois) $4- $+  } | halt }
raw 379:*: { echo -a 4User Modes: $+ $color(whois) $6- | halt }
raw 671:*: { echo -a 4Secure Connection: $+ $color(whois) $3- | halt }
raw 320:*: { echo -a 4Info: $+ $color(whois) $3- | halt }
raw 338:*: { echo -a 4IP: $+ $color(whois) $3- | halt }
raw 340:*: { echo -a 4IP: $+ $color(whois) $2- | halt }

Comments

Sign in to comment.
N3M3S1S   -  Sep 02, 2010

Thanks :D

 Respond  
HartselleBoy01   -  Aug 30, 2010

Works Good.

 Respond  
Swat   -  Aug 27, 2010

Nice script!

 Respond  
Serpentsounds   -  Aug 12, 2010

Yeah, the command character switching is a good point...although I'm sure the vast majority of people leave it as /, I guess that means omitting the / in scripts does make it SLIGHTLY more compatible.

And yeah, the . prefix is only to make fewer things appear locally. It's good for some private /notices or /msgs that are script triggered (especially auto-identify. Something about seeing my password appear on the screen bugs me. :P). Also useful for /timer and file handling commands (/fopen and the rest) because nobody really wants to see hundreds of /fwrite notices outside of debugging. ;]

 Respond  
N3M3S1S   -  Aug 12, 2010

The . is for quietly executing a command. i.e.

on *:JOIN:#: {
  if ($nick != $me) { .notice $nick Hello! Welcome to $chan }
}

That right there would quietly send a notice to $nick, where as /notice you would see the message on your screen being sent to $nick and with .notice you wouldn't see it on your screen at all. Now it still shows up on $nick's screen, obviously.

The . can be used on most commands to quiet their echoing default text. It can be used with /timer, /nick, etc. Any command that echoes default text to your window can be silenced with the . and if you want to use it outside of a script use //.timer etc.

 Respond  
Gummo   -  Aug 12, 2010

Yes, except for the case of someone using /echo when the user has changed the command character to ~.
My point was mostly about the . rather than the /
I'm not sure people quite understand what the . is for.

 Respond  
N3M3S1S   -  Aug 10, 2010

o.O Hmm picky picky lol well regardless of how its made, it still works!

 Respond  
Serpentsounds   -  Aug 10, 2010

By "minor syntactical deviation" I was implying that only a small number of characters varied. I'm not saying any way is right or wrong either, just that differences like "/echo" and "echo" both function the same in the script. Though I would personally opt for the shorter option, it should be up to whoever is writing it.

 Respond  
Gummo   -  Aug 10, 2010

Nobody actually mentioned wrong or right, just unnecessary. A syntactical deviation which is exactly the same except for a character which serves no purpose isn't the same as a deviation which uses a different method.

 Respond  
Serpentsounds   -  Aug 09, 2010

A person doing something one way doesn't make it "right," especially if others use minor syntactical deviations to achieve the result (that means that their method is also not "right").

If it works and there aren't blatant inefficiencies, no arguments here. ;)

 Respond  
Gummo   -  Aug 09, 2010

Another strange habit is putting . in front of things which don't need to be silenced, such as halt.

 Respond  
N3M3S1S   -  Aug 06, 2010

LOL like Jethro_ said, its a force of habit.

 Respond  
Aucun50   -  Aug 06, 2010

I use else if because Java doesn't like elseif and mirc doesn't care, not a bad habit.

 Respond  
Jethro   -  Aug 06, 2010

Well, that does not really matter if they use the command char or not. It's force of habit for some. It's the same philosophy that you use > else ifwhile others use

elseif
 Respond  
Aucun50   -  Aug 06, 2010

You don't need the / before echo.

 Respond  
Are you sure you want to unfollow this person?
Are you sure you want to delete this?
Click "Unsubscribe" to stop receiving notices pertaining to this post.
Click "Subscribe" to resume notices pertaining to this post.