Deep Dungeons and DDoS Attacks

[DeepDungeon_Enjoyear]

After two weeks of constant issues, I’m officially done trying to push through this. Yesterday I lost another Pilgrim Party run at floor 98 due to mass disconnect. Today, I lost two more runs in Eureka Orthos (Solo) one on floor 73 and another at floor 30, with the boss at 2% HP.

That makes over 10 runs lost (actually more I’ve stopped counting at this point), easily more than 50 hours of Deep Dungeon progress gone.

This isn’t an isolated issue. Downdetector show frequent disconnections and instability. Deep Dungeons are some of the most time consuming and punishing content in the game, and losing entire runs because of server instability is beyond frustrating. At this point, the game feels unplayable for anyone trying to do serious content that relies on stable connection.

[VictorSpoils]

I could argue in favor of allowing continues with any number of KOs but making the floors harder, particularly the earlier floors. It is slightly odd design to track KOs but ultimately force you to reset with only 1. This would alleviate the d/c's for clear runners and not negatively impact the score runners, who just reset anyway. The latter could also be given some form of tangible reward for the amount of effort they put in.

[GioTrance]

After two weeks of constant issues, I’m officially done trying to push through this. Yesterday I lost another Pilgrim Party run at floor 98 due to mass disconnect. Today, I lost two more runs in Eureka Orthos (Solo) one on floor 73 and another at floor 30, with the boss at 2% HP.

That makes over 10 runs lost (actually more I’ve stopped counting at this point), easily more than 50 hours of Deep Dungeon progress gone.

This isn’t an isolated issue. Downdetector show frequent disconnections and instability. Deep Dungeons are some of the most time consuming and punishing content in the game, and losing entire runs because of server instability is beyond frustrating. At this point, the game feels unplayable for anyone trying to do serious content that relies on stable connection.

I've lost 8 runs in total between a few deep dungeon solos as well. After losing PT on my main I went to an alt to practice Class-only runs of Palace, just to lose it to DCs. Eventually we had like 8 hours of being okay, so I started PT on my main again to DC.

This is genuinely the only content in the game at all that punishes you for disconnecting. Not even Criterion Dungeons or DRS punishes you this badly.
Even if you take the DDoS out of the equation, The Sacramento Node drops connections a lot too. Anyone who doesn't connect through here probably never notices but that node backs up a lot and sometimes gives up.
Obviously Square can't do anything about that themselves, but they should at least acknowledge that it happens.
DC in Criterion/Ultimate, okay we repull. 15 minutes at the worst. DC in DRS? You die, but if the rest of the party still clears you can be raised. Entire party wipe? Idk what the clear speeds are now, but it used to be like 2 hours. That's a raid night, but still manageable you know?
DC in a solo deep dungeon? 20 hours.

I could argue in favor of allowing continues with any number of KOs but making the floors harder, particularly the earlier floors. It is slightly odd design to track KOs but ultimately force you to reset with only 1. This would alleviate the d/c's for clear runners and not negatively impact the score runners, who just reset anyway. The latter could also be given some form of tangible reward for the amount of effort they put in.

At this point in time I think this is the most fair. Allow players who want the title to continue since they are still putting in all the effort, but reset the score.
Hell, even if they hard capped us at 3 KOs to but reset our score each "Continue" I see no way how anyone who still clears "doesn't" deserve it. How someone can abuse it as a way to reset bad floors. Or how it effects Score Players.

It feels like absolute -garbage- to have 2 save files on Floor 91 with 1 KO, and knowing there is nothing you can do while still not being at fault.

[Valence]

I know it's probably not easy to do because other games struggle with this as well, but the best solution imo would be to have a replay feature that literally saves the state of the game as soon as a character goes ?????
Reconnecting would resync with the game in the exact same state. If you were fighting, then you'd go back to fighting with everybody's HP and state reinstated as they were.

[Plaglow]

Chat we just got DDOS'd out of PT at floor 99
its so over

[Emme]

I wish they acknowledge and do something about this issue. Got two runs interrupted today in the span of a few hours. As I guess many of you do, I often do Solo runs for the title. It's really not fun to redo the earlier floors over and over because some jerk in a basement pressed the funny button or something.

One of the worst parts of this whole thing, to me at least, is logging back in and just seeing everyone spawn by the entrance, knowing we all got [Redacted] for reasons beyond our control. Like, what can we do about it? Nothing. What do we do? Pray we can speedrun a set of floors before we get forcibly dragged out the door next time.

Something needs to be done. Either about the DDOS in general or at least to protect Deep Dungeon runs.
From the proposed solutions, resetting the save to a prior state, or allowing us to continue accumulating KOs while resetting the score to 0 both seem fine.

[ThurinTurambar]

whats even crazier is that current system is super exploitable if someone was dedicated enough. If you disconnect and just close the game, it seems the server will see you as online indefinately and keep at least a bit of the instance in memory. You can ask your friends if you are visible as online on friend list and if they can /tell you (they will receive character being bound by duty error).
So now imagine what could someone with x botted free trial accounts could do. Enter in there... and just disconnect, leave it like that to clog the server memory. How many would it take to basicly achieve a ddos attack?

So yeah, keeping the instance 'alive' for 5 minutes after player disconnects and discarding it once timer passes would be good both for players and servers