R77 Community Forum Archive

Major Projects => Advanced Moderation => Topic started by: Shadow on September 19, 2008, 12:58:55 PM

Title: AM Discussion
Post by: Shadow on September 19, 2008, 12:58:55 PM

If I remember correctly, we were working on the following ideas:

Limit The Amount of Access an individual user is able to give out
  EX: Shadow can only give out 20 access even though he has 60
Delay Ban
  EX: The ban command is given 3 times in 1 second by 3 different users.
      User1 was banned by Bot
    Wait 2 seconds
      User2 was banned by Bot
    ETC

That's all I remember at the moment...

Title: AM Discussion
Post by: Hero on September 19, 2008, 01:25:52 PM

Ace was also planning on adding anti-spam protection based on #'s in usernames

Title: AM Discussion
Post by: ArticWolve on October 15, 2008, 04:48:57 PM

~BUMPING~
SO when are we going to tackle the Limit part of this, or is that going to be a stand alone (I feel it should be part of this script)

Title: AM Discussion
Post by: Hero on October 15, 2008, 04:56:20 PM

Someone can do it whenever. I am not going to.

Title: AM Discussion
Post by: ArticWolve on October 15, 2008, 06:06:34 PM

If I could make it, I would... so that leaves only a few left rofl.... Hey wasn't ace working on something like this already??

Title: AM Discussion
Post by: Vector on October 16, 2008, 10:33:27 AM

I'll do it. I've only added one feature to this plugin, and I need to add something else =/

Title: AM Discussion
Post by: ArticWolve on October 16, 2008, 12:58:25 PM

And would this work with Stealthbot Beta's AND Version 2.6 R3??

Edit: Seen the line where you have it set to 70. That line should be in AM.ini you know...

Title: AM Discussion
Post by: ArticWolve on October 16, 2008, 03:15:45 PM

So then quick question, let's say I am using the beta, and I changed access requirements of Add, set, remove and their aliases to say 150. Would it still be able to work? (And a quick tutorial would be nice)

And also, the LIMIT command should be able to apply to anyone without the "A" flag I hope...

Title: AM Discussion
Post by: ArticWolve on October 19, 2008, 02:41:06 PM

Permission to use in future scripts?

Title: AM Discussion
Post by: de80 on November 14, 2008, 03:50:42 PM

Can someone please post all cmds?

Title: AM Discussion
Post by: ArticWolve on November 14, 2008, 04:00:17 PM

Arguments in <> are mandatory, while those in [ ] are optional.
The only command:

.Limit <User> <Access>
Effect: Limits user to only give out equal or lesser access then he/she was limited to by you.

Title: AM Discussion
Post by: Hero on November 14, 2008, 04:37:26 PM

Most of the things you can do are change the settings used to detect spam.

Title: AM Discussion
Post by: Vector on November 17, 2008, 08:07:48 AM

I'm going to re-do NumSpam (sorry ace) and add in general flood detection as well. (currently, it only works with numbered names. Geno can spam using random characters too.)

Title: AM Discussion
Post by: Ace on November 17, 2008, 01:26:00 PM

Quote from: Vector

I'm going to re-do NumSpam (sorry ace) and add in general flood detection as well. (currently, it only works with numbered names. Geno can spam using random characters too.)

Not really...
It bases it off of ping, if a # is in the username (as in Geno#125), client, and lag plug.

Title: AM Discussion
Post by: ArticWolve on November 17, 2008, 01:30:10 PM

Well, most spammers use one account like Nes. Others use random names, and yet others use both. So yeah, that part should be redone me thinks.

Title: AM Discussion
Post by: Ace on November 17, 2008, 01:33:38 PM

Quote from: 7thAce

It bases it off of ping, if a # is in the username (as in Geno#125), client, and lag plug.

Username isn't thing only thing it checks.  I doubt there are many d2/wc3 spammers without lagplugs and <400 ping.

Title: AM Discussion
Post by: ArticWolve on November 17, 2008, 02:48:30 PM

triple post by topic splitting. And yes ace there aren't that many...

Title: AM Discussion
Post by: Vector on November 17, 2008, 04:58:15 PM

I"m not going to base it off that. I'm going to base it off of how many people join in one second. Say, if three join in the span of 1 second, then there is a potential flood. I may gase it off ping too.

Title: AM Discussion
Post by: Hero on November 17, 2008, 07:26:22 PM

We already have something for when users join too fast..

"Join Spam" -- I added it

Title: AM Discussion
Post by: ArticWolve on November 21, 2008, 07:37:17 PM

Well in any case, everyone, including me, failed to add in a safelist check until 0.211 I believe. Anyways, I think this is ALMOST done ><