Dauntless Delver after being disconnected?

5 replies [Last post]
Notbob's picture
Notbob

Random disconnects from the game seem to be a fact of life around here, but do they matter if they happen during a Dauntless Delver run? If you're disconnected and log back in right away, returning to the same spot, can you still get the achievement? This is the situation where you're not logged off according to any friend/guild notices.

We tried asking in a support request if this would ruin the achievement, and were helpfully (?) told "it's possible", essentially "I don't know".

So, SK hive mind, does anyone have a definite answer to this issue? Has anyone been disconnected mid-run, reconnected, and still gotten the achievement?

Thanks.

Dogrock's picture
Dogrock
While this has not happened

While this has not happened to me, I would assume that if you manage to log back into that same instance (not ending up in Haven) it should still count. Much like how if you disconnect in a boss stratum you do not take a Token reward penalty if your game reconnects without issue.

(This is also assuming monsters don't mob and kill your poor disconnected body somehow)

Notbob's picture
Notbob
still awarded

Just as a follow-up, in case this happens to anyone else in the future, the achievement was still awarded, even after three disconnects/immediate re-logins.

So, not everything is designed against us. :)

kbe2k11
Legacy Username
Yea it doesn't ruin the

Yea it doesn't ruin the achievement on my dauntless run I waited a few times for certain floors and because of that got DC when I took the elevator and didn't screw up anything though I was a bit worried, takes around 3hrs to do dauntless at least solo it took that long I'd hate of lost that due to a DC.

Tipiak's picture
Tipiak
Well, congrats to P. then ;-)

Well, congrats to P. then ;-)

GamerTB
Legacy Username
(This is also assuming

(This is also assuming monsters don't mob and kill your poor disconnected body somehow)

Bloody hell, it happens to me so many times it's not funny in the slightest. I can't be the only one who has this damned ialmrnt.dll problem.