I may go back to tf2 / csgo, Overwatch is a good place. You cannot dodge enemies' attack if your enemies really hit you.
Comment has been collapsed.
They can't fix a bug until they know that either A: the bug exists and B: how to reproduce it.
In this case people apparently just never noticed.
Comment has been collapsed.
Considering they take months to fix known game breaking bugs and lied about other things being fixed before, I am genuinely surprised that they even fixed it.
Comment has been collapsed.
Somehow I'm not surprised of Valve. Also this is a mega trap when claimed, -2 points.
Comment has been collapsed.
At least read my post. :P
This reply cannot be claimed
Comment has been collapsed.
I did, I guess my compression isn't that good
I understood that the first one gets the point
I'm a moron
you were talking about your comment
Comment has been collapsed.
Now I just need to wait for all the other games I suck at to get fixed.
Comment has been collapsed.
While I'm not surprised that something like this could go unnoticed by Valve for so long, I'm really shocked that the competitive community never really caught onto this until now. I can understand that it would be difficult to tell in an online match because of lag compensation, but quite a few people analyze frame data so it's strange that such a massive bug wouldn't be better known.
Comment has been collapsed.
There is this group f.e that are trying to spot cheaters, some are about how certain cheaters seem to aim right next to a target but still hit, i wonder if that has something to do with it too and if valve fixed this if in some cases it will get harder to spot certain cheaters. https://www.youtube.com/watch?v=9dFT9pNNGiE
Comment has been collapsed.
37 Comments - Last post 5 minutes ago by GarlicToast
49 Comments - Last post 10 minutes ago by Chris76de
11 Comments - Last post 32 minutes ago by PoeticKatana
154 Comments - Last post 34 minutes ago by LeLecherousLeech
64 Comments - Last post 49 minutes ago by ZPE
349 Comments - Last post 51 minutes ago by Vasharal
213 Comments - Last post 2 hours ago by possom2009
97 Comments - Last post 16 seconds ago by coleypollockfilet
24 Comments - Last post 2 minutes ago by DeliberateTaco
2,205 Comments - Last post 7 minutes ago by LeLecherousLeech
98 Comments - Last post 8 minutes ago by s4k1s
546 Comments - Last post 9 minutes ago by sirnathaniel
12 Comments - Last post 19 minutes ago by lext
6,340 Comments - Last post 25 minutes ago by arafijb
Maybe depending on your class. Afer 10 years they fixed this particular bug.
"Video games with a dedicated developer team periodically release software patches to fix broken things. Sometimes these come at the behest of the title's community, and dedicated users can be counted on to pick apart janky or erratic flaws faster than developers can address them. Unless everyone misses something for, say, a decade. That's how long a particular bug had been in the shooter Team Fortress 2 -- since it was released in 2007 -- if a pair of modders are to believed, an issue that studio Valve finally fixed in yesterday's game update.
The phenomenon would've flown under history's radar if Reddit user sigsegv hadn't called attention to a particular fix nestled in this recent patch's unusually dense list of addressed issues. In a comment, sigsegv pointed out that he'd reported this bug to Valve after a developer of the TF2 Classic mod, Nicknine, first exposed the issue in a video a few weeks ago and claimed it had been in the game since its original release. sigsegv__ made his own video exploring its severity:
To explain the bug simply, if someone started the game as one of three particular classes and then shifted to any of the six others, their character would have one set of hitboxes and the server would register a slightly different one to other players. The mismatch between animated model and actual hittable zones means a decent amount of shots taken over the game's ten-year lifespan were likely near-misses when they should've been hits, assuaging the ego of anyone who swore they'd gotten that sweet headshot that one time.
Fixing it was as simple as changing one line of code, sigsegv__ claims in the Reddit comment, but knowing which line and where was the real trick. We've reached out to both modders and Valve, and will update when we know more about the bug. For now, rest easy that your shots are slightly more accurate and a long-overlooked wrong has been righted."
https://www.engadget.com/2017/02/15/team-fortress-2-patch-fixes-decade-old-bug/
Comment has been collapsed.