Forum

EDIT:
See this post for info about screenshots:
http://etf2l.org/forum/general/topic-21038/page-24/?recent=406689#post-406387

AnAkIn’s Anti-Cheat
—————————————————
Site: http://tftrue.esport-tools.net/anakinac.html

Description
—————————————————
List of detections:
– Detect prediction hacks (crit hacks & no spread hacks)
– Detect an exploit to bypass the old anti speedhack protection
– Detect potential auto shoot, auto zoom, auto stickybomb det, auto airblast and auto cloak hacks
– Detect hacks that modify viewangles

The detections get printed to a log called TriggerBotDetections.log (can be changed with aac_logname) in tf/ (and are also sent to me) on EVERY MAP change
or when all players have disconnected from the server.
It’s important to remember this otherwise you could loose all the detections (especially if your host restart the server every night).
There is a simple reason for this: writing in a file while you play can cause lags, especially if someone is getting detected a lot.

Auto shoot hacks
—————————————————
It is not because someone has such detections that he is surely cheating.
It’s just a tool to help you find people that can potentially cheat and you can just check the demos then to confirm that they were cheating or not.
The most detections for a single person you will find in the log, the more likely he is using one of these cheats.

Automatic kick/ban
—————————————————
Cheaters detected with prediction hacks, anti-speedhack bypass hacks and invalid viewangles will be automatically banned if aac_prediction_ban, aac_speedhackbypass_ban and aac_viewangles_ban are set to 1 (default).
You can use the local banlist (aac_banmethod 0) or use SourceBans, if installed on your server (aac_banmethod 1).

For the local banlist, the banned cheaters can be seen with aac_showbans, or by opening the aac_banned.txt file in the tf directory.
You can also remove a ban with the aac_removeban command.

Original message, please read below:

Hey,
Back in January I started working on a plugin that can detect POTENTIAL triggerbotters. It has been installed secretly on many servers, but it’s not really a secret as some people decided to not keep the secret and almost everybody heard about it very quickly.

To make it clear as some people didn’t understand, the detection is kind of “heuristic” (I won’t explain in detail, if I do then the cheat coders will bypass it in no time), so it’s not because someone got detected that he is surely cheating. It’s just a tool to help you find people that can potentially cheat and you can just check the demos then to confirm that they cheat or not.

The detections get printed to a log called TriggerBotDetections.log in tf/ (and are also sent to me) on EVERY MAP change or when all players have disconnected from the server. It’s important to note this otherwise you could loose all the detections (especially if your host restart the server every night). There is a simple reason for this: writing in a file while you play can cause lags, especially if someone is getting detected a lot.

The most detections for a single person in the less timespan you will find in the log, the more likely he is using a triggerbot.

I was able to check some of the STV demos to see if some of the detected people were really cheating, there were lot of people cheating with F2P accounts though, so it’s pointless to list them, and there were some where the server was not recording, so I was not able to check them. Here is a quick list:

Didgi – http://etf2l.org/forum/user/2939/ – 10/01/12
boomeh – http://etf2l.org/forum/user/1423/ – 14/01/12 and 19/01/12
rub – http://etf2l.org/forum/user/33960/ – 21/01/12
Fix – http://etf2l.org/forum/user/24119/ – 20/01/12, 09/02/12
danny – http://etf2l.org/forum/user/5333/ – 25/03/12
Fwn – http://etf2l.org/forum/user/6352/ – 25/03/12, 26/03/12, 28/03/12 and 29/03/12
reactioN – http://etf2l.org/forum/user/17083/ – 04/04/12

Unrelated (maybe not after all) DBlocker ( http://dblocker.didrole.com/ ) is not a new Anti-Cheat but it can catch a lot of cheaters as well.

Thanks to:
Casual/2k – for giving me the idea on how to make the triggerbot detection
Didrole – sometimes being helpful
Everyone who tested the plugin on their servers (better not give names or it would let people know on which servers it’s installed)

Download: http://tftrue.esport-tools.net/TriggerBotDetector.zip

EDIT:
Some stats about the number of detections for each one:
Didgi – 25 in 10 mins // Average: 2.5 detections/min
boomeh – 75 in 24 mins – 37 in 46 mins // Average: 1.96 detections/min
rub – 26 in 30 mins // Average: 0.8 detections/min
Fix – 273 in 50 mins – 313 in 34 mins // Average: 7.33 detections/min
danny – 200 in 21 mins // Average: 9.52 detections/min
Fwn – 95 in 34 mins – 36 in 5 mins – 137 in 39 mins // Average: 4,5 detections/min
reactioN – 118 in 11 mins // Average: 10.72 detections/min

Note that it doesn’t mean anyone with this number of detections might be cheating for sure, remember that you always have to check the demos.

ooh drama

http://www.youtube.com/watch?v=xzpndHtdl9A

Cool.

good job

http://www.threadbombing.com/data/media/2/THISGONBGUD.gif

http://www.youtube.com/watch?v=IUH3JQjcweM

now in HD

AnAkIn 2012

Quoted from Casual

[…]

Big hush-hush secret. A few people have been banned before this plugin after I reported them to Gubbins relying on the same heuristic.

How is your STV spectator plugin coming along?