In article <3t4l44dnr7dt9e7tnefuv9vip452i1oet6@[EMAIL PROTECTED]
>,
Chemo Savy <Tonto@[EMAIL PROTECTED]
> wrote:
> On Mon, 05 May 2008 06:50:24 -0500, Chemo Savy <Tonto@[EMAIL PROTECTED]
>
> wrote:
>
> >
> >I just reviewed the archives on this subject and there doesn't seem to
> >be anything more recent than 2005. I would appreciate any further
> >information on the following:
> >
> >There seem to be 3 types of temp ban. The first lasts up to 30 min.,
> >the second several hours (maybe 24), and the third is for 3 days. I
> >have experienced all three but am not sure what actually triggers the
> >3 day one.
> >
> >The first ban seems to be the first one "for that day" and is
> >triggered by either too many games/hr (known as the 20 game/hr limit),
> >or by joining games too fast, as when trading or muling furiously. The
> >24 hr ban seems to be triggered if you have previously had a short ban
> >preceding in the 24 hr. period (ie. the second ban of the day).
> >
> >Does anyone know what triggers the 3 day ban?
> >
> >Does joining games count the same as making new games (ie could I make
> >20 new games in an hour and join a few already made games) or does the
> >joining of games count on the new game total too? Is there a limit on
> >the number of just "joining" games?
> >
> >Any facts or speculation on the above would be appreciated.
> >
> >Chemo
>
> It seems there is probably a games/24hr. limit too. I just ran into
> that when I did over 240 games at 12/hr. and got a 12 hr. temp ban. It
> was either that or a glitch ban that occured without the initial 1 hr.
> temp ban. Anyone know anything about such an animal, and what is the
> specific games/24 hr. limit?
>
> Chemo
I'd be *VERY* surprised if there was any definitive answer to those
questions. Dunno about Blizzard, but if I were designing such a thing in
order to prevent abuse, I'd definitely *NOT* tell anybody the specifics
involved - Doing so would be little short of an invitation to the
script-kiddies to design the "optimal" bot for spamming - "OK, we know
that if the bot joins more than 20 games in an hour, it'll get banned,
so we'll code it to only join 19 games, then change keys and repeat,
and..."
In fact, I'd very likely make the trigger for slapping a ban on someone
at least somewhat random, for exactly that reason - Instead of a "hard"
20 join limit, I'd probably set things up to start generating a random
number at the 15th join, for instance, and if the random number came up
lower than some value, drop the value slightly, and allow the join to
happen. Next join, new random number - If still below the threshold
value, allow the join after lowering the threshold, etc, etc, etc. This
would keep the script-kiddies from "tuning" a bot reliably.
--
Don Bruder - dakidd@[EMAIL PROTECTED]
- If your "From:" address isn't on my
whitelist,
or the subject of the message doesn't contain the exact text
"PopperAndShadow"
somewhere, any message sent to this address will go in the garbage without
my
ever knowing it arrived. Sorry... <http://www.sonic.net/~dakidd>
for more
info
|
