Official Everybody Edits Forums

Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?

You are not logged in.

#1 2015-04-15 13:51:21

Hexagon
Member
Joined: 2015-04-22
Posts: 1,213

[Question] Finding key "spammers"

Are there any solutions to finding players who "spam" the keys? Since player id doesn't come with the key event it makes things difficult.

Has anyone tried doing this? I'd imagine it'd have to use some sort of physics to determine where all of the players are and whether they are intersecting the key block.

Offline

#2 2015-04-15 14:12:05

goeyfun
Member
From: Mighty Japan
Joined: 2015-02-18
Posts: 667

Re: [Question] Finding key "spammers"

What if it's a key spam bot //forums.everybodyedits.com/img/smilies/tongue


Ug3JzgO.png

Offline

#3 2015-04-15 14:27:23

Hexagon
Member
Joined: 2015-04-22
Posts: 1,213

Re: [Question] Finding key "spammers"

goeyfun wrote:

What if it's a key spam bot //forums.everybodyedits.com/img/smilies/tongue

Didn't think about that. I guess it would only work if the world didn't allow everyone to edit (i.e free edit) or there was only one or two people that could edit. If you can send key commands without having edit access, then this will virtually never work, unless user id is associated with keys.

Offline

#4 2015-04-15 15:22:08, last edited by DarkDragon4900 (2015-04-15 15:23:24)

DarkDragon4900
Member
Joined: 2015-03-17
Posts: 251

Re: [Question] Finding key "spammers"

This had already been discussed.
I can't recall at which post, though.

Offline

#5 2015-04-18 02:47:06

meagainhey
Member
Joined: 2015-04-15
Posts: 7

Re: [Question] Finding key "spammers"

it's really impossible to figure out.

Keys aren't sent with user ID...
and users don't have to register movement to hit the key.

You can't even target those who aren't moving because many people skip the bot route and WPE Pro the packets.

Offline

meagainhey1429321626495846

Board footer

Powered by FluxBB

[ Started around 1714333351.716 - Generated in 0.034 seconds, 10 queries executed - Memory usage: 1.4 MiB (Peak: 1.51 MiB) ]