Buzzen V2 Passport Flood Protection

Ok guys Buzzens V2 will be official in 2/3 days no more msn chat clone ocx. You may or may have not noticed buzzen v2 irc flash chats can easily be guest flooded passport flooded!!!!! Chat room ADMINS are starting to get things in order setting up scripts for buzzenv2... We need passport flood protection scripts !!!!!!!! most of the ones we used in the past is loaded with old msn server code !!! they dont work i've spent 3 hours looking for a flood protection code that works the closest i have found is this !!!!!! only problem is it disconnects after kicking a few flooders out...

#passportfloodkick on 
on @!*:join:#:{ 
  set -u2 $+(%,#) $eval($+(%,#),2) $nick 
  if ($numtok($eval($+(%,#),3),32) >= 5) { 
    kick # $replace($eval($+(%,#),2),$chr(32),$chr(44)) :4,1)»• 14Proteccion 0Revolution $+  4•«( 
    unset $+(%,#) 
    set %timerlock.chan $chan 
    .timerlock.chan 0 1 mode $chan +i-u 
    .timerlock.chan off 
    access # add DENY >*!*@*$* 
    access # add deny $ial 0 :4,1)»• 14Proteccion 0Revolution $+  4•«( 14Anti 0Flo0d 
    set %timer2knock.chan $chan 
    .timerknock4 1 60 mode $!chr(37) $!+ $right(%timer2knock.chan,-1) +u-i 
    .timerknock6 1 60 msg # )»•Modos-Ro0m18-i+u•«( 
    .timerknock4 off 
    .timerknock6 off 
  } 
} 
#passportfloodkick end

I FOUND THIS GUEST FLOOD KICKER WORKS !!!!!

#guestflood on 
on *:JOIN:* { 
  if (> isin $nick) { 
    if (%GuestFlood == $null) { 
      set -u5 %GuestFlood 1 
    } 
    else { inc %GuestFlood } 
    if (%GuestFlood >= 3) { 
      access $active add DENY >*!*@*$* 2 
      msg $active Possible Guest_ flood detected, Guest_ have been banned (1 minute ban) 
      kickguest 
      unset %GuestFlood 
    } 
  } 
} 
#guestflood end 

alias kickguest { 
  set %kg 1 
  :next 
  set %mnick $nick($active,%kg) 
  if (%mnick == $null) { halt } 
  if (%mnick == $me) { inc %kg | goto next } 
  if (> !isin %mnick) { inc %kg | goto next } 
  if (> isin %mnick) { kick # %mnick Mass Guest Flooder kicker } 
  inc %kg 
  goto next 
}

plz help guys 2 days is gonna be here and i have a feeling our room is gonna get flooded left and right and the Help Desk is gonna be bizzy bizzy bizzy :?

The beta helpdesk doesn't work anyways..it's only on invite ( so far).

I FOUND THIS GUEST FLOOD KICKER WORKS !!!!!

 

#guestflood on 
on *:JOIN:* { 
  if (> isin $nick) { 
    if (%GuestFlood == $null) { 
      set -u5 %GuestFlood 1 
    } 
    else { inc %GuestFlood } 
    if (%GuestFlood >= 3) { 
      access $active add DENY >*!*@*$* 2 
      msg $active Possible Guest_ flood detected, Guest_ have been banned (1 minute ban) 
      kickguest 
      unset %GuestFlood 
    } 
  } 
} 
#guestflood end 

alias kickguest { 
  set %kg 1 
  :next 
  set %mnick $nick($active,%kg) 
  if (%mnick == $null) { halt } 
  if (%mnick == $me) { inc %kg | goto next } 
  if (> !isin %mnick) { inc %kg | goto next } 
  if (> isin %mnick) { kick # %mnick Mass Guest Flooder kicker } 
  inc %kg 
  goto next 
}

If this works, then go with it.

first one looks a bit like the one i did for passport floods on msn

looks like it was changed to do guests lol

Yeah, the guest one looks like it was from Infinite, just modified some.

The beta helpdesk doesn't work anyways..it's only on invite ( so far).

Probably to protect from floods.

how sad travis

oh come on YAHOO the guy was just having a joke lol

on a better note i tried the flash chat today.. nice job

on @!*:JOIN:#: {
  var %x = $numtok(%ppc. [ $+ [ $chan ] ],32)
  if (%x == 3) .raw kick $chan $nick :Flood Protection
  else set -eu3 %ppc. [ $+ [ $chan ] ] $addtok($nick,%ppc. [ $+ [ $chan ] ],32)
  if (%x == 2) {
    .raw access $chan add deny *!*@*$* 2 :Flood Protection
    .raw kick $chan $nick :Flood Protection
    .raw kick $chan $gettok(%ppc. [ $+ [ $chan ] ],1,32) :Flood Protection
    .raw kick $chan $gettok(%ppc. [ $+ [ $chan ] ],2,32) :Flood Protection
  }
}

It's been way too long since i've coded in mIRC, so here is something i did just off the top of my head. It should do the job, but if it doesn't, well i'm sure you could just pluck something out of someone else's script. That's how everything works now a days isn't it?

yup i know and yup u found me out i was having a giggle about it lol.

$addtok($nick,%ppc. [ $+ [ $chan ] ],32)

It has been a while since you've stooped to mIRC level.

$addtok you state the variable first and then what you are adding to the variable.

$addtok(%ppc. [ $+ [ $chan ] ],$nick,32)

This is a great flood protection against seperate nicknames. But I don't think it would stop the same nickname from joining repeatedly. If someone wants I can find sometime to work it into this so it wouldn't conflict. Course TGK is way better than I. Im sure he can say Im wrong or write it up quickly.

Why not just code a sockread flood protection. Its much quicker.

$addtok($nick,%ppc. [ $+ [ $chan ] ],32)

 

It has been a while since you've stooped to mIRC level.

 

$addtok you state the variable first and then what you are adding to the variable.

 

$addtok(%ppc. [ $+ [ $chan ] ],$nick,32)

 

This is a great flood protection against seperate nicknames. But I don't think it would stop the same nickname from joining repeatedly. If someone wants I can find sometime to work it into this so it wouldn't conflict. Course TGK is way better than I. Im sure he can say Im wrong or write it up quickly.

with $addtok, it doesn't matter which way you put it. You just need to know that you are joining one piece of information with the other, using the delimiter provided. I chose to join it in descending order, where the most recent nickname is at the front. You DO NOT need to do it "variable, nickname" or "variable, additional information". What if you were doing a list that you wanted to do in reverse, without using a loop? $addtok will do it fine, you just reverse the information, which is what i did. I don't see how it's "stooped to mIRC level" .

If you are referring to a "hop flood", that's very different. If that was requested, i would make it, but it wasn't .

Why not just code a sockread flood protection. Its much quicker.

for starters, sockreads maybe quicker but they are also more susceptible to flood out. My flood protection will work across any network, provided the "access $chan" is allowed. If it isn't, it only requires changing that one line. Having a sockread protection means that you need to hardwire it to the connection, meaning that you need to know exactly where to put it. This can cause issues when you are having to upgrade connections, or transferring to another server. And as for a general purpose tool, this method is a lot better. It may be a tad slower, but it will serve it's purpose none the less, and if done correctly, can be as (if not more) effective than a sockread protection code.