Instance not found, Sudden Death, killed by server in Hardcore

So the situation is simple, for about 2 weeks I got from time to time regular problems while zoning, or teleporting like

  • world server is down
  • instance not found
    arriving on a zone, there is no mobs, and I’m pushed back to where I was before zoning.

Here Comes Hardcore realm. I give it a try, and just finished the alliance druid’s quest with a dedicated Alt character.
Bear’s quest in sight, I Just defeated Lunarclaw and Teleport to Moonglade, wanting to take the flight from Moonglade to Theldrasil.
Here comes the pain:

  • Teleport to Moonglade
  • Loading screen pops, and do not load, the loading bar remains empty
  • I kill wow,
  • Still at Lunarclaw cavern
  • Teleport to Moonglade
  • Wow client crash
  • Relaunch Wow
  • Teleport to Moonglade
  • Wow client crash
  • Still at Lunarclaw cavern
  • Teleport to Moonglade
  • Everything in order
  • [SERVER] Shut down in 15 min.
  • Take the hippogryph
  • The harbor of Theldrasil is in sight.
  • [SERVER] Shut down in 11 min.
  • Transfer Aborted: Instance not found
  • Char pops high in the air between Moonglade and Darkshores and fall down
  • You have died. Your deeds of heroism will be remembered

I need a rollback on that, since it’s independent from the bestiary or a normal game experience but from your network provider’s technical failure.

Read the blurb you get when you make your character on Hardcore. No backsies.

Any death is a permanent death.

1 Like

Hi there Espritduvent,

I’m sorry to hear about this – definitely not a great way to go.

That said, as mentioned in the warning Dottie linked, dead HC characters will not be revived or rolled back for any reason.

I hope you’re not too discouraged to give hardcore another try, and wish you the best of luck whichever version you choose to adventure on next!

1 Like

It’s faulty on your side.
nevermind, I rolled to help a friend and heal him. He will not have my support because of your failure.

Fix your network responsible of those failures btw, as I experience it as well on DF and it’s now regular.

6. ae1-br01-eqld5.as57976.net                                              9.1%   788   44.4 222.528.39311. 922.4
7. (waiting for reply)
8. et-0-0-5-br01-eqam3.blizzardonline.net                                 13.7%   787  164.1 351.725.79710. 1389.

PS: You got a Typo at “seRver outages”

None of that is relevant. Dottie posted the Terms of Service YOU agreed to before you started playing.

Do you always agree to things you don’t actually mean?

Dead characters will not be restored, wherever the fault may lie.

I just checked in-game, and it appears to be spelled correctly.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.