* Flood protection: # message(s) in queue

Good day everyone ...

-----

Since i returned to MSN after a 6 month leave ... i noticed that my script was acting funny..

when ever there was a flood .. when ever i posted alot of lines..or when ever i tried to do too many things at once (owner/prop/access/ban) .. i would get a message that said something like this

---------------------------------------------------

* Flood protection: 10 message(s) in queue |

---------------------------------------------------

people told me to set the mIRC flood prot "off" but that just seemed to flood me out of the room when i tried doing any of the things that usually triggered the flood prot...

I was also told to use a "Buffer" that would halt sockets if they exceeded a certin amount .. but using a connection that had a buffer..i seemed to post things in a bunch ... and the joins would not be shown since the sockets were halted.

-----

My question is ...

Is there a way i can stop the mIRC flood protection from triggering so easily and not have to use a buffer...so i am able to work faster when trying to post stuff or kick/ban floods.. ?

======

I'm using

Vincula 4.9 EZR 4.1 (Edited)

mIRC 1.1.7 (since the updater requires that)

and my flood setting is as shown

* Trigger: 500, Queue: 5000, User: 50, Ignore: 0

-----------

Hope someone out there can help me out.

Good day everyone ...

 

-----

 

Since i returned to MSN after a 6 month leave ... i noticed that my script was acting funny..

 

when ever there was a flood .. when ever i posted alot of lines..or when ever i tried to do too many things at once (owner/prop/access/ban) .. i would get a message that said something like this

---------------------------------------------------

* Flood protection: 10 message(s) in queue |

---------------------------------------------------

 

people told me to set the mIRC flood prot "off" but that just seemed to flood me out of the room when i tried doing any of the things that usually triggered the flood prot...

 

I was also told to use a "Buffer" that would halt sockets if they exceeded a certin amount .. but using a connection that had a buffer..i seemed to post things in a bunch ... and the joins would not be shown since the sockets were halted.

 

-----

 

My question is ...

 

Is there a way i can stop the mIRC flood protection from triggering so easily and not have to use a buffer...so i am able to work faster when trying to post stuff or kick/ban floods.. ?

 

======

I'm using

 

Vincula 4.9 EZR 4.1 (Edited)

mIRC 1.1.7 (since the updater requires that)

 

and my flood setting is as shown

 

* Trigger: 500, Queue: 5000, User: 50, Ignore: 0

-----------

Hope someone out there can help me out.

ya get a better script

open your script and hit DELETE and download GD5 lolol

@ bonkers

Nothing's wrong with the script .. its working fine ... its mIRC that's doing it .....

-------

@ Casper74uk

I tried G.D ... but i faced a few problems with it. . plus i enjoy using something i put together (other than the connection)

hence the reason why i am slowly getting there with the stand-a-lone DC... I know that not everyone is going to be able to use GD5, whether they just don't like it, or they can't get use to the setup, well i offer what i can, it's up to people to make the choice.

I don't have anything against G.D .. it was very well made, and i am sure ALOT enjoy using it .. but like i said ... i kinda prefer using something i put together to be able to play with as i like ...

G.D sort of limits me since it had almost everything needed in it ... which is good for those that do want everything ready made ...

====

But, i'm still open to any suggestions as to how to stop the IRC flood from triggering... or atleast to not drop ..

I haven't tried a buffer for vincula .. I used Sky's script that has a buffer installed in his connection ..

----

so if anyone's willing to help, i'll be greatfull

yep, i know mate, and i respect that, everyone has the right to use what they want.

Only thing i can really recommend is that you use things like the slow senders, peter did one for messages (mq), ctcps (cq), and i did a general one (ss).

These are the aliases for each:

; by Pete®tje 2004
; msg sending queue mechanism 
; use mq <channel|nick> <message> 
; 
alias mq { 
 inc %mq_pointer 
 /hadd -m mq %mq_pointer $1- 
 %mq = $addtok(%mq,%mq_pointer,32) 
 if (!$timer(mq)) { .timermq -m 1 $iif(%delay_mq,%delay_mq,400) /mdeq } 
} 
alias mdeq { 
 if ($hget(mq,0).item == 0) { unset %mq* } 
 else { 
   var %item = $gettok(%mq,1,32) 
   %mq = $deltok(%mq,1,32) 
   /msg $hget(mq,%item) 
   hdel mq %item 
   if (%mq) { .timermq -m 1 $iif(%delay_mq,%delay_mq,400) /mdeq } 
   else { unset %mq_pointer } 
 } 
} 

; by Pete®tje 2004
; CTCP sending queue mechanism 
; use cq <nick> <message> 
; 
alias cq { 
 inc %cq_pointer 
 /hadd -m cq %cq_pointer $1- 
 %cq = $addtok(%cq,%cq_pointer,32) 
 if (!$timer(cq)) { .timercq -m 1 $iif(%delay_cq,%delay_cq,400) /cdeq } 
} 
alias cdeq { 
 if ($hget(cq,0).item == 0) { unset %cq* } 
 else { 
   var %item = $gettok(%cq,1,32) 
   %cq = $deltok(%cq,1,32) 
   tokenize 32 $hget(cq,%item) 
   .ctcpreply $1 TIME $2- 
   hdel cq %item 
   if (%cq) { .timercq -m 1 $iif(%delay_cq,%delay_cq,400) /cdeq } 
   else { unset %cq_pointer } 
 } 
} 

; by The Gate Keeper - based off the mq alias
;to use, just place ss infront of your commands, e.g.
; original code : msg $chan hi $nick
; modified code : ss msg $chan hi $nick
alias ss {
 inc %pss | hadd -m slowsend %pss $1-
 var %l = 1 | while ($var(%ssend.*,%l)) { var %i = $($ifmatch,2) | if ($len(%i) < 900) { break } | inc %l }
 set -e %ssend. [ $+ [ $(%l,2) ] ] $addtok(%ssend. [ $+ [ $(%l,2) ] ],%pss,32)
 if (!$timer(slowsend)) .timerslowsend -m 1 300 gosend
} 
alias gosend {
 var %c = $gettok($var(%ssend.*,1),2,46) , %item = $gettok(%ssend. [ $+ [ $(%c,2) ] ],1,32) | %ssend. [ $+ [ $(%c,2) ] ] = $deltok(%ssend. [ $+ [ $(%c,2) ] ],1,32)
 $hget(slowsend,%item) | hdel slowsend %item
 if (!%ssend. [ $+ [ $(%c,2) ] ]) unset %ssend. [ $+ [ $(%c,2) ] ]
 if ($var(%ssend.*,1)) .timerslowsend -m 1 300 gosend
 else unset %ssend.* %pss
}

thnx The Gate Keeper .. but it would be hard to post alot of lines (code for example) at once ... that would work if i just posted one line at a time ..

but still .. the main problem i face is the "join/kick/part" .. which is what usually disconnects me

for pasting a lot of lines of code, you could use this

on *:INPUT:#: {
 <echo here for your theme>
 inc -eu1 %input. [ $+ [ $chan ] ]
 $iif(%input. [ $+ [ $chan ] ] >= 3,ss) .msg $chan $1-
 haltdef
}

You need the ss alias from above.

For the join/part/kick, i guess it's the connection, maybe wait a bit till i am happy with DC and i'll release it, and you could try that. But for me personally, i leave mIRC's internal flood protection off.

Well if your using 6.17, the flood protection is broken in that version.

hence, why i keep it off in GD5

Ok ... so shall i try a buffer for vincula ...

and if so .... how on earth am i to do one lol

use mirc 6.16 , as stated the flood protection in 6.17 is broken

Ozzy .. i tried 1.1.6

i even went as low as 1.0.3 (manually updated passport incase anyone wonders how i was able to join) ..

and i still got the flood thingy

Very odd, what are you using for a flood prot??

Haven't tried this yet, but try this, and see if this will work...

; by The Gate Keeper - based off the mq alias
;to use, just place ss infront of your commands, e.g.
; original code : msg $chan hi $nick
; modified code : ss msg $chan hi $nick
alias ss {
inc %pss | hadd -m slowsend %pss $1-
var %l = 1 | while ($var(%ssend.*,%l)) { var %i = $($ifmatch,2) | if ($len(%i) < 900) { break } | inc %l }
set -e %ssend. [ $+ [ $(%l,2) ] ] $addtok(%ssend. [ $+ [ $(%l,2) ] ],%pss,32)
if (!$timer(slowsend)) .timerslowsend -m 1 300 gosend
} 
alias gosend {
var %c = $gettok($var(%ssend.*,1),2,46) , %item = $gettok(%ssend. [ $+ [ $(%c,2) ] ],1,32) | %ssend. [ $+ [ $(%c,2) ] ] = $deltok(%ssend. [ $+ [ $(%c,2) ] ],1,32)
$hget(slowsend,%item) | hdel slowsend %item
if (!%ssend. [ $+ [ $(%c,2) ] ]) unset %ssend. [ $+ [ $(%c,2) ] ]
if ($var(%ssend.*,1)) .timerslowsend -m 1 300 gosend
else unset %ssend.* %pss
}
alias echo { ss echo $1- }
alias msg { ss msg $1- }

What I think this will do is it will add any messages, or echos to hash table, and then will echo, and message as needed on a timer so that it will slow down a little bit, and not flood you out. At least that is what I'm hoping this code will do, lol. Give it a try, and if you don't like it just delete this code, and everything will go back to the way it was before you added the code.

the thing is ... i am not flooding out of the room ..

I just get a message saying i got a number of messages in queue when ever i post something .....

i mean for example ...

Hitman*!*918942F42E836AA7@GateKeeperPassport Has joined the channel.

* Hitman sets mode: +q Hitman

* Topic is 'Welcome to Revolution'

* ×Skillet 007 sets mode: +v Hitman

-

* Flood protection: 1 message(s) in queue

-

* -Xenocide sets mode: +v Hitman

* JUNNY sets mode: +v Hitman

That happens when i join a room with a long name and i get ownered .....

----

Other stuff are like ..

<.Hitman> The Ban On xX-Rob-Zombie-Xx Was Deleted.

<.Hitman> 'lb

• Hitman deletes deny access: *!5CBB95EFE4C4A12B@GateKeeperPassport$*

-

* Flood protection: 1 message(s) in queue

-

<.leo> donkey *

<.Hitman> lol

<.Willow> oh

-

* Flood protection: 2 message(s) in queue

-

the second queue was from the "lol" that i said ... and it queue'd it because the first queue wasn't posted !! ...

--

its stuff like this that bugs me .. and when there's a flood ... all the deny access are not added because they're all in queues ... which really annoys me...

----

I hope my problem is better explained so you know what i'm facing ..

and my flood settings = 500 5000 50 0

i tried other settings but all seem to flood me out of room when a flood happens

mine are

300

30

10

0

i tried that before and was disconnected pritty fast when a flood joined....i guess vincula loves its fives and zeros ..

I leave the mirc's flood protection off too.

However, try this:

//flood 400 9999 9999 300