News:

So the widespread use of emojis these days kinda makes forum smileys pointless, yeah?

Main Menu

Massload Prevention

Started by Lance, June 16, 2008, 08:27:15 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Lance

How can I prevent being loaded & flooded out from JavaOP2? My bot auto-bans someone without flags (meaning it tries to ban the loads) and it drops. If I turn on antiflood commands take a long time to work but loading is my main concern.
Quote from: Joe
[23:55:31] [william@enterprise ~/Documents/Programming/javaop2]$ svn commit -m 'Tried to fix StayConnected. Again.'
Committed revision 63.
StayConnected strikes back!

rabbit

Don't ban every flagless person.

Lance

#2
i don't want to have the channel full of noobs saying "vouch me, vouch me!!!" and taking up space vouched players should have

although i may be able to modify it to only do so for war3/w3xp clients and i have to manual kick anything else :o

if(statstring.contains("3RAW") == false && statstring.contains("PX3W") == false) { return; }


Think this should work ^_^
Quote from: Joe
[23:55:31] [william@enterprise ~/Documents/Programming/javaop2]$ svn commit -m 'Tried to fix StayConnected. Again.'
Committed revision 63.
StayConnected strikes back!

Camel

If you're in a clan channel, and you detect a flood, I'd recommend /c priv, for a short period of time.

If you're getting loaded faster than bnet will allow you to ban without flooding off, the flooder is in clear violation of the TOS, and you can ask a battle.net representative to come log your channel so they can ban the offender.

<Camel> i said what what
<Blaze> in the butt
<Camel> you want to do it in my butt?
<Blaze> in my butt
<Camel> let's do it in the butt
<Blaze> Okay!

pro_

I doubt blizzard can do anything permanent.  If you are up against a strong flood you are dealing with thousands of cd keys over hundreds of proxies, the only way to deal with it is to set clan private until the flooder gets bored.  If you need to get into channel with a non clan acct, make a script to unlock the channel for a bit after you whisper it a password.

Camel

Or, you can get a blizzard rep to log your channel, and perm ban every key and ip that flooded. I don't know why you think there's not much they can do; that is their procedure - that's what they have always done, and that's what they still do.

<Camel> i said what what
<Blaze> in the butt
<Camel> you want to do it in my butt?
<Blaze> in my butt
<Camel> let's do it in the butt
<Blaze> Okay!

DBX_5

Blizzard/Bnet Reps do not protect Clans from Flooders any more, its been like that for a long time, Several clans including GGL and TDA have asked for assistance several times and been denied every time.

Camel

Quote from: DBX_5 on August 14, 2008, 06:19:38 AM
Blizzard/Bnet Reps do not protect Clans from Flooders any more, its been like that for a long time, Several clans including GGL and TDA have asked for assistance several times and been denied every time.

That is just untrue. I can think of at least two clan channels at, at this very moment, have a channel limit of 39 users due to a (hidden) blizz rep logging chat.

<Camel> i said what what
<Blaze> in the butt
<Camel> you want to do it in my butt?
<Blaze> in my butt
<Camel> let's do it in the butt
<Blaze> Okay!

Lance

The reps have told a few people I know to fill out a web form and leave them alone pretty much.
Quote from: Joe
[23:55:31] [william@enterprise ~/Documents/Programming/javaop2]$ svn commit -m 'Tried to fix StayConnected. Again.'
Committed revision 63.
StayConnected strikes back!

Armin

If you don't at least try the solution provided yourself, don't ask for help.
Hitmen: art is gay

Camel


<Camel> i said what what
<Blaze> in the butt
<Camel> you want to do it in my butt?
<Blaze> in my butt
<Camel> let's do it in the butt
<Blaze> Okay!

Lance

I've just edited the Simple Event processor and it completely ignores anyone @USEast. Works great :]
Quote from: Joe
[23:55:31] [william@enterprise ~/Documents/Programming/javaop2]$ svn commit -m 'Tried to fix StayConnected. Again.'
Committed revision 63.
StayConnected strikes back!