Mechagon Island, can t drop combat

Seriously this is really ****ing me off so hard right now. Missing on being able to reach rares on time etc. Only way is to hearth back.

Can t you have a simple distance check? Walking the whole island up to fatigue doesn t help nothing work but hearthing and since not a night elf that doesn t help.

Sidenotes sometimes also mobs stick to you for half the length of the map and since the last patch = drop your aggro on anybody for the lolz this also makes it rather annoying to try to get out of combat.

Rant over

4 Likes

From the WoW support article:

" To remove yourself from combat, we recommend the following:

  1. Use any class abilities which force you out of combat
  • Example - Rogue’s Vanish, Hunter’s Feign Death, Mage’s Invisibility
  1. Try using your hearthstone
  2. Close the game client for 5-10 minutes

If you notice that your character is stuck in combat often, reset the user interface. If the issue persists, contact us."

But no, it could be handled better.

This bug is ancient and has plagued this game long before mechagon showed up.

Its those damn murlocs fighting mechagnomes near the area where Seaspit spawns. They are forever engaged fighting eachother, but they are also never capable of killing the other without the player’s influence.

If you get too close to one of them, but don’t cause enough aggro to make them attack you directly they just keep fighting eachother while also locking you in their little feud for all eternity.

There are many ways to unbug yourself. My favorite is to slaughter those gnomes and murlocs until the bug goes away.

2 Likes

When this has happenex to me i just swim out towards drustvar. Eventually you leave the mechegon area and combat drops. Then you just fly back.

I occasionally run into this problem IN EVERY ZONE. I have not experienced it more in Mechagon. As someone said, this bug is ancient.

The game is imperfect. If you get angry because of that, you need to find a better game. Your anger isn’t going to turn this into a perfect game program.

Today I had the opposite problem. I couldn’t get IN combat mode. A rare was announced, in the ocean. So I flew there in a jetpack. But I couldn’t fire (range attack) while flying, and I couldn’t exit the jetpack over water. Finally I flew to shore, “landed” and swam back to the rare, losing 30 seconds on a rapidly-dying rare.

“stuck in combat” is a bug dating back to at the very least Wrath. That’s my oldest memory of it being an issue.

Blizzard has made many changes over the years trying to eradicate it. One of the bugs was totems would keep groups in combat if there was a shaman in the party. So they retooled totems.

The list of changes they’ve made is huge and yet they still can’t fix it.

Makes me think its part of the core engine. While engines may be modified, upgraded and tweaked over time, there is only so much you can alter before you run into the limitations of the very ‘root’.

Bethesda suffers from that with the engine they use. No matter how much they tweak and modify the core engine, there are flaws at the very root of the engine all their programs work around.

Maybe they should change how you getting put in combat works. Why should I be put into combat because something else is fighting near me? I did not aggro it, I am not fighting it, so why should I be put into combat with it? Seems to me I shouldn’t be.