nick

By StoneD on Nov 15, 2009

ex: (IRChat) Called you on ( #IRChat ) MSG:(Stoner Welcome Back)

on *:TEXT:*:#:{ 
  if ($chan == $active) { 
    halt
  }
  else {
    if ($me isin $1-) {
      haltdef 
      echo -a ( $+ $nick $+ ) Called you on ( $chan  ) MSG:( $+ $1- $+ )   
    halt  }
  }
}

Comments

Sign in to comment.
Grant-   -  Nov 22, 2009

I know Ghost-Writer has pride for his child pornographical images which he distributed over our nice and innocent server of SwiftIRC, but then he even did something as bad as joining a channel and to ask to DDoS an IP! He's in touch with his inner child, as it's never left them

 Respond  
Cracker200   -  Nov 22, 2009

lol /fail

 Respond  
Ghost-writer   -  Nov 21, 2009

:> pwnz0r i do.

 Respond  
Cracker200   -  Nov 19, 2009

Yup probably

 Respond  
Jethro   -  Nov 19, 2009

I bet ghost-writer has high pride for his inner child.

 Respond  
Cracker200   -  Nov 19, 2009

:< gtfo. jethro_ is just a hater. My coding is pro. And for the snippet, if you wanted to be highlighted on more words you could use $regex, like on
Code:
:TEXT::#: {
if ($regex($strip($1-),$me|Word|Word2|Word3)) { bla }
}

LOLOLOLOL @ My coding is pro.

 Respond  
Testor   -  Nov 17, 2009

StoneD Said..

on :TEXT::#:{
if ($chan == $active) {
halt
}
if your on the channel and some one calls your nick will not echo Thats why (:
My version does that D: /Late

 Respond  
Jethro   -  Nov 16, 2009

Guys, this is not a competition. It doesn't matter who's first or last. What matters is you're to be helpful and offer your suggestions with constructive criticism.

 Respond  
sunslayer   -  Nov 16, 2009

no pic, no proof.

 Respond  
Grant-   -  Nov 16, 2009

Rage sunslayer, I posted like at the same time he did :<

 Respond  
sunslayer   -  Nov 16, 2009

Posted on Nov 16, 2009 4:47 pm> Posted on Nov 16, 2009 4:50 pmi lol'd, maybe next time Grant- :p

 Respond  
Grant-   -  Nov 16, 2009

If you're going to use regex, at least fucking use it right.. And by the way kid, you can't bash someone if you don't know regex yourself. For one, $me won't evaluate. Two, $strip is unneccessary. Using /Si would do the same. And you didn't even open it, so here's what your failure of a regex should look like, and it wouldn't even work still!

on *:TEXT:*:#: {
if ($regex($1-,/$me|Word|Word2|Word3/Si)) { blah }
}
 Respond  
Jethro   -  Nov 16, 2009

I ain't gonna argue with your name-calling, because that's the way you are. Before you call yourself a pro, can you at least have the decency to ensure that your example works before posting? You missed an "on" and the way you constructed your regex will not work. Let me give you two examples in return that work:

on *:TEXT:*:#: {
  if ($regex($1-,/( $+ $me $+ |2nd|3rd|4th)/iS)) { ... }
}

Or

on $*:TEXT:$(/( $+ $me $+ |2nd|3rd|4th)/iS):#: { ... }
 Respond  
Ghost-writer   -  Nov 16, 2009

:< gtfo. jethro_ is just a hater. My coding is pro. And for the snippet, if you wanted to be highlighted on more words you could use $regex, like on

*:TEXT:*:#: {
if ($regex($strip($1-),$me|Word|Word2|Word3)) { bla }
}
 Respond  
Jethro   -  Nov 16, 2009

Actually Ghost-writer's altered version will make it only work when you're not looking at the active window. Furthermore, the dollar sign ($) next to the text event is not needed, since this is not a regex match.

And as sunslayer's stated, and I wish Ghost-writer's mentality can be more like yours, that using $iif is pointless when you are making one comparison. Now, that is a helpful tip right there.

 Respond  
sunslayer   -  Nov 16, 2009

the $iif is pointless when a single /if is all that is needed

 Respond  
Jethro   -  Nov 16, 2009

Ghost-writer, you've failed to offer a helpful explanation. As usual, you resume your boasting attitude toward every snippet you come across. What's wrong with you?

 Respond  
Ghost-writer   -  Nov 16, 2009

1 line

on $*:TEXT:$($+(*,$me,*)):#: {
$iif($chan != $active,echo -a ( $+ $nick $+ ) Called you on ( $chan  ) MSG:( $+ $1- $+ ) ) 
  }

You are all forgetting the strip event!

 Respond  
Jethro   -  Nov 15, 2009

My intention was to strip out the control codes if called by someone using them to trigger the script. Although it may seem the tokenize part is sorta excessive for a small script like this one, with only one $1- in it, it'll be another story if you have more than one $1- used in a script. That means you'll have to use $strip() everywhere to cover them. I'm not too big in using the $strip() identifier, but I always thought that'd affect a script's workability if someone's font is made out of control codes, which needs to be stripped to successfully initiate it. I may be mistaken, but please do correct me so I can steer myself in the right direction.

 Respond  
sunslayer   -  Nov 15, 2009

why even strip $1-?

 Respond  
Grant-   -  Nov 15, 2009

Jethro_, was the tokenize part really necessary? You could of just had $strip($1-) in the ouput lol

 Respond  
Jethro   -  Nov 15, 2009
on *:TEXT:$($+(*,$me,*)):#: {
  tokenize 32 $strip($1-) | $iif($active ischan && $me ison $chan,echo -a ( $+ $nick $+ ) Called you on ( $chan  ) MSG:( $+ $1- $+ ))   
}
 Respond  
StoneD   -  Nov 15, 2009

on :TEXT::#:{
if ($chan == $active) {
halt
}
if your on the channel and some one calls your nick will not echo Thats why (:

 Respond  
Testor   -  Nov 15, 2009

you should strip out control (k/u/r/b) codes from your description.
And check if $Me isin $Strip($1-), rather than just $Me isin $1-
Also, instead of

on *:TEXT:*:#:{ 
  if ($chan == $active) { 
    halt
  }
  else { 
..

to

on *:TEXT:*:#:{ 
  if ($chan != $active) { 
...
 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.