Would be kind of nice to see more blue responses in the bug report forum.
I just wish they would say SOMETHING about how their bad implementation of batching has effected a multitude of things. Its a backend issue causing classes to not act as vanilla intended.
Vanish is currently in a state of bad.
Pets are currently in a state of bad.
Hunter FD - bad.
Pyroclasm proc - bad.
many many more.
Is it too much to ask for a little more PR in the bug report forum??
Valid (and ofc invalid) bug reports are posted dozens of times a day and all we get is a lame reply that tells us essentially nothing.
Too bad the streamer folks were used to hype the classic release instead of using others that care more about accurate mechanics.
And what would you have them say, exactly, beyond that they’re looking into it?
Anyone who has ever tried their hand at writing (and debugging) code can tell you that you just don’t snap your fingers and suddenly it is all fixed. You have to first track down where the problem is, which can be an adventure all on its own, figure out WHY the problem is occurring, and then attempt a fix. Then, you have to test that fix, because in fixing that bug, you’ve probably caused three other bugs to pop up, which you have to find and fix before sending the patch live.
< singing > 99 little bugs in the code. 99 little bugs in the code.
It would be nice to see them acknowledge that it is indeed the spell batching backend that is causing this issue globally, or that it is something different that is individual to each issue. That would make me feel better.
I dont expect immediate fixes
I just want them to say - yes we are aware ,xyz or no, not a bug - reference. Maybe 1 blue post every 3 days? donno is that too much to ask? It could be - I don’t write code.
That’s the thing, though. They might not know what is causing it yet. It is like trying to diagnose a problem with a 747 with nothing more than someone saying they heard a noise somewhere while it was flying. You know in Jurassic Park where they decided it was easier to turn everything and reboot from a backup instead of trying to find the command in a few million lines of code? That’s what we’re talking about here. They could probably get the issues fixed in a couple weeks if they shut everything down. That obviously isn’t a viable option, so it will take longer.
1 every three days would be asking too much. 1 a month would be better.
I’m a former dev. Has any reporting player given Blizzard enough detailed information that devs can reproduce this problem on their own systems? Not a vague comment and “try it for 100 hours”, but an exact approach that makes the problem happen over and over?
That is step 1 of finding the bug. Then a dev has to test it enough to agree with you that it is “bugged” behavior. Then he starts searching a million (or more) lines of code, looking for the problem. Out of 225 devs, there may be 1 or 2 that know this part of the code. Are those 2 devs free now? Is this bug their highest priority task?
Saying “it is indeed the spell batching backend that is causing this issue globally” is around step 20. And step 23 is putting out a fix. So nobody in the bug forum can issue that statement until a lot of research and bug-fixing has happened. About 95% of it. Usually fixing a bug is not much work: finding the cause takes most of the time.
It is there so that players can report bugs to Blizzard. The players provide as much detail as possible, in the bug report. Every thread is a request for Blizzard to “put this on your long list of bugs, and work on it”. Every post is “here is some info about this bug, to help you make it happen, find it, fix it”.
Blizzard has people who run their bug-lists. Those people monitor the bug report forum, and use it to add bugs to their list. Someone (same or different person) also sorts bugs by priority, urgency. Someone (same or different person) also sorts bugs by “which dev or dev group knows about this part of the code?” and assigns the bug to the correct dev or group.
In my experience, a bug may get looked at by one group, who figures out it is in another groups code and transfers it. But it stays on the bug list, and keeps its priority.
The GD forum is player-to-player. Complaints there don’t get put on the bug list. Blizzard is not required to monitor the GD forum for bugs, or to respond to any posts there.
It WOULD be nice if they at least updated the known bug list. I mean it’s been 2 months. A little acknowledgement would go a long way. But hey it’s friday night and a blue probably will never see this before it falls into the abyss of weekend troll threads.
This is pretty standard operating procedure for blizzard, been that way for retail for a long time. Don’t address or fix combat related bugs until the content where they heavily impact (pvp for a lot of current things) becomes the main focus, which will be phase2/3 (phase 3 bgs being the main one).
Melee leeway, DRs, Vanish bugs, druid mana drain (and most other druid related issues) aren’t causing enough of an uproar in pve so they’ll ignore it until they cant.
Well and the biggest issue is they gotta be able to reproduce it so they know just exactly what is jacked up. Not to mention in the case of Classic, they gotta make sure it’s an actual bug and not just how it was, which means being able to reproduce it or not on the reference client as well.
It’s just not that easy sometimes, and generally they don’t comment on it until they might have a solution.
This might be a good idea. Telling players about ALL the known bugs (and ALL the known it-is-not-a-bug’s) might be helpful.
On the other hand, it might just cause more complaining. Many smart people (who never worked on big software teams) think:
[1] good programmars create bug-free software
[2] bugs are easy to find and fix
The reality: find a typo in a 2-million-word novel that somebody else wrote. THAT is bug-fixing.
Another issue: what if one player claims there is a bug, but devs can’t reproduce it (make it happen)? Is that a bug or just a rumor? Of course I work on it, but do I tell 3 million players about it, or wait until it has been confirmed (by a dev or tester making it happen)?
So I think Blizz could inform players better, but I see problems.
Please do not ask for a Blizzard/Blue response in your posts.
Not getting a Blizzard/Blue reply does not mean that your issue is or is not a bug, and it does not mean that your post has been ignored. We read every single post in this forum. We cannot reply to all (or even most) threads.
Bug reports is not a back-and-forth discussion in most cases. The goal is to provide as complete information as possible about what is suspected to be a bug, and only if they have an explicit question or answer will Blizzard tend to respond.
Also, Kaivax does seem to be keeping the “Not a Bug” list updated, even if the Known Issues sticky seems woefully out-of-date
I’ve posted a pretty major bug that is currently being exploited and it has received no attention as of yet. It would be nice if they just had one person at least monitoring the forum.
