Valhalla Legends Archive

Perhaps you could implement a function that alerts Blizzard when people violate their agreements. You could log the incident, and send an e-mail letting them know what happened. It would not instantly stop a flood/spam attack but it could lead to cd-key bans and possibly help filter out the bad seeds over time.

Does this sound like a practical idea? I am not too familiar with Blizzards policy on the subject, but I would assume they are just as eager as us to get rid of the flood bots.

Quote from: Tuberload on February 06, 2004, 12:44 AM
Perhaps you could implement a function that alerts Blizzard when people violate their agreements. You could log the incident, and send an e-mail letting them know what happened. It would not instantly stop a flood/spam attack but it could lead to cd-key bans and possibly help filter out the bad seeds over time.

Does this sound like a practical idea? I am not too familiar with Blizzards policy on the subject, but I would assume they are just as eager as us to get rid of the flood bots.

Nice idea, turn any flood bot into an e-mail spammer...

You'll find out whether they choose to ban the flood bot or the e-mail spammer first I suppose

Quote from: Adron on February 06, 2004, 04:27 AM

Quote from: Tuberload on February 06, 2004, 12:44 AM
Perhaps you could implement a function that alerts Blizzard when people violate their agreements. You could log the incident, and send an e-mail letting them know what happened. It would not instantly stop a flood/spam attack but it could lead to cd-key bans and possibly help filter out the bad seeds over time.

Does this sound like a practical idea? I am not too familiar with Blizzards policy on the subject, but I would assume they are just as eager as us to get rid of the flood bots.

Nice idea, turn any flood bot into an e-mail spammer...

You'll find out whether they choose to ban the flood bot or the e-mail spammer first I suppose

I would assume it only sends a single email for a floodbot :/

I don't think Blizzard particularely cares, though.

if they really cared in the slightest they would just completly change the game prot.ocol or make a minute (probally very hard to find) change

IIRC, the actual bot that sends the email is also in violation of the EULA of B.net.

Quote from: NuLL on February 06, 2004, 07:40 AM
if they really cared in the slightest they would just completly change the game prot.ocol or make a minute (probally very hard to find) change

They could limit bots in other ways, too, without having to update their game clients.  But most of all, they could automaticly detect them and ban their cdkeys (I don't see any other reason that FloodBot#23 would be online unless it was either a winbot or a floodbot, neither of which they should allow).  But they don't, so obviously they don't care.  Moo.

I've often thought that too. Why would they not void cdkeys logging any account with a multiple number '#'? Like you say, they can't be that bothered about it.

Well, just because you have a # in your name, you dont have to be a bot.  People do share accounts...But anything higher than #5 its reasonable to assume its a bot.

I also assume bnet allows 8 connections from 1 ip for people who have LANs.

Quote from: Eternal on February 06, 2004, 08:01 AM
I've often thought that too. Why would they not void cdkeys logging any account with a multiple number '#'? Like you say, they can't be that bothered about it.

What if you leave your war3 on and go to the LAN cafe or your friends house.

You have to log in on a #2.

They could easily gather up thousands of CD-keys which break the ToU and disable them. The problem is, most of the mass CD-keys people own are what they've stolen from someone else. So such a mass ban would result in massive complaints from the original owners of the CD-key.

Future restrictions to Battle.net will make attacks more weaker. Until then, your best option is to let Blizzard do their job while you not worry about it and think of other methods to block them out (e.g., an auto-ignore if short visit).

Spht are there any functions on these forums that show how to auto filter a floodbot or anything? like a 1 second join and leave. How could u implement that?

Quote from: Networks on February 06, 2004, 12:26 PM
Spht are there any functions on these forums that show how to auto filter a floodbot or anything? like a 1 second join and leave. How could u implement that?

By checking the amount of time since he joined when he leaves, and if it's small enough ignore him completely?  It isn't that difficult to do if you know anything about programming.

If Blizzard cared, they could do more to temporarily change the situation.  Flooders would adjust their methods.  The best Blizzard can hope to do is block methods which are beneficial to bots, but serve no useful function for regular gamers.

That said, it is not practical to write their servers to prevent floodbots, because the design specifications would change the moment they implemented the previous model.

For example, I could create 200 email accounts, 200 random-letter names, use 200 CD-keys, on 500 different internet addresses.  Generally, this is how average gamers appear to battle.net -- unique names from all over the world.

How do you combat it?  More importantly, is it worth it to spend shareholder dollars on combatting it?  Probably not.  Floodbotters are only annoying a few people out of millions, and not doing damage to battle.net.

Quote from: Grok on February 06, 2004, 12:59 PM
How do you combat it?  More importantly, is it worth it to spend shareholder dollars on combatting it?  Probably not.  Floodbotters are only annoying a few people out of millions, and not doing damage to battle.net.

So, the solution to our problem is to ensure that floodbotters annoy a larger share out of the millions, and so become a problem worth spending shareholder dollars combatting?

Quote from: Adron on February 06, 2004, 01:37 PM

Quote from: Grok on February 06, 2004, 12:59 PM
How do you combat it?  More importantly, is it worth it to spend shareholder dollars on combatting it?  Probably not.  Floodbotters are only annoying a few people out of millions, and not doing damage to battle.net.

So, the solution to our problem is to ensure that floodbotters annoy a larger share out of the millions, and so become a problem worth spending shareholder dollars combatting?

If that is what it may take.. perhaps turtle released his floodbot source thinking the exact same thing in hopes blizzard/bnet will do something about it.