Impaled, unable to do anything, even to log out, you got to kill the client… What kind of retarded game design has it necessary to KILL the Windows Process (the game client) in order to continue playing with another character maybe, while the game decides in its own time what to do with the impaled character.
(PS I suppose you can also disconnect the internet to force the client into an error, which is very similar to killing the client).
As a suggestion there should be an option, “Leave instance” or “Hearth to Base” or “Travel to Nearest Flight Point”, to get you out of an impossible situation like this one or similar, eg stuck in combat etc
Well, obviously not this Warlock which I did not even know I had and the forum seemed to have randomly picked when I was posting the message.
More to the point however, how can this mature game still have unacceptable bugs like these where you lose control of your character for > 15 mins or how long it took to get kicked out of the dungeon and AFTER I had to KILL the WoW client?
Can we please suggest a “PORT ME HOME” basic ability ?
It’s not a bug? It’s a mechanic of the fight where other people would break you out. You simply don’t do enough damage to kill him before mechanics kick in so I’d suggest getting better gear/level
I didn’t think that it was going to be a level 23 Warlock no, which is why I asked what level are you attempting to do the boss on. It’s been easy to solo content for a considerable amount of time without getting to that stage of the fight.
Being impaled is not something that happens every day.
Breath, and take some time to enjoy the moment.
OK, you’re impaled so I’m guessing you can’t really breath.
Blink, and take some time to enjoy the moment.
Because it’s an evolving game. They update not only the game but the content consistently. In a game as complicated (under the hood) as WoW when you change one thing you might inadvertently change another long forgotten thing in a past encounter. This may have happened. What is important is that Blizzard fix it promptly.
With regard to disconnects, I have to say that this also annoys me but…
The internet was not designed for real time communication but to eventually get there so some games try to reconnect (most of the time unsuccessfully.)
there’s also reason to prevent cheating. let’s say you were in an arena match and were just about to lose. Pull the cord and disconnect and survive unbeaten.
Yes, being impaled by Lord Marrowgar and losing control of the game client is not a very common problem, that is true. Like being stuck in combat for ever; not very common, but it happens.
For an MVP you are doing a very bad job because you are not accepting the problem which required me pressing Alt-F4 and terminate the client as the ONLY solution!
Let me give you an example, if I fell through a “hole” in the world (which I have a few times) your answer would be, “do not go there then”. Great advice and help.
Yes, thank you for understanding…
No Sh*t, Sherlock… Actually this was with an ilvl 390 character. Boss cannot kill me, I cannot kill it, I cannot hearth, I cannot log out, I cannot shut the game down, I MUST kill the client or stay like this for ever. When the only resolution to a in-game situation is to kill the client, well, this is a bug.
There must be someone at Blizzard that can understand this…
Well…it’s something they should fix, but it’s gonna be so low on priority it will be another expansion before it’s resolved.
It is working as intended right now so Blizzard will have to go in and break it for people that want to solo it, not something they haven’t done before in other raids but again…it took years for them to do some of the fixes.
And here we have exactly the example I was going on about in another thread. When people can’t find anything better to do that resort to insulting your ability to be an MVP or purely for the colour you post in. I should link this in the ohter thread.
I asked what level the character was because it was relevant. Instead I got a snarky answer about it wasn’t the Warlock that posted the question.
I see you don’t really want to answer any questions about what exactly your issue is but purely be aggressive with anyone who tries to find out any circumstances surrounding the issue you have.
If you fell through a hole and got stuck in an endless loop I would advise you contact Blizzard reporting your character being stuck. I might actually ask for some additional information first. That’s what people do. They don’t blindly assume anything.
Why should you be able to hearthstone when you’re impaled? I can’t HS when I’m stunned by a rogue
Edit: I’m also guessing you must have been trying to heal him to death since you’d oneshot him otherwise and wouldn’t have to deal with impale so here’s a tip: try hitting the boss next time when you start the fight
Dont you just DPS him down before he impales you at that level??
Although ICC does seem to be harder then the other Wrath raids for some reason (by which I mean you dont one shot the bosses and they can take a few seconds to kill).
Tbh i can’t understand how you can’t kill him before he casts the Bone Spike Graveyard…the last time i’ve seen someone impaled by this spell was during WoD and with a very crappy gear.
The patch 7.3.5 scaling had made ICCa little “harder”, but really, if you are truely at 390 ilv you should kill him before it casts the spell even if you forgot to switch your fishing pole with an actual weapon before the fight start.
I was going to write a longer post, but I think it’s sufficient to say that this is a very rare, minor issue and that with some patience it will fix itself. Like you said, force the app to close and wait 15 minutes.
![:slight_smile:](https://d1bg94bbsh66ji.cloudfront.net/en/wow/images/emoji/twitter/slight_smile.png?v=6" ":slight_smile:")