Please don't penalize players in Deep Dungeon due to a random disconnect.

Its annoying, and incredibly unfair.

I know its a old issue, but the fact remains the penalty for something beyond the player's control is still there.

I was livid when I got to the 150+ floors with Warrior in potd, and then suddenly I'm punished for it because the internet decided it need to throw up for a second.

=

At least give a grace period if I happen to use a revive pomander because I'm sure I would be dead by the time I logged back in.

Or anything please, this should not have been a thing for years.

What makes you think SE is capable of fixing this issue? Or really want to at all?

If it isn't going to cause outrage on 2ch or be on a MrHappy video, they don't care, period.

There's no way for SE to determine the cause of a disconnection, so they treat them all the same way. It's very trivial to make the game log you out immediately, not all disconnections leave you standing still for a few minutes.

It is impossible to know the cause of the disconnection on the server side, not only this game but any game.

It's not fun. My solo run of HoH, which was going flawless and I was at a point where I was confident of getting through it, gave me a lag spike (which I'd never had before in this game actually) and then I died because it didn't register that I moved out of the cone at all. It must have been around the time that ntt issue started.

But I don't think they can do anything about it without making the content easier. If we had multiple chances then the amount of solo clears would be far higher. If things didn't kill us, then it wouldn't be punishing enough and become too easy. It would become as easy as a dungeon where soloing it on a Warrior or Blue Mage is trivial.

It's really frustrating. I wouldn't mind if the game would put me right where I was when I DC'd if I log back within a few minutes even at the risk of dying if there was something coming at me or if I was fighting (so that people don't abuse it to survive unsurvivable situations). A chance is better than no chance. Several times when I got DC'd I was in safe places. It does something similar now in dungeons with duty support.

If this game "respects your time" they should be implementing a one-time checkpoint system that you either set manually or it automatically gets activated upon DC, and is erased the moment you reload. Wiping should be the only thing forcing you to start over.

I got to floor 98 in HoH and quit trying because of this exact problem. With 200 floors PotD is just too long time-wise to even attempt. A disconnect or crash is guaranteed during a 10+ hour run.

You DC at least once every 10 hours of game time?

Yeah if you dc that much, the problem is on your end.

But yeah as others have said, there's no way of identifying why the disconnect happened. So people would absolutely abuse this.

This suggestion needs more attention

Sucks but majority have stable connections, it will 10000% be abuse indefinitely if any attempt is made to save you from DC....the title would just be kinda of pointless when there is a 100% way to cheese to top floor. I say the potential abuse outweighs the benefits on this.

Lost a run on floor 88 solo with 26 mins left, full poms and a auto rez activated. Lost connection for a few seconds. Never went back after that.

Quote:

---

Originally Posted by ValkyrieL

Sucks but majority have stable connections, it will 10000% be abuse indefinitely if any attempt is made to save you from DC....the title would just be kinda of pointless when there is a 100% way to cheese to top floor. I say the potential abuse outweighs the benefits on this.

---

Nobody's pocket is being picked here by erring on the side of the player, especially in player positions where there's nothing to gain from disconnecting (i.e. the player is not in combat). I can think of at least a few ways to foil attempts to game the system without explicitly knowing how a disconnect happened. One possibility would be a snapshot the current state of the instance (i.e. last known character position, enemy/trap/treasure/etc. states), and load directly from that when the user returns, similar to a quick save file on a offline game. The user gains zero advantage from purposefully disconnecting because they are in exactly or near exactly the same situation they were in when they DCed. If they were getting beaten on by a monster, that will be the situation when they return. (Or the instance can be failed if the player was currently aggroed when they DCed, and not bother with the state in that case, since that's a clear situation where they might gain from the monsters being reset even a little).

Obviously, the feasibility of this is dependent on just how many variables are being tracked, but I kind of doubt the state variables for each instance take up that much memory.

Once on HOH my group made it all the way to floor 99 and about to go to floor 100 when game caused us all to DC from ddos attack.

That sounds incredibly frustrating and seems to be a fair request. If it can't be met, personally, I think then it should be changed to allow it to be possible (without becoming too easy as a result).

Quote:

---

Originally Posted by Hexadecimal

Nobody's pocket is being picked here by erring on the side of the player, especially in player positions where there's nothing to gain from disconnecting (i.e. the player is not in combat). I can think of at least a few ways to foil attempts to game the system without explicitly knowing how a disconnect happened. One possibility would be a snapshot the current state of the instance (i.e. last known character position, enemy/trap/treasure/etc. states), and load directly from that when the user returns, similar to a quick save file on a offline game. The user gains zero advantage from purposefully disconnecting because they are in exactly or near exactly the same situation they were in when they DCed. If they were getting beaten on by a monster, that will be the situation when they return. (Or the instance can be failed if the player was currently aggroed when they DCed, and not bother with the state in that case, since that's a clear situation where they might gain from the monsters being reset even a little).

Obviously, the feasibility of this is dependent on just how many variables are being tracked, but I kind of doubt the state variables for each instance take up that much memory.

---

The reason thet are not going to do this is becaus it makes playing with a higher ping/instability completely insufferable when you keep rubberbanding. Also, you can disconnect yourself from the game instantly by force closing the game.

Quote:

---

Originally Posted by ReynTime

If this game "respects your time" they should be implementing a one-time checkpoint system that you either set manually or it automatically gets activated upon DC, and is erased the moment you reload. Wiping should be the only thing forcing you to start over.

---

Its not about respecting your time. The solo title is one of the few "flexes" that mean anything. While DC's are irritating, if they didnt treqt a DC as a death, then people would be exploiting the hell out of it.

It must be bloody soul destroying when you DC deep into PotD though.

While what youre suggesting sounds like a fair solution, a single use checkpoint is hard to exploit. Connection issues tend to happen over time, so I dont think its necesarilly that practical.

Tecnically, the server can know you DCed because you closed it. The client knows when game window lose its focus. To force close, it must necessarily unfocus the game window to interact with OS. So, if the connection loss is following a unfocus game window message, it was 100% sure provoked by the player.

So, there are 2 situations that's out of client's control:

1. User's computer was turned off (or rebooted or whatever);
2. User's network cable was disconnected.

So, in those cases is a matter of giving the benefit of the doubt or not. In both cases, there could be a 60s timeout to let user comeback to the game. If so, the game will act like its character was stopped there for the DC time. If the user took of because he would wipe, he will wipe anyways. If he DCed in a safe spot and came back after 20 seconds, the server will act like he was 20 seconds stopped at that place.

I understand not letting you become unkillable or pulling you into a safe pocket disconnect limbo when you DC because yeah that will surely get abused, but whats so wrong about just not kicking you off the instance if you happen to DC out of combat and out of danger?
I can't think of a way to abuse this, time in the instance will still be ticking, enemies will still be patrolling and aggroing, mechanics still happening, etc.
Surely the engine can handle leaving your character unmanned for a bit and if it pulls something and gets killed then so be it, dead. But if not then you can just log back in and continue.

I still feel you should be able to reset back to the latest x0 floor... you still beat it with your own skills and the only thing you save is the time wasted gettin back up. Everything is random anyways, so you cant even cheat by knowing your way...

Loving how even something as basic as this is getting pushback. As if someone being forgiven for their ISP disconnecting them takes away from the "prestige" of their title that people literally buy for like 12 dollars on the black market.

Or because it's not that basic and any solution that isn't 'you stay in place until you reconnect or X minutes pass, the instance keeps on going, if a patrol or AOE kills you, oh well' would be very easy to exploit given the design of Deep Dungeons (aside from the 'snapshot' suggestion, but that's unrealistic for technical reasons).

Mind you, staying in place would be better than the current status quo where a disconnect is an immediate eject, but it's also not what most of the suggestions are proposing.

Quote:

---

Originally Posted by Sindele

Or because it's not that basic and any solution that isn't 'you stay in place until you reconnect or X minutes pass, the instance keeps on going, if a patrol or AOE kills you, oh well' would be very easy to exploit given the design of Deep Dungeons (aside from the 'snapshot' suggestion, but that's unrealistic for technical reasons).

Mind you, staying in place would be better than the current status quo where a disconnect is an immediate eject, but it's also not what most of the suggestions are proposing.

---

That’s exactly what I suggested. A chance is better than no chance. Made another attempt at HoH and all was well with an amazing luck on Magicites and pomanders only to DC on the exit to floor 93. I was able to reconnect immediately.

I am not even trying PotD any longer after the last DC at 186.

Quote:

---

Originally Posted by Avoidy

Loving how even something as basic as this is getting pushback. As if someone being forgiven for their ISP disconnecting them takes away from the "prestige" of their title that people literally buy for like 12 dollars on the black market.

---

It's getting pushback because the request is riff with abuse potential. If someone accidentally pulls too much or is very likely to time out on the last set of floors, all they have to do is Alt F4 and bam, they get a whole redo. There's absolutely zero way for the game to know whether you DC because of say, a power outage, your cat chewed a wire or you intentionally killed the game. Which is why they can't implement something like this.

The last time I played wow (which granted was at the end of BFA), there were certain scenarios where if you DC'd, the game would basically snapshot you + whatever agro you had. DC fighting 3 mobs at 50%? Come back to those same mobs at 50%. Much more sane than losing potentially 10+ hours of time because of a dc. It is really frustrating and kinda silly.

Quote:

---

Originally Posted by ForteNightshade

It's getting pushback because the request is riff with abuse potential. If someone accidentally pulls too much or is very likely to time out on the last set of floors, all they have to do is Alt F4 and bam, they get a whole redo. There's absolutely zero way for the game to know whether you DC because of say, a power outage, your cat chewed a wire or you intentionally killed the game. Which is why they can't implement something like this.

---

Several solutions have been proposed to get around that. You didn't bother to read them. You pull too much? You reload and you are dead, much like when you DC and are with a team and no one is around. No one seems to have a problem with that. DC in a safe spot with no ugly mob coming at you? relog within a few minutes and you are back in the game.

Quote:

---

Originally Posted by ForteNightshade

It's getting pushback because the request is riff with abuse potential. If someone accidentally pulls too much or is very likely to time out on the last set of floors, all they have to do is Alt F4 and bam, they get a whole redo. There's absolutely zero way for the game to know whether you DC because of say, a power outage, your cat chewed a wire or you intentionally killed the game. Which is why they can't implement something like this.

---

Even IF you abuse it like that, you still have to clear those floors... idk if you can get THAT good rng so its worth to reset 100x lol

My honest advice is to just not even try and go for a solo run unless you have a stable ethernet connection. It's just too risky, and immensely frustrating, I should know.

I think you should be allowed to continue DC/Death but it will count as a death and make it so you cant get the title
just for practice sake

Quote:

---

Originally Posted by Toutatis

Several solutions have been proposed to get around that. You didn't bother to read them. You pull too much? You reload and you are dead, much like when you DC and are with a team and no one is around. No one seems to have a problem with that. DC in a safe spot with no ugly mob coming at you? relog within a few minutes and you are back in the game.

---

I did "bother to read them." They're just not the solutions you seem to think they are. First and foremost, a DC with a group isn't necessarily a wipe to begin with as I'll outline below. Furthermore, your "solution" wouldn't even apply to solo runs as you'd respawn dead, thus still wiping. Your second scenario is exactly the type to be abused, specifically in a solo run. If it looks like you won't clear the set of floors in time or you get several bad RNG rolls, you can safely "DC" and reset the run.

Quote:

---

Originally Posted by Kuroka

Even IF you abuse it like that, you still have to clear those floors... idk if you can get THAT good rng so its worth to reset 100x lol

---

If you've solo'd to the higher floors, especially of PotD, and you get bad RNG, it's always worth intentionally DCing if it resets the run because you'll save anywhere from 9+ hours getting back there. Even with a group, that's not a short climb. So resetting is still better than risking a wipe. In fact, to both these points. A perfect abuse scenario in a group setting would be always have someone not aggro. That way if traps go off or a straggler is pulled, that one person can hide, DC and potentially raise everyone. Obviously, you wouldn't do this for every single pull but having it be a legit option and simply making say, the healer wait a second or two to aggro means you always have a potential out.

Another abuse scenario? Tank pulls every single mob in sight right towards the exit, nobody else aggros and then immediately Alt+F4s. All the mobs now auto reset, ignoring everyone else and the tank respawns dead... only to be raised by the healer. People will absolutely do things like this.

I see no harm in this. In my opinion it's not making Necromancer easier as much as it's making it faster. The first 100 floors of PotD are really easy solo assuming you're anywhere near capable of necromancer, so assuming you abused this all you're doing is saving time. Sucks for people who've done it before, but it's not really an application of skill and never has been. First 100 floors itself are 6-7 hours and you start taking on 40+ minutes consistently for every 10 after, depending on how badly RNG treats you.

Unlike the person above me I'm not gonna be losing any sleep at night over seeing a few more Necromaner titles in game.

Quote:

---

Originally Posted by ForteNightshade

Another abuse scenario? Tank pulls every single mob in sight right towards the exit, nobody else aggros and then immediately Alt+F4s. All the mobs now auto reset, ignoring everyone else and the tank respawns dead... only to be raised by the healer. People will absolutely do things like this.

---

You can easily give it an "everyone must be alive" condition. Further, again... if you get to 180 and reset on 186, you still need to clear those 6 floors out again. Same difference. Sure you can fish for better rng but still... ppl cheat there anyways so whatever, the effort is still there and technically you even do way moor floors then needed...

You save some hours but you still need the same skill.


Look at Savage - imagine you're only allowed to reach the enrage once and after that youre locked out of the fight for the week. Or if you wipe on part 4 you need to redo 1-3 before you continue...

I just feel skill should be the limit, not time.

I lost a run at floor 88 Solo in EO due to a tiny DC. I'm never doing that content ever again. Just too much of a time sink.

That being said there is nothing SE can really do about it either as if you let people DC it opens the door to exploits. It's fine as is. You just need to be willing to accept that it's a risk involved.

Said in another thread and just thought to share here, I know it'll make it easier but I think it's fair. Every 50 levels you checkpoint, if you fail you can start there. At level 199 and hate your RNG (as an example someone made here) ... sure you could reset, but you'll have 50 levels to go through with potentially just as bad RNG. Easy to represent too, just star (UI mark) the 50 level options once you reach them consecutively without dying (then you can start from them and still count for achievement).

I'm not that much into this content, but an option I'd like to see is a 'training save'. If you fail a run (for whatever reason), to be able to still use the save to retry that floor ; of course without the ability to progress further and with no (or limited ?) drops.

I understand kinda why it happens and why its difficult to create a fix for it without creating exploits. However, truthfully, as someone who pays monthly to support this game, I don't care why its a difficult problem to solve. It just needs to be solved ASAP. This aspect of the game makes deep dungeons unplayable and not much fun at all. (My internet connection is fine btw, I ONLY get dc'd in deep dungeons). I was heavily looking forward to trying to get the necromancer title because it sounded like a ton of fun. However, after I realized this little "quirk" regarding deep dungeons, I threw away those plans instantly. This is a total deal breaker and Square NEEDS to fix this or im gonna end up unsubbing.

I can get behind this.

The only difficulty would be making the distinction between those that actually do legitimately disconnect and those that intentionally disconnect to essentially try and get a reroll on a set of floors.

Ehh, it's already content people cheat in anyway from everything I've ever read/seen on it.

From the "simple" exploit of spinning monsters to the third party tools that essentially give you permanent pomander of sight, people have been abusing their way to the titles already.

I was really into trying to get the titles for a good while, and out of about 7 or 8 runs I did to 150+ in PoTD, I had two DCs. More than that from runs that never made it to 150 even. Most infuriating DC I've had was DCing at 178. I didn't have perfect pomanders or anything, but the time loss is absurd.

Most of my DCs in PoTD happen in the 140s range. Which is still a loss of 8~9 hours.

HoH I DC in way less. Most infuriating DC there was a floor 92 DC. Time so crunched in that floorset though, I may not have made it anyway.

Haven't even given Eureka Orthros a solo attempt. Everything about soloing just dissuades me from even going anymore. Having to start over from floor 1 just sucks completely.

Worse still is the fact that you can make it to final floor, and then DC before touching the item you need to interact with to actually get the achievement. We've all seen the guys who make it to the final floor and time out before touching it. Especially egregious in PoTD where the run down the slope is like a minute by itself. But you could do everything right and be good on time and DC before touching it as well, killing the attempt.