Like this [Edited by Blizzard] guy. Check this out at timestamp 21:47.
game replay code: [Edited by Blizzard]
Watch him going after the junkrat. There’s no way he knew he was in that window. He was wallhacking, and throughout the game seemed to be aimbotting too.
His level was bronze 84, no stars, and he had a plat rank in comp. His maneuvering seemed clumsy, but his hacks were compensating for his lack of skills.
His hacks are pretty sophisticated when it comes to his aimbotting, but what makes it abundantly clear was his wallhacking. He would shoot us in ways where he could not have known we were coming around a particular corner, or at a certain position.
I seem to run into cheaters about half of the time when playing. What’s the deal? When will Blizzard start to cracking down on cheaters?
Forum Moderator Note: We do not allow accusations on the forums. Regardless of their validity, it is considered harassment. If you suspect that someone is cheating, report them in-game. Our Hacks Department will investigate and take action if they verify it.
First, naming and shaming isn’t allowed on the forums.
That said, maybe you didn’t realize that your team’s Rat was spamming a voiceline throughout the match. Anyone with headphones and a quarter of a working brain could tell which direction that noise is coming from.
He wasn’t at that time, so you’re lying. (yup just reviewed it again, he never once triggered the voice line you’re talking about) I watched it several times. If you can’t see the clear wallhacking there, I don’t know what to tell you. You must not know how to spot cheaters. That is clear wallhacking. Watch it at half speed. You can even see him jerk over, which is a smooth aimbot he has installed.
Address what I brought up. It’s not naming and shaming. It’s bringing up cheating, which should be shamed. This game is getting inundated with cheaters making it almost unplayable. Who in the hell wants to play OW2 if they can’t take care of this problem?
Someone needs to go after these monthly services providing cheats.
I’ll try to break down the first things that come to mind.
A. He saw the Junkrat on the bridge walking towards tiny room.
B. Next he saw, there was no Junkrat on the bridge. Where did Junkrat Go?
C. Saw Sigma on the Bridge going into the tiny room.
D. As soon as he saw Sigma, realization: maybe Junk is in room!
C. Find Junkrat in tiny room.
D. After going into tiny room, get surprised by a Soldier he didn’t see through walls.
If the Sigma wasn’t there, I’d agree that it looks fishy. A pretty quick movement to what looks like nothing. But since there WAS a stimulus that could have reasonably provoked that reaction, it seems like a more reasonable explanation.
I heard his footsteps before he was visible at the doorway and would have shot him there too.
A lot of people call cheats for “aiming through walls” in plat, the reason for this is experienced players are actively tracking the footsteps/ability sounds through walls and then positioning their crosshair where they expect them to peek out from.
That jerking motion, is a flick, which lands nowhere near the Junkrat’s hitbox and was his natural reaction to hearing the footsteps.
I watched a couple minutes of his gameplay and don’t see anything suspicious about his aim.
THAT BEING SAID, there has been an influx of cheaters recently, but I don’t think this guy is cheating.
Object Permanence:
Object permanence is the understanding that objects continue to exist even when they cannot be seen, heard, or otherwise sensed. This is a fundamental concept studied in the field of developmental psychology.
Just report and see what support will say. I play with lot of aimbotters hanzos that they arrow make curves to my head, people will say that is game feature also?
For strange reason every headshot i take from hanzo’s, most 90% of hits comes from a arrow that simple make closed curves on air. So i report every hanzo that exist in any match.
This is applicable to real life only, in games its more simple, you can see? you can hit, you cannot see, but you can hit? server will predict if in fact hit is valid (based on surfaces, enemies barrieries etc).
Also an object cannot exist if they cannot be seen, like black holes in universe, we know they exist because they pull radiation around him, black hole eats light (that make more difficulty to find them) but we still able to know they exist.
See population, when someone dies/object is destroyed, it don’t exist anymore, you have only stuff that you can remember that people, pet, object, but still will not exist anymore.
Sounds like you are false reporting many Hanzos as what you notice isnt a hack but the whole ‘favor the shooter’ thing OW has, if it hits you on their side then it registers as a hit no matter what you see, thats why it curves like that. Plus what you are suggesting seems close to impossible to go on for so long in a server-sided game, especially one as big as OW.
I’m not reporting every hanzo, i report every hanzo that make his arrow curves and headshot me, i can see this in killcam and deathscreen, based on old player stats on that match i report, because many people can abuse from an hero shooter and hide cheat to make similar to real player movement. So half of these reports i receive feedback about them ‘Thanks for reporting’ screen after i login into game.
Not just “killed me then i will report”, i analyze every match before report someone.
Also in overatch servers ensure 100% both client and server are syncronized, so if both have low latency, i don’t except hanzo arrows making curves, since both clients ticks are matched with server timer.
For players:
High latency: Server syncronize all player data with latest data snapshot server has, and keeps using this snapshot replicating untill player sends another input.
Low latency: Server both syncronize all player data, but if someone input is more faster than another one of them will be rejected, because is overpassing server tick.
For projectiles:
You send input to spawn projectile, this is ticked to server and replicated to client, so isn’t impossible to arrow make curves on server side, because projectile will hit last know player position.
I usually have extreme low latency, about to 9ms~30ms on my region, so isn’t latency problem here.
That makes me think, only way to do this is predicting player position, but for lagged player will receive wrong view position and never will hit someone, or in fact is low latency, but an aimbot smoothly moving aim to predict next player position.
This isn’t about hitting shots, this is about understanding that when somebody hides behind cover, they still exist, they are just not visible from your perspective currently. This is why, at the marked time in OP’s VOD, it’s not unusual for the Pharah to check the opposite opening, especially after hearing footsteps indicating that the Junkrat was heading that way.
This is largely irrelevant, a Hanzo behind a wall cannot be seen from the opposite side of the wall, but he still exists behind the wall. He is not invisible or ceasing to exist, he is just shielded from view temporarily.
A big reason that many people cannot climb out of lower ranks is that they do not understand that when a threat becomes invisible (hiding behind cover), they no longer pursue, respect, or otherwise give any attention to that threat, only to be destroyed by them seconds later when they re-peek a different angle.
This is also not relevant, all abilities in this game follow “favour the shooter” as others have said. This means that you can still be hit by an ability, regardless of whether the ability visibly hits you on your client.
Every player has 3 positions. Client side (you), client side (enemy/ally), and server side.
If client side (enemy) shoots an arrow and it visibly hits on client side (enemy), even if you dodge or move out of the way on client side (you), the server will register it as a hit in most cases. The best example of this is when a Tracer blinks from point A to point B, but she is stunned, cc’d or dies at point A, even though her client shows her briefly at point B, only to be moved back to point A, also known as “rubber banding”.
But this is neither here nor there, Hanzo arrows (projectiles in general but Hanzo’s are one of the most noticeable outside of Mercy’s pistol) have larger hitboxes than what is shown ingame, which when you factor favour the shooter into it, results in the arrow “snapping” to your head on your client. There are no cheats that will adjust an arrow’s path after it is fired, only the aim of the player firing them.
Very unrelated to OP but that’s your explanation for that.
I dont think name and shame is allowed here. But I do agree that game companies should do more about it. if people are cheating. Such as… shaming them.
That is what H1Z1 did, when players cheated. Each day they had a message board up, on players cheating, and their gamer tags.
Is naming and shaming when people just give replay codes and ask “is this a cheater”? Watch for Ashe at [timespan] and then we all see the name of a player?
I think it’s quite same crap but I don’t see moderators editing those posts.
