antiflood - mIRC Discussion Forums

How could add a antiflood, of 10 seconds per user?

Code:

on $*:text:$(/^[!](ping|commands)$/Si):#mIRC: {
  if $regml(1) = ping { 
    mode $me -T 
    ctcp $nick ping
  }
  if $regml(1) = commands { 
  .play $nick play/commands.txt 10 
  }
}

on 1:ctcpreply:ping*: { 
  .notice $nick PONG!: $iif($calc($ctime - $2) <= 1,$v1 second.,$v1 seconds.) 
  mode $me +T 
}

For my part, I prefer hash tables to store/check this kind of temporary data

Code:

on $*:text:$(/^\!(ping|commands)$/Si):#mIRC: {
  if $hget(noflood,$+($cid,.,$fulladdress)) { return }
  else { hinc -mu10 noflood $+($cid,.,$fulladdress) }
  if $regml(1) = ping { 
    mode $me -T 
    ctcp $nick ping
  }
  elseif $regml(1) = commands { 
    .play $nick play/commands.txt 10 
  }
}

For the regex part, you don't need to specify another if statement to reference another command, just else will do it...since you only have two of them...so it's either true or false.

Quote:

on $*:text:/^!(ping|commands)$/Si:#mIRC: {
if $regml(1) == ping {
;do something
}
else {
;do something else
}

And you don't need to enclose regex with $() because there is no identifier used to be evaluated.

Quote:

And you don't need to enclose regex with $() because there is no identifier used to be evaluated.

It's not needed with this, but it might be needed for things such as:

Code:

/^\S+(v| $)/i

No, it'll still work without $().

Quote:

/^\S+(v| $)/i

You miss a delimiter (forward slash).

I think you're looking at this pattern:

Code:

/^\S+v( |$)/i

This will make sure it triggers on

Quote:

blahv blah

and not

Quote:

blahvblah

no. THe reason I showed it the way I did, was so u could see:

Code:

on $*:TEXT:/^\S+(v| $)/i:#:{ }

when this event triggeres it might see "$)/i" as an identifer,
hence why u would surround the matchtext with $()

Well, you do know the dollar sign in regex has its special meaning too?

Yes, I'm pretty good with the ol' regex.

was just saying that when mIRC parses the event match-text it might have parts seen as an identifer on occations without the $() around it.

Originally Posted By: FroggieDaFrog

no. THe reason I showed it the way I did, was so u could see:

Code:

on $*:TEXT:/^\S+(v| $)/i:#:{ }

when this event triggeres it might see "$)/i" as an identifer,
hence why u would surround the matchtext with $()

that is, if anything, an example of where you would certainly not want to enclose the matchtext in $(). malformed expression aside, surrounding it with $() will have mIRC attempt to evaluate $)/i as an identifier. without it, mIRC will leave the expression alone and handle all parts of it literally which is, presumably, what we want :P

I agree with jaytea.

One thing I don't get is the pattern demonstrated by Froggie. (unless it's a random, trivial example) It'll match anything starting with one or more nonwhite space characters, followed by a capital or lower letter v, or followed by a space. Sorry, but I don't see how this pattern is any of the benefits for the match...

Quote:

malformed expression aside

perhaps that's what you meant with the expression constructed incorrectly?

Code:

/^\S+(v| )$/

<-this, however, will make some sense to me, because it'll make sure it ends with the uppercase of lowercase v, or proceeded by a space. At least it has a purpose.

Thanks!!!