Really simple poke script!

By mircmattuser on Feb 19, 2010

Simple script where you type !poke and it'll go... [17:32:56] <&Matt> !poke User
[17:32:56] * ~Bot_Tom pokes User

ON *:TEXT:!poke*:#: {
  /describe $chan pokes $2-
}
ON *:TEXT:!aboutpoke*:#: {
  /notice $nick This script was made by Matt.
  /notice $nick IRC vHost, Matt@Hiding.My.Identity.From.You.Stalkers
  /notice $nick Do not reproduce without my explicit permission.
}

Comments

Sign in to comment.
Gummo   -  Feb 24, 2010

My first trigger was active only in a staff room and it was flooded, so ner. :D

 Respond  
Jethro   -  Feb 23, 2010

well yea, but whos ganna spam a poke command?Maybe not you, but some rascals will...> i guess better safe then srry ?Yes, never say never and you can't be too careful these days.

 Respond  
napa182   -  Feb 23, 2010

lmao

 Respond  
GuitarMasterx7   -  Feb 23, 2010

well yea, but whos ganna spam a poke command

_>

i guess better safe then srry ?

 Respond  
Jethro   -  Feb 22, 2010

I like simplicity, but if you're referring to a kind of simplicity with multiple text events per trigger, without trigger flood protection, and some needed factors considered to benefit a script, that won't be an efficient simplicity.

 Respond  
GuitarMasterx7   -  Feb 22, 2010

well touche Jethro
made sumfin so very simple
into sumfin longer =D
rofl
<3 Jethro

 Respond  
Jethro   -  Feb 20, 2010

I agree, Gummo. Slacker could've done it like so:

on $*:text:/^!(about)?(poke)\b/iS:#:{
  if ($2 ison #) && ($regml(1) == poke) { describe # pokes $2 }
  if ($regml(1) == about) {
    .notice $nick This script was made by Matt.
    .notice $nick IRC vHost, Matt@Hiding.My.Identity.From.You.Stalkers
    .notice $nick Do not reproduce without my explicit permission.
  }
}
 Respond  
Gummo   -  Feb 20, 2010

Seems to me that slacker's regex wouldn't work for a number of reasons..
One of them is the fact that "!aboutpoke" takes both regml(1) and regml(2).
The other is the fact that it can trigger for ! by itself and something after it, or any trigger at all other than !

 Respond  
Jethro   -  Feb 20, 2010

Well, slacker, if you must do it with regex, you really don't have to construct it with the match for nick, poke and aboutpoke. All you need to do is this:

on $*:text:/^!(\w+)\s(\S+)/iS:#:{

since you already use $regml(1) and $regml(2) to indicate what you're going to match.

 Respond  
slacker   -  Feb 19, 2010

you can also do it like this as well if all you are doing is a poke.

on $*:text:/^!((about)?poke)?\s?(\S+)/iS:#:{ 
  if (!$hget(poke,$nick)) {
    .hinc -mz poke $nick 3
    if ($regml(1) == poke && $regml(2) ison #) { describe # pokes $regml(2) }
    elseif ($regml(1) == aboutpoke) {
      .notice $nick This script was made by Matt.
      .notice $nick IRC vHost, Matt@Hiding.My.Identity.From.You.Stalkers
      .notice $nick Do not reproduce without my explicit permission. 
    }
  }
}
 Respond  
Jethro   -  Feb 19, 2010
on *:TEXT:*:#: {
  if (!$hget(p,$nick)) {
    hinc -mz p $nick 5
    var %x = $strip($1-)
    goto %x
    :!poke
    if ($2 ison #) .describe # pokes $2-
    halt
    :!aboutpoke
    .notice $nick This script was made by Matt.
    .notice $nick IRC vHost, Matt@Hiding.My.Identity.From.You.Stalkers
    .notice $nick Do not reproduce without my explicit permission.
    halt
  }
  :%x | return
}
 Respond  
napa182   -  Feb 19, 2010

/timer 0 0 msg # !poke user

maybe add some kind of flood pro to this. Also maybe check to see if $2 is said...

 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.