Valhalla Legends Archive

Quote from: ___/\___ on October 25, 2003, 11:26 AM

Quote from: Freeware on October 25, 2003, 11:15 AM

Quote from: Grok on October 25, 2003, 07:31 AM
Is the next ops bot evolution something in cooperative banning?  Since an Ops channel can have two ops, if they were able to negotiate which users they were banning it would double the bannable number and banning speed.

Dualops (or for a Warcraft III 4x Ops) is very effective, I have just incorporated it into my bot. Banning flood bots like the titan could also be banned this way (this is the way my bot does it, and it DOES work against titans very well)

 .titanphrase <string> - Sets a string to recognize the bot as a titanbot. For an example if the titan says:

<TitanBot>: Your Clan Sux!
<TitanBot>: HAHAHAHAHA
<TitanBot>: Your Clan Sux!

 the string could be set to: Sux!

well that would work but what if they change the way they flooded to :
rejoin (5 times)
say Your Clan Sux! (Twice)
disconnect
change name
repeat

You wouldnt be able to ban someone offline.

Thats why it waits a little and sends /ban to the NEXT username that they would load.

Quote from: Freeware on October 25, 2003, 01:04 PM

Quote from: ___/\___ on October 25, 2003, 11:26 AM

Quote from: Freeware on October 25, 2003, 11:15 AM

Quote from: Grok on October 25, 2003, 07:31 AM
Is the next ops bot evolution something in cooperative banning?  Since an Ops channel can have two ops, if they were able to negotiate which users they were banning it would double the bannable number and banning speed.

Dualops (or for a Warcraft III 4x Ops) is very effective, I have just incorporated it into my bot. Banning flood bots like the titan could also be banned this way (this is the way my bot does it, and it DOES work against titans very well)

 .titanphrase <string> - Sets a string to recognize the bot as a titanbot. For an example if the titan says:

<TitanBot>: Your Clan Sux!
<TitanBot>: HAHAHAHAHA
<TitanBot>: Your Clan Sux!

 the string could be set to: Sux!

well that would work but what if they change the way they flooded to :
rejoin (5 times)
say Your Clan Sux! (Twice)
disconnect
change name
repeat

You wouldnt be able to ban someone offline.

Thats why it waits a little and sends /ban to the NEXT username that they would load.

Not everyone uses titans, so it would change its name to something random.

But I was talking about Titans...

Flood protection is indeed an issue.  Speaking from experience in Op [vL]/Clan [vL], which have been some of the most floodbotted channels on Battle.net, many attacks have been fast enough that without flood protection the operator bot would have flooded out and all bans would have been lost.

This is probably accomplished by using large quantities of SOCKS proxies or something similar, but it is most definitely something you need to worry about.

Skywing is right withought any anti-flood of some sort any floodbot is useless. But i suppose if it isnt effencient then no use trieng to ban the impossible.

Quote from: Grok on October 25, 2003, 07:31 AM
Is the next ops bot evolution something in cooperative banning?  Since an Ops channel can have two ops, if they were able to negotiate which users they were banning it would double the bannable number and banning speed.

I pondered this for my bot (zeroone) but i came to the conclusion that it would really only help against mass load attacks.  and while thats handy, denial showed me that a massload attack can't really be banned due to max banlist size.

But it would help against slow massload attacks that do not exceed the max ban limit.

Quote from: Grok on October 26, 2003, 08:00 AM
But it would help against slow massload attacks that do not exceed the max ban limit.

Yes it would. And, considering how most people are fools and don't know ANYTHING, this is the type of massload that you would have to deal with most often.

Maxban is 500 bans per key if i recall right it may be 250 per key.

It's an approx. amount of about 80 - 100 per op.

thats incorrect i have banned Vietphos 200 bots with  single op.

The ban (and squelch) limits have been 80 for years and years.

Quote from: Skywing on October 26, 2003, 06:58 PM
The ban (and squelch) limits have been 80 for years and years.

Incidentally, although it seems you can exceed the limit, what actually happens is that when you ban the 81st person, the 1st person you banned is no longer banned. Or at least that's how I recall it working.

Quote from: Zakath on October 27, 2003, 09:38 AM

Quote from: Skywing on October 26, 2003, 06:58 PM
The ban (and squelch) limits have been 80 for years and years.

Incidentally, although it seems you can exceed the limit, what actually happens is that when you ban the 81st person, the 1st person you banned is no longer banned. Or at least that's how I recall it working.

It is FIFO.

FIFO?