Either way though, I agree that it’s bad, but this is extremely common for Blizzard. They leave things broken all the time, especially when it comes to old content features. The miners in garrisons, for instance, still have a bug where they spam the gold coin sound effect in the middle of the garrison over and over and most likely bugs like this will never be fixed because Blizzard simply doesn’t care.
While focusing on bigger issues first is certainly the correct choice to make, after a while it becomes obvious they have no intention to ever touch the problem and leave things broken literally forever.
All of this said I think a post like this is really unnecessary. If you want to bring attention to the topic that’s good thing (and please provide links for us so we have context) but coming off the way you are just feels sarcastic or passive aggressive and certainly isn’t going to get Blizzard’s attention sadly.
…At the same time though, there really isn’t literally anything that will so there’s no reason not to do this I guess, so who am I to judge?
My idea messes with nothing, it simply tells the game to list whatever I am in combat with so i can do something about it. The game knows something is in combat with me, so let me know as well. something like a red dot on my minimap so if i mouse over it iʻll know "Oh that random grasshopper off to my left is whats got me in combat. proceed to oneshot and get out of combat
I responded specifically to the whole “But it should be easy to fix”, I even mentioned that in a situation like with this particular bug all you can do is treat the symptoms of it (I mentioned how they fix problematic abilities when they start doing it on the regular, you mention bringing in a system to solve it; they both do the same thing, treat the underlying symptom of the problem)
I wasn’t speaking out against your idea, and if anything I spoke in support of it
The music at the Citadel of Loyalty in Bastion plays the first 300ms then resets and repeats rapidly ever since 9.1. Really wish they hadn’t left that, I bug reported on it every month for years. It makes the experience of an otherwise really nice zone horrible.
I’m still convinced that it’s not a bug.
I’ve played all classes, and never experienced it.
I notice instantly if I’m in combat.
If I look around, I can always find what I’m in combat with, and kill it.
It’s either:
a critter which is running around like a maniac, needing to be put out of its misery
a sleeping mob which i got too close to
some npcs which are fighting
aoe’d near a target dummy
a mob stuck under the ground (yes, this one is a bug, report it)
Beyond those situations, I’ve never been in combat with “nothing”.
When people claim to have experienced this “bug”, they never want to go into details of exactly where they were, or what they were doing.
Nobody seems to be able to provide video of it happening.
The specific bug I am talking about is legacy raids glitching out and being unable to be finished. Doors that need to unlock upon boss kill are not unlocking, making completion impossible.
Edit:
Also as someone who has played a rogue variously on and off, as well as druid for several years at a time, there is a bug where if you kill a mob instantly from stealth they still get a free autoattack on you, which is weird.
Finally, your statement that you say that the vanish bug doesn’t exist for you just sounds to me like you are lucky and don’t get to experience it. Your positive experience doesn’t mean it never happens. I remember back in legion when I would randomly get teleported to the middle of nowhere in Azsuna when using the warrior “flight path” thing where you jump up to and down from the order hall. No matter where I selected to go, it would deposit me about 200 feet in the air in some random spot in Azsuna. Many warriors claimed this never happened to them, just because it didnt happen for them doesn’t mean it didn’t exist. And while I doubt it’s the case, if you’re claiming people are lying about bugs then… I don’t know what to say about that.
Bleh, just like that pink spider Shadowstalker in the house by the undead starting area, the spider is stuck in the fireplace, been like that for 5 years, went by that the other day helping a new guildie, spider is still stuck. you would have thought by now after 5 years, they would have fixed it, right, must be to simple.
The thread I am referencing specifically is for Siege of Orgrimmar, after you kill the iron juggernaut, sometimes the doors dont open. Happens often enough that people keep updating the thread every couple months.
can I ask what about this is common sense? How would knowing this information be common thing to know?
common sense would be something like seeing cars fly across a highway at 70+ MPH and having the sense to not run across, if you needed across, and finding some other way.
common sense would not be knowing some obscure information about how video games work to know that if you kill amonster too fast the game will break, just trying to understand where the commonness of that knowledge comes from.
If you look at the patch notes for patch 1.1.0, from Nov 7, 2004, you will see a note saying “Blink should work much more reliably”, and let me tell you, to this day it still doesnt.
to be fair, people will still attempt to wander into traffic just because they expect vehicles to stop.
it’s not exactly obscure though… is it.
fights have mechanics.
many of those fights have phases.
these are raids, not dungeon bosses which can be brute-forced when you’re double their level.
mechanics don’t all disappear just because a player is higher level.
if someone has been playing the game for more than a month or two, they should know to go to wowhead for anything they’re unsure about.
it will explain any required mechanics.
comments will note if a scripted fight needs to be allowed to fully play out.
but as i already noted, there will always be those people who expect the traffic to stop for them.
my dumb head still attempts to blink in the WSG tunnel.
Personally I think there is a bug, but its associated with how NPCs get stuck in combat and won’t either evade back to their original position or something else akin to that
But you are right in that its not a bug because its code not working as intended but more like things interacting in a way that keeps you stuck in combat (the Fyrakk Assaults are a great example of this where folks get in combat with the NPCs fighting other NPCs and that’s a brilliant way to summarise it)
But you are right though that the whole “stuck in combat” bug aspect is in neigh on every example someone not understanding how aggro works (and also why trying to fix or change this so it wouldn’t be a thing anymore would be neigh on impossible, ergo why the whole ‘treat the symptom’ aspect)
Good for you
I still doubt you because you said “Vanish has always been broken and its been like this for almost 20 years”, despite updates and changes to how the game works
Somehow I don’t really trust someone’s take if they say “It was always broke and they never got around to fixing it” when it comes to things that should have explicit examples of it in that case
You just saying “20 years, still bugged” indicates a bad faith talking point, or that you don’t understand how Vanish is supposed to work and is attributing an intended function of it as unintentional, such as this!
The only time a mob doesn’t get an automatic auto attack on you is if you start off by stunning them - getting an “instant-kill” doesn’t really exist in terms of coding because everything happens, for all intent and purposes, simultanously when computing the code
Bugs can happen to anyone and I don’t doubt that you experienced your flying warrior, I have experienced bugs that were too fringe to figure out what had happened and I couldn’t recreate them so I had no idea how to report 'em so these bugs do happen
But… again, if you are saying “This has been bugged for 20 years and somehow never got fixed or was even ever popularly mentioned in memes or videos” … allow me to disbelieve that person’s take on it
