This bug here has been an issue for past 3 years, has never been fixed, no blizzard reply/GM confirmation. How can you just IGNORE a gamebreaking bug that prevents us from using our character?
I got stuck on Caverns of Time flightmaster 3 months ago, again few weeks ago, now Dalaran Northrend stuck. This is absurd, and ridiculous.
If you feel that something is still bugged, you’ll want to be sure to inform the QA team by posting in the Bug report forums or by using the in-game suggestion feature.
Neither the CS forums nor the GM team has anything to do with fixing bugs. That’s left up to the QA team and the developers.
Lastly, it may very well be a bug that’s so rare that it’s difficult to track down and squish.
It’s actually been around since Wrath was the current expansion, much longer than 3 years.
You don’t know if that’s true. Bugs get fixed a lot, and sometimes, the fix doesn’t work as well as intended. Or a different change can undo the fix.
Bugs can be complicated. Sometimes, they are not easy to handle.
This bug is neither gamebreaking, nor does it prevent you from using your character. You may have to relog to reset the character, but that is not gamebreaking.
That said, bugs are triaged. What is affecting the most people, most often is generally moved to the frontlines. A bug that affects a few people every few weeks could be put on the back burner for something more widespread, and more current.
While I understand your frustration, Retallica, fixing potential bugs is a great deal more complicated than you seem to think. That a reported issue hasn’t been resolved yet is in no way an indication that it is being ignored or that we refuse to find a resolution.
Knowing about a potential bug doesn’t also include a fix. There is an often long process involved to investigate the reports we receive, look for a possible resolution, test that resolution and finally implement that resolution.
Yes, there are some situations in which our QA and Dev team can look at a bug and guess what may be causing it, allowing for a faster resolution, but many bugs don’t work like that. Some bugs are extremely difficult to investigate based on how they present themselves.
In most situations, the QA team must be able to verify the bug, which means being able to reproduce it themselves. Can you get stuck on the flight path reliably? Or does it just happen once in a while with no real means to predict it? That’s often the challenge, that unpredictability for when something like that shows up.
If you are able to reproduce the bug, then you need to figure out what may be causing it, then figure out an appropriate resolution that doesn’t impact any other system. Testing those resolutions and finally implementing them to live.
It is also important to note that many of these issues are actually related to a connection or UI issue and it is important to take that into consideration as well.
The best way to help with this process is to submit a bug report when it happens. If you can use the in-game tool on the character experiencing it that can provide a lot more data.
I wouldn’t be assuming it is a bug, OP. This issue is generally caused by faulty addons, connection issues, or other things. You should first try a UI reset following these instructions https://us.battle.net/support/en/article/7549 and see if it still happens. If that doesn’t help, then you can restore your UI by putting the folders back, and then investigate your connection by posting over in technical support to see if they can come up with anything.
“Game-Breaking” is a loaded term.
Most software organizations use a Change Management System to categorize and prioritize bugs. Game-Breaking means no forward progress is possible.
For this particular issue, there is a work-around available to allow gameplay. The Unstick self-help facility is available both in the game help menu and on the web site
this was my thought as well. Especially since I have never not once experienced it. Kind of like the naked toon that did not have their account compromised bug that has been ever so elusive for many years as well.