Please change how the Solo Achievement works in Deep Dungeons.

[MajinUltima]

Last week, due to summer, I had a power outage right as I pulled the floor 80 boss in PotD.
I didn't die.
I didn't wipe.
I was in no danger of either, the fight is trivial.
Entire achievement run dead.

About 10 minutes ago, I open a treasure chest on floor 57ish and notice I'm not moving.
Error 90002. Not even on my end, not my ISP, not a blackout, just a common 90002 hiccup.
I log back in as soon as possible.
Entire achievement run dead.

I shouldn't have to fight RNG gods on a combat achievement testing my knowledge, gameplay, etc.
Even if someone could "abuse" it, they really can't do more than fish for a little luck.
At the end of the day, they will need to clear the entirety of that Deep Dungeon solo.
So what if they retry a few times from 160 or 190? It doesn't invalidate the fact that they still had to clear every inch of it solo, which IS the stated challenge and achievement.
But the current system throws dozen hour runs away because of a two second server hiccup, through no fault of the player.

It would be much better to remove the "wipe" counter aspect entirely, because it serves no meaningful purpose beyond the RNG and frustration element, and the timesink of making people restart from floor 1... and for what? I mean it makes the achievement more exclusive, but the "gather thousands of items in [category] nodes" and other hilarious timesink achievements are really exclusive too, and not in a fun way that challenges the player.

And now I'm really unmotivated to try again.
I literally have not even died once in my solo runs so far, but fighting the 90002 RNG gods, or Spectrum or Comcast going out, out-of-game luck should not be the challenge I need to overcome for this Achievement.

[Kuroka]

Yes, the trouble with the EU servers back then made me stop HoH as i just didnt wanna deal with that anymore, as long as there are no real savespots. even if you fish for better rng, the only thing you save is time.

[MajinUltima]

The thing that makes it particularly frustrating is that the same incidents don't stop your group runs because the instance does not become vacant.
So the solo run not only requires doing it solo, it requires an extra RNG condition not present in the group version.

But even solo, the solo achievement would not be diminished in anything but TIME investment without the "wipe" counter.
The ONLY thing the wipe counter does is pad the TIME between pushes. Retrying from 1 vs retrying from 191 is only a matter of doing the same thing you'd already done.

So PLEASE change this achievement. There's nothing more frustrating than doing everything right and then losing almost a dozen hours to a 90002 hiccup.
No other achievement in this game breaks on a short disconnect.

[Puremallace]

No. It is extremely easy to exploit it and Necromancer title is an EXTREMELY rare title for a good reason.

[ItMe]

Puremallace I'm having trouble putting two and two together, how would DCs not terminating a solo run be exploitable?

[Stepjam]

I sympathize pretty heavily with you, I can imagine that being horribly obnoxious, especially since my connection seems to have periods where it just refuses to remain stable. Only thing I can think that they can do is maybe have the instance remain open for a period of time if you DC to give you time to get back in, but I know they are conscious of how many instances are up in the game at any given time.

That said, I don't think they'll add more checkpoints because they want it to be a grind, and the solo achievement was meant to be a serious reward. Hell, I don't believe the necromancer title was even achieved by anyone until Stormblood came out, so that was like at least a year of time where nobody was able to get it.

[ArchlordPie]

I'd have it keep the instance live and running while you're DC'd. The timer keeps ticking and enemies keep spawning (and patrolling), but if you reconnect and aren't dead when you get back, you can keep going without losing the entire run. (Of course, if something spawns on top of you and murders you while you're reconnecting... too bad.) Only way I can see them at least partially mitigating this without leaving it open to abuse.

[R4ND0MD3RPUZ3R]

Puremallace I'm having trouble putting two and two together, how would DCs not terminating a solo run be exploitable?

The fact of the matter is that you can decide to disconnect on purpose if you get undesirable chests and mob spawns (i.e. only Ice Sprites and Crawlers on 183, only Anzus on 176-179) and can reset as often as you want until you get the desired result. (Assuming it would work like that. But I highly doubt it because you can't check it out due to how the game works and it also not being like this in a party sitting.) It sucks for people whose internet isn't as stable, but unfortunately it is what it is.

[Puremallace]

Puremallace I'm having trouble putting two and two together, how would DCs not terminating a solo run be exploitable?

Behemoth on the 180th floor comes to mind as one easy way to exploit this. Before his meteor impacts just dc and miss the explosion until your CD's come back up. There is no way to fix what the OP wants without some type of exploit associated with it that functions similar to the live game.

This is just a guess but the fear of a possible exploit would be my only reason to be against this.

or if we say for example if you dc it does not end your run and you can run whatever floors you were on well then that means ENDLESS attempts on floor bosses by simply unplugging your modem and causing a user side DC that mimics a power outage.

Trust me I understand as someone who has run PoTD solo a lot but simple changes like this could ruin the most rare title in FF14

[XiXiQ]

I've often thought given the old-school type theme an independent levelling, they could give you 3 strikes rather than none, like the good old days