Can someone from Blizz notify me with reaction or in any way that they saw bugs i have reported?
It started again with frequent bugs affecting my gameplay. I have new bugs and still no one reacted. Why are they producing so many bugs?
Can someone from Blizz notify me with reaction or in any way that they saw bugs i have reported?
It started again with frequent bugs affecting my gameplay. I have new bugs and still no one reacted. Why are they producing so many bugs?
Bugs happen during development, that’s a thing. From all the games I know, there’s not much that do not have any bug at all. The more you develop, the more bugs you will have, regardless of how many devs you have and how good they are.
Blizzard doesn’t seem to react to any bug report on the forum, at least directly by replying to the topics. But a lot of bug they fix have been seen at one point on the forum. I don’t know if they use external sources to know about bugs but a lot of them seen here eventually get fixed.
People are too impatient when it comes to bug fixing. Sure you can develop a fix and quickly drop it in production (live) environment, but’s that’s a bad habit. If you don’t do a minimum of proper testing, the more you just drop untested fixes,the more bugs you risk to add
I know people are always saying that it’s unacceptable from such a “big company with so much money” but they don’t know what they are talking about.
On the opposite sid eof the spectrum, the bank I work for has some serious bugs in its billing system. Sometimes we, or the over teams, develop the fix in 1 or 2 days. But for some internal political reasons, we are not allowed to push that fix on upper environments for testing, and even less in production to apply the fix.
Those bugs can cost thousands of € per day, just because of the time wasted in workarounds. Not even talking about the damage to reputation the application suffers in front of the users, and the damage the bank suffers in front of its customers. But some random guy in the hierarchy didn’t want us to fix because “bugfix testing was not in the schedule of that release”
At least in my job the main users of the application are well aware of the situation and are comprehensive.
I think I went completely off-topic but I was on a roll. Maybe some would learn something from that. The others are free to ignore.
No, because if they did it for you, they’d have to do it for everyone, and ain’t nobody got time for that.
Sure there are bugs in other games, but not at this rate and they fix their bugs!
They do not react to bug reports, i believe they do not read this thread and they are not fixing bugs!
I can be patient. I am reporting some bugs for 2 years and i had them before that. Fine, they need more time, but can someone tell me if i have to wait for 2 more years or what is the average time to resolve some simple bugs?
Hard to compare rate when we don’t really know what workload represent all the updates we have and how it is split between developpers.
How many devs are working on an update ? How challenging is the update for the Hearthstone engine ? They are implementing brand new mechanics in the game each expansion. That’s a challenge to some points.
There are also games that are way more bugged than hearthstone. Even some that you have to pay for in the very first place.
Not all games. Not all bugs. And certainly not instantly.
Skyrim is more than 10 years old. The game had multiple DLCs and re-editions, and still has some game breaking bugs.
League of Legends introduces tons of bugs each patch. Worse than hearthstone they introduce bugs that they fixed by the past.
Minecraft has a proper bug report system where devs flag tickets to indicate what’s going on. Some bug tickets have been at “to be fixed” for years now.
Warframe has a ton of bugs, just need to see how long their patchnotes are.
One of my favorite games, now dead, had some game breaking bugs that were never fixed and became actual huge gameplay mechanics
They could, it would be nice. But then it would require to dedicate a person to specifically reply to every single post on the forum and if they dare to forget or ignore a single one, people will enter full guerilla mode to have their reply.
Just in the last pacth I saw multiple bugs that have been reported on this forum being fixed. I don’t know if they have external source to check on bugs but I assume they read us at some point.
I’m not checking your reports but I can already tell that bug reports such as “car didn’t work, fix pls”, that are really present on the forum, are pretty useless and won’t help to fix a bug.
A propper report needs a propper test case. Best case scneario you found a reliable way to trigger the bug. The least being to indicate which other cards or effects were in play at the time of the bug.
And a bug may be simple, but it may also not be on the priority list.
Devs are not the omnipotent deciders of everything too. I hate when people just blame “devs” when there are way more people than just them in play. If the wiki is to be trusted there’s more than a 100 developpers on the game. I can guarantee you that when you blame “devs” for their decisions, at least half of them just do what they are told.
All they need to do is update the list of known bugs.
And they do
Just looking at it you can see that last updates are from friday and they include a bunch of stuff reported on the forum
So how long i should wait? What is the average time for resolving pretty simple bugs? Two more years, 10? I would like to know approx time so i know what to do.
An average time to solve a bug is not something any sane support will eer give you because the answer doesn’t exist
I can give you examples from my work :
We have a bug in our waiting list that I am able to solve in literaly few minutes.
But this would require that I modify a very sensitive tool of our application, with repercusions on objects out of the scope of the fix
If the tool were to break because of my change, it could require an entire day to fix it
After fixing it I would have to spend some time to do some unit testing
Once I’m done with the fix I prepare the package to deploy the fix in the othe renvironments (that doesn’t take long)
Once our business analysts team is ready they ask for the fix to be dpeloyed in their testing environments, where it will be verified that the result of the fix is still compliant with our customer’s initial request.
Once they finish testing, they flag the bug to be included in the next release
Once the scope of the next release is validated by some people in the hierarchy of our customer, we can deploy the fix in another environment used by another team for non regression testing
Honestly these guys are not the most effective at testing, to say the least. They don’t understand how the app is supposed to work because they never read the documentation, never listen during presentations and have an gigantic issue about knowledge transfer when people quit their job. But at least they have timeline to respect, so even if they’re slow, eventually they’ll do their test and flag the bug as ok to be deployed further.
Once that full release is tested in their environment, rince and repeat another time for yet another environment of testing run by sloth.
And when this environment is done, finally comes the production update where we can deliver the bugfix to the production environment.
This is when the hierarchy accepts that the bug will be fixed in the first place. Because all the above worktime costs money. So they need a comparison of “what’s the impact of the bug ?” - “How much will it cost to fix it ?” “What’s the risk of added bugs by the fix?”
If the impact of the bug is too small compared to the cost, it won’t be fixed.
For this peculiar scenario, we usually wait for a big change request of the tool (about 1 or 2 per year) and we slide the bugfix in to reduce its cost, as it will be deployed and tested alongside the change request.
But we also have some bugs that have really minimal impact for gianormous costs and that we can’t slide in any bigger topic. This is actually our “Know issues” list of bugs we acknowledged but can’t deploy a fix for.
tl;dr : Good devs want to get rid of bugs and sometimes could in short delays. But cost management and intern political reasons will delay or even deny them to do so because that doesn’t fit their schedule.
Ok, let me ask this way. Do you think 2 years is some reasonable time (bug not yet fixed)?
Need more context
What is the bug ? How many players are impacted ?
Is it in a game mechanic ? A card ? A functionnality out of any game mode ?
What would be the implications of fixing it ? Revamping a whole mechanic ? Just a slight adjustment ? Will it require the implication of all translation teams ? Will it take long to test ?
Will they have the allocated budget for that ?
Depending of the answer to these questions, which most of them we can’t provide, yes it could even be reasonable to never fix this bug.
good luck getting any answers
he never posts any details and claim asking all the questions you posted is “Trolling”
he spams this forums with thread like this one or
that one below
Here we go again. You came to yet another of my posts asking the same thing, when i give you all the info you just ignore it and wait for another. You really do not have any better thing to do but to troll other ppls posts?
Please tell me i did not answer and give you detailed description every time you trolled like this? Just answer me this please.