There are way to many “bugs” posts here. I would suggest that before create a “bugs” post that you actually try a bit of “coding” for yourself. You may be slightly amazed at how complicated even the shortest bit of software coding can be. You also seem to lack the knowledge of how expensive programming can be. Programmers do not come cheap. Even off shore and out sourced programmers are incredibly expensive for a company.
You are also blissfully unaware of the multitude of “bugs” that you don’t even notice. Just remember for every bug you complain about there are hundreds of bugs that you can’t even comprehend or even notice. This is the nature of software.
Also keep in mind that the game will be long forgotten and uninstalled from your computer well before “all” the bugs are ever/never fixed.
Bug reporting is important for players and developers but bug complaining is mostly a waste of time for all involved.
Right extremely hard to fix = ignore reins shatter and charge for 2+ years. Gotcha.
I disagree. If there are many reports, reports that are currently being handled may end up on the back-burner, because of other, more pressing issues, or outright forgotten for whatever reason. Complaining about them is a way of ensuring it stays on a developer’s radar. Sure, you can take this too far, but if that’s the case, then the developer should just come out and say what they’re currently working on, so people know what to stop complaining about, as it’ll likely end up in the next patch.
Being a developer myself, I, too, am guilty of this from time to time, and while people asking for a status update can be annoying if you were working on something else at the time, it’s still a reminder telling you, “Hey, they’re waiting for this thing you started working on a while back. Maybe prioritize this once you’re done with what you’re currently working on?”
And that brings me to problem #1 with Blizzard; they hardly, if at all, communicate with us. You post a bug report, and 99 out of 100 times, you don’t even know whether they’re looking at it or working on it. If they’d start getting more involved, especially when it’s about bug reports, that’d go a long way to improving the general mood here on the forums.
But all they do, is answer random questions about Torb’s sleeping habits or whatever other garbage, instead of the more important stuff.
Also, quite hilariously, your username prevents me from quoting you directly, because it contains a certain 4-letter word
It’s funny when people say this, because if you look down the dev tracker, they do discuss the important stuff, or at least people’s questions. They don’t talk about the complicated stuff because it just annoys more people. (Mercy is fine, anyone?)
Hardly. Pretty much the only developer who does that, is David Adams, the Principal Level Designer. And even he doesn’t always respond to map-related issues. Specifically, David Adams is around when they’re about to put out a new map, like with the release of Rialto and now Busan. Anything else is pretty much radio silence.
And only recently did we get some from Jeff Kaplan, who doesn’t really tend to talk about pressing matters, either. I mean, we got no response, whatsoever to Reinhardt being broken AF since the previous patch. Only through PTR patch notes did we learn he’s being looked at. What BS is this?
The same thing goes for highly upvoted hero balance concerns. Why aren’t they being addressed? A simple yes or no and a short explanation of why is sufficient. No need to write an entire essay about it. But, apparently, that, too, is too much of an effort. Instead, Blizzard seems all too happy to help grow the toxicity they claim to be fixing.
Yes, and while most of the time, the bugs are bad, if they’re difficult to reproduce in a normal environment(like out of map glitches that rely on the projectile speed of Sombra’s translocator being at 500% or the D. Va mech duplication glitch) or something that’s harmless, where is there a problem with keeping it in? When I found out about the glitches I mentioned, I had fun showing them to my friends and just screwing around in custom games. But if it’s the numerous Rein and Doomfist bugs, those are problems that should be fixed, not an out of map glitch that can only be done in custom games, it’s fun to explore the maps other than what you can see, like the guests walking around BlizzardWorld in the distance are just holograms of Soldier in various colors
I don’t think anyone here has implied coding is easy? Programming is super hard; it’s a language in of itself. But I have personally not seen anyone claim “it’s easy so it should be easy for you all to fix it.”
Most of these bugs are already on the Bug Report forums, and I’ve also seen a lot of them also on Reddit. I really don’t see the issue with people complaining and posting about bugs that are breaking heroes; we paid for a working product. I think any logical person knows that every game has kinks, and every gamer is used to games having their issues.
But D.Va getting launched through the map when she de-mechs, Reinhardt’s Earthshatters going through people and not affecting anyone, are all issues that need to be fixed. If you’re going to have an eLeague video game, I think it’s pretty standard to expect things to work well enough to not cause a team to lose because Reinhardt’s shield randomly decided to not block an enemy’s Earthshatter.
It becomes so much easier when people provide video evidence or a step-by-step, and even those aren’t being picked up. Take, for example, the Doomfist bugs. Most of 'em have videos showing how the bugs have been found, yet we hear in an interview with Jeff Kaplan somewhere down the line that they weren’t even aware he had bugs. Like, do they even read these forums?
Hate to break it to you, but they’ve addressed both of these several times in the past. However constant changes to the game either broke them again or reverted them.
- Feb of 2017 had pin bug fixes
- May of 2017 had Earthshatter changes/fixes
- July of 2017 had more pin bug fixes
- Jan 9 of 2018 had more pin bug fixes
- Feb. of 2018 had more pin bug fixes
- March of 2018 had more pin bug fixes
- April of 2018 had Earthshatter bug fixes
Except. Nothing got actually fixed.
Until now.
…
Am I the only one remembering the calls to FIRE people over dev responses to balancing concerns. The D.Va debacle and “Mercy is fine” come to mind.
No, they got fixed. They just broke again when changes happened to the game. Changes to the engine, other heroes, maps, etc. broke whatever changes or introduced new bugs.
Code isn’t so simple as, “Oh thats supposed to be a 2 but its a 1, lemme fix that real quick,” its more like, “Okay what the heck change to Sombra broke Rein and how!?”
Knowing there is a bug and finding what is causing the bug are two different jobs entirely with two vastly different work loads.
Then it ain’t fixed. When you change code, you test for regressions. If you don’t, you might as well consider the original bug to be unresolved.
Sometimes, it is. Off-by-one errors do happen, you know? More than you think.
Reeks of sloppy coding. Changes to hero A should never affect any other hero, aside from game balance. As soon as changes to hero A break another hero, there’s gotta be some talking during the next meeting, because someone clearly forgot about the coding guidelines.
For most of the code I work on, I can pretty accurately predict the effect of any given change, and I always test my changes personally, before I hand the thing over to other people for further testing and eventual deployment. Very rarely do I see anything back for further fixing, and when it does come back, it’s usually a minor thing that’s fixed in a few minutes, at most.
Isn’t even a job. That’s just someone submitting a bug report. Just reading through one should be a clear indicator something’s up, and if not, you reply to the report and ask for more info. Blizzard normally doesn’t do any of these things, outside of the cases I mentioned earlier.
Right. And then they came out and said that the problem has been in rein having faulty coding from the beginning. So I’m assuming everything you just shared with me were band aides. I’m not one of people around here that rag on blizzard but to say the bugs arnt getting out of hand is just wrong. The only two heros I “main” have consistent bugs I have to continuously play around each time I play. And hard or not theres no excuse for a multibillion dollar company to let these problems persist for so long. I understand loads of bugs are literally always going to be around it’s in the nature of a game that changes as frequently as this. but lots of them have been around since launch and alot more are bugs people have to actively play around to play the heros they like. Theres no excuse for that.
funny how gamebreaking bugs gets fixed right away while smaller ones never gets fixed
its not because its too hard or its too expensive