Cheater is not getting banned after tens of reports

[theonelomi]

https://tracklock.gg/players/1756662873

This mofo has been aimbotting in several games and despite the amount of reports (Probably 4 to 10 each games considering all the chatting about it ?) he's still here, playing the game after weeks. In high elo too, striking a 75% winrate.

He's even aimbotting in street brawl, it's completely insane.

What do we have to do to get this cunt banned already ? Do we need him to ruin 100 more games before he gets definitive ban or what ? Reports do nothing here.

I know this is not the right forum, but I don't see what else I can do except posting here ?

Edit : Actually, "cheating reports are not doing anything" would be the correct bug title for this post. Because that's the truth

 

[theonelomi]

BUMP

 

[theonelomi]

BUMP
I'll do this until I get banned myself or this dude account gets terminated.
He is playing eternus 6 with 80% win rate what the fuck

 

[OrangeFreeman]

As much as this sucks, the right approach would be to ban cheaters in waves. If you ban someone the moment the detection system fires, cheaters can probe exactly which behavior triggered it and update their cheat software to avoid that signature. Ban them weeks later in a batch, and they have no idea which session, which action, or which detection method caught them. Makes reverse engineering the system nearly impossible.

Valve does this with VAC notoriously. Bans can come months after the infraction. Blizzard ran the same playbook with Warden in WoW. The delay also serves as a honeypot: let the cheater keep playing, keep logging their behavior, potentially catch their whole network of alt accounts and friends before dropping the hammer all at once.

There's also a psychological element that developers openly enjoy: ban waves often happen right after a new cheating tool becomes popular, so the cheat developers wake up to thousands of angry customers demanding refunds simultaneously. It tanks the cheat software's reputation and makes their business model miserable.

The tradeoff is that legitimate players get stomped by cheaters for weeks or months while detection data accumulates, which is a genuine cost. Games with ranked systems or economies take real damage during that window.

 

[theonelomi]

As much as this sucks, the right approach would be to ban cheaters in waves. If you ban someone the moment the detection system fires, cheaters can probe exactly which behavior triggered it and update their cheat software to avoid that signature. Ban them weeks later in a batch, and they have no idea which session, which action, or which detection method caught them. Makes reverse engineering the system nearly impossible.

Valve does this with VAC notoriously. Bans can come months after the infraction. Blizzard ran the same playbook with Warden in WoW. The delay also serves as a honeypot: let the cheater keep playing, keep logging their behavior, potentially catch their whole network of alt accounts and friends before dropping the hammer all at once.

There's also a psychological element that developers openly enjoy: ban waves often happen right after a new cheating tool becomes popular, so the cheat developers wake up to thousands of angry customers demanding refunds simultaneously. It tanks the cheat software's reputation and makes their business model miserable.

The tradeoff is that legitimate players get stomped by cheaters for weeks or months while detection data accumulates, which is a genuine cost. Games with ranked systems or economies take real damage during that window.

I want to believe this is true. But a total of 100 games ? 20 days so far ...
Imagine a hacker in Apex Challenger in LoL, that sounds ludicrous to me.

 

[barlakopofai]

As much as this sucks, the right approach would be to ban cheaters in waves. If you ban someone the moment the detection system fires, cheaters can probe exactly which behavior triggered it and update their cheat software to avoid that signature. Ban them weeks later in a batch, and they have no idea which session, which action, or which detection method caught them. Makes reverse engineering the system nearly impossible.

Valve does this with VAC notoriously. Bans can come months after the infraction. Blizzard ran the same playbook with Warden in WoW. The delay also serves as a honeypot: let the cheater keep playing, keep logging their behavior, potentially catch their whole network of alt accounts and friends before dropping the hammer all at once.

There's also a psychological element that developers openly enjoy: ban waves often happen right after a new cheating tool becomes popular, so the cheat developers wake up to thousands of angry customers demanding refunds simultaneously. It tanks the cheat software's reputation and makes their business model miserable.

The tradeoff is that legitimate players get stomped by cheaters for weeks or months while detection data accumulates, which is a genuine cost. Games with ranked systems or economies take real damage during that window.

It is not, there is no reason to have the pretense of cheat detection when you have manual user reports. Why would you possibly need to wait for a ban wave if the guy has been caught red handed by multiple people?

 

[z_strout]

Ya, I just got done playing a match earlier this morning (could no sleep) and came across a Lash that was using a map hack / tracker. I was playing Haze the dude, Hikioamori, was tacking my movements while I was stealth, off the side waiting ambush in team fights (at least 4 times). The dude kept on moving towards someone while he was looking at the position before engaging. I know this was a old hack issue last year, but it is still shitty to see people still using it and not getting banned for it.