Second aimboter in since open beta.

(fascinatingThimble) #1

So I encountered my second aimboter since the game went open beta. I imagined the game would get an increase in cheaters but what is being done to prevent these kinds of cheats? Account bans based on reports? If that’s the only measure I might aswell throw in the towel now and wait for Overwatch. I sincerely hope preemptive measures are in the works since I’ve greatly enjoyed my time in Dirty Bomb so far.

(Ardez1) #2
  1. Account bans based on reports.
  2. XIGNCode3(which is junk, but better than absolutely nothing, barely).
  3. They are currently working to replace XIGN based on posts from MissMurder.

Do you believe that Overwatch with not have any cheaters in it at all then? If you have only seen two, then that isn’t too bad with hundreds of different servers to choose from.

Nexon knows that this is a huge problem and they are working on it.

(Amerika) #3

I’ve only ran into one aimbotter since about a week before Open Beta began. Considering how much time I’ve put in that’s pretty good. I also recorded the aimbotter and sent it off to support so he’s going to be gone soon (and it was a level 8 account).

Overwatch is an FPS. It will also have aimbots and cheaters just like every other FPS. The goal of an anti-cheat isn’t to automatically catch every single cheater as they are cheating. It’s not possible and it can also lead to better cheats that can get around that system. Instead cheaters typically get banned in waves so the cheat maker might not know exactly what was detected and might make the same mistake with an update. And it will hurt a lot of their customers all at one time which in turn hurts the cheat makers pocketbooks and can cause some of them to go out of business (a big WoW one went out of business recently).

XIGNcode does need to be replaced though. I did a bit of research on them and they do not have a great track record in regards to stopping very well known and old cheats, false positives or customer response time (for both devs and players).

#4

A few days ago I met four aimbotters. Since then I haven’t seen any.

I’m happy that Xigncode gets replaced though.
I personally don’t have any problems with its false positives but I know that others do.
Sometimes it determines normal programs like Skype as a cheat.

(Ghosthree3) #5

What scares me most about its false positives is it picks up things that could be used as a cheat even when they aren’t being used for such.

Very extreme example, a friend of mine had the suspect program popup come up twice on him because he had a mouse clicker running in the background he’s been using for clicker heroes over night. No idea what that game is or what the clicker is for but that’s not really important. He left it open because he couldn’t be bothered closing it and even though he never used it in the game it flagged him for it.

It should not punish unless it detects some kind of actual affect on the game itself. I know there’s also an issue with net limiting software being detected as a cheat even though it’s probably not being used for it.

If it’s going to flag people for simply running anything that could possibly change the game then it might as well just ban everyone now because the amount of software - including video drivers - that can do that is insane.

(Ardez1) #6

An autoclicker doesn’t affect the game, it affects your computer. No way to detect if it is being used for DB or not, so it simply isn’t allowed at all.

(Ghosthree3) #7

It is affecting the game, though indirectly sure. There’s an easy way to block/detect it, set a threshold on click inputs that when underneath either prevents the trigger going off or warns the user. Eg. 100ms between clicks - I have no idea how fast a pro can actually click a mouse in combat situations but use something around or just below that value.

If not that then at least do not punish for suspect exe detection, only warn the user to close it and refuse to start the game. Punishing is just beyond stupid, I do not know if it does or not, I certainly hope not.

(Ardez1) #8

It is affecting the game, though indirectly sure. There’s an easy way to block/detect it, set a threshold on click inputs that when underneath either prevents the trigger going off or warns the user. Eg. 100ms between clicks - I have no idea how fast a pro can actually click a mouse in combat situations but use something around or just below that value.

If not that then at least do not punish for suspect exe detection, only warn the user to close it and refuse to start the game. Punishing is just beyond stupid, I do not know if it does or not, I certainly hope not.[/quote]

Easier said then done and easily exploitable. Implementing this would be the same thing as saying it is allowed as long as you don’t break these rules. Not to mention your pc interprets any click action as coming from a peripheral. It doesn’t tell the game that it came from a software program. The game will think it is coming from a mouse.

(Ghosthree3) #9

I didn’t mention detecting the software at all in this case. Only detecting the clicks, which would detect a superhuman clicking the mouse and also allow clickers that are slow enough to be within human reach. On the other hand there are no false positives and it prevents outright abuse.

Best way is to just ignore clicks that are sent too quickly imo. Allows you to set the threshold a little higher and won’t punish anyone, it just means clicking faster than x is useless.

EDIT: Or like I said just warn the user to close any programs the game doesn’t like and only start once they have. But do not punish or flag them.

(Amerika) #10

In a perfect world XIGN would give a player a notice if they are running a banned program and prevents them from playing in the case of the clicker (macro application). But we’ve already covered how XIGNcode is anything but perfect.