TL GM / Master hacker thread contains a database of confirmed hacker and is a place to discuss general hacking / cheating related subjects. keep it civil and productive.
skip to database
WoL GM/Master hacker thread
05.01.2013: starting up
as more hots replays came in and as hyeon provided me with HOTS beta access (thanks) i decided it was time to start this bad boy up. the format will remain somewhat the same, but try to use the template when submitting a replay, and add a tag to the submission. i'll revert back to the old TL Hacker Database threads style and group hackers by season. the OP also contains a list over strong and weak proof, well worth a peep.
submitting a replay
i would prefer it if you uploaded the replays on drop.sc. that's where i'll be uploading them anyways, and you'll save me a few clicks, but it's not a must.
the first line of your submission should be a tag. these tags have two purposes. first of all it makes it easy for me to prioritize, and it helps you not putting your foot in your mouth.
[SUSPECTED HACKER] - when you observe strong evidence of hacking or a plethora of weak evidence.
[NEEDS REVIEW] - this tag is for you to use when you have a replay that you think is suspicious, but contains no hard evidence. if you have even the slightest doubt, use this tag.
this entry identifies the player. it is not enough with just a name, please provide the battle.net profile url as well. battle.net url can be found through the persons drop.sc page or through sc2gears (right click on their profile pic after loading a replay).
self explanatory. EU/NA/KR/SEA.
provide league, points and preferably sc2ranks.com url. not only is it needed for infering what can and what can't be interpreted as evidence, but in addition a name change seems to take longer time on sc2ranks, in case of somebody trying to do a vanishing act. the sc2ranks url can be found on the players drop.sc homepage or through sc2gears in the same manner as bnet url.
provide replay link, and instances of strong / weak evidences, as well with timestamps. the more conclusive the replay is, the more specific you can be, and the more specific you are, the more information you should fill out (spawns, races, ladder pointrs). do NOT post guesswork based on a replay tagged [NEEDS REVIEW, again, err on the side of caution.
- copyable template
words in caps are for you to fill in. be as descriptive as you feel is relevant. do not remove the colons before and after RACE, or you'll miss out on a cute icon.
[TAGCOLOR (red FOR RED ETC)][b]TAGNAME[/b][/TAGCOLOR]
[b]Name:[/b] :RACE(P FOR PROTOSS ETC): [url=BATTLENETURL]NAME[/url]
[b]Rank:[/b] [url=SC2RANKSURL]LEAGUE, POINTS[/url]
[url=REPLAYURL]PLAYERNAME (RACE) vs PLAYERNAME (RACE) @ MAPNAME[/url]
list of confirmed hackers
[CONFIRMED HACKER] barcode
[CONFIRMED HACKER] Python
[CONFIRMED HACKER] GEHSEKKI
[CONFIRMED HACKER] RTStrauma
[CONFIRMED HACKER] ƇħųƈƙƝǿƦƦìs
[CONFIRMED HACKER] Nerffy
[CONFIRMED HACKER] EGHukRC
[CONFIRMED HACKER] xDaRkSLaYeRx
[CONFIRMED HACKER] TriniXY