POTD KO and server stability

[Airget]

For an instance content that relies on not only ones connection to stay stable but also for the servers to stay stable, one hiccup and you lose all your progress to proceed past floor 100. It's not the mobs or even the bosses that are difficult in this content but the hope that you don't d/c and lose the time spent progressing and planning ahead for future floors.

I feel SE should implement an NPC that removes -1 KO from one save when it's a server error that caused you to lose said dungeon, aka unstable servers. At least then the only variable that could hurt people while going up the dungeons is there own connection, which while it still sucks I"m ok with. However when it comes to the servers being the reason for the loss and not ones connection, they need to implement something to allow people to rollback a KO that was the servers fault.

[Ametrine]

The fear then may be abuse from the player's side. Would the servers know the difference from a forced DC or an unfortunate outage?

[aesteval]

The fear then may be abuse from the player's side. Would the servers know the difference from a forced DC or an unfortunate outage?

In the case of what's going on with Primal, it's a big data center wide kablooie. That much could be validated as legitimate. It wouldn't account for every disconnect, but I think the original motive has much to do with Primal's problems.

[Lambdafish]

In the case of what's going on with Primal, it's a big data center wide kablooie. That much could be validated as legitimate. It wouldn't account for every disconnect, but I think the original motive has much to do with Primal's problems.

I'm surprised at the lack of outrage over loss of progress when it comes to primals outage (maybe people don't know and will log back in to a nasty surprise)

[Ametrine]

Well, there is anger over Primal's bizarre habit of breaking at peak hours, on a damn near biweekly basis.

It's especially strange considering Aether, which is considerably more populous and straining, never so much as hiccups.

I'd rather them fix our servers verses adding a "cheat" to bandaid the issue.

[Airget]

It's a fix til they find a way to make things more stable. They should put something in place instead of nothing if they keep running into issues and it causes people to lose their progress over something they have 0 knowledge over. They claimed to fix the issue earlier and then I just d/ced about half an hour ago, frustrated beyond all belief because I was on floor 123 and then bam, d/c. Not even a slow d/c. One of those d/ced where actions are still taking place, you are mid-fight and then just ZAP you're gone.

If they know these servers are have issues and nothing they do seems to be fixing it, they should attempt some form of compensation for people who lose their progress because of the faulty server. My suggestion isn't for something to always be there but to at least offer people a fair chance at actually running a run without it being ruined because of an issue on their end.

--

And just to confirm, ya it does just boot you out with no recourse if you d/c for any reason. that is just stupid. So fair warning, regardless of duration of d/c, when you do POTD solo, one d/c and that run is over. Again, they could at least keep you in the instance and give you a chance to log back in, and ye know, now that I know no amount of speed would of saved my run from the d/c, that just makes it more irritating, you can do any other dungeon solo, d/c and actually reconnect and be ok but not with POTD, they just kill your run. That's a lot of pressure to put on the player to know that any short circuit will end their run.

Honestly with that, screw solo, that is not worth the pressure, to know that if you d/c your run is over, it makes no sense to do that, a forced d/c takes time to acknowledge on the server end, so even if someone attempted to pull that off they would most likely be killed by any mobs in that 20 second window or more if they did it wrong. It takes 20 seconds to disconnect on your own and even then you can easily die in that 20 seconds, I don't see what exploit someone could do with disconnection (solo play mind you) that should just end their run.


--------

In it's current form, they are asking a lot of technology to stay stable for a solo run. Everything has to go perfect, you could have the best run, but the moment they identify you as "logged out" they end the run. With Party mode, I can understand having 0 KO to go past 100 up to 200, because it is going to be easier for a group of 4 to make it to 200. However a solo player has to rely on themselves to get through the journey. To expect them to be held to the same 0 KO and 0 disconnects as a party isn't very balanced. At least if a party memeber d/cs in POTD the other 3 can wait til they get back but if a solo d/cs your run is over.

Solo 100+ should get at least 5 KOs to at least give them some leeway for issues like internet or servers. 0 KOs would only be acceptable if you didn't get kicked out of the instance the moment of d/c, then I could understand them keeping it like that. But something as simple as 5 lives to make it to 100+ would at least make this content easier to digest because in it's current unstable form, I don't think people realize that if you play solo and anything causes your connection to bugger off, power goes out, cable gets loose, servers disconnect or give you an error, and you can't continue that run anymore.

At least with a 5 KO limit if there are server issues or a disconnect messes you up you lose a life ya, but at least you don't lose those hours of progress from something out of your control.

And then of course just add those KOs to the score count, add points based on how many lives left or deduct based on how many used. The odds of running into 5 KO's due to server/internet is a lot less likely than losing a run from a single disconnect. It would make it more bearable to have to eat a loss because of a d/c but at least know as a solo player I could try again 4 more times at least.

[Eloah]

something like this just happened to me. I joined a group that wanted to try going to floor 200, but you have to head past floors 51-100 without a KO, okay, I guess. Well we get to floor 79 and guess what happens, I DC, not just a minor, "Oh hey sorry about that", a full blown I have to reset my router, and shut down my PS4 DC. Well I finally get back, they were able to fight the boss, yay for them, but I was stuck on floor 71 and they had floor 81, so yeah we don't know what to do now, just yay?

[Alleo]

I had that happen yesterday..it was only on a solo floor 21+ run but I had to start again from floor 1 because I wanted to get through it without any k.o..I already fear the upper floors. I would be okay if a dc simply means that you have to start again from floor 51 if you got kicked at 59, just like you are if you die but it would be nice if a dc does not count as a k.o..

I know people will say that they might not want to do it because people could take advantage of it but I dislike how other people are punished for things just because some could theoretically cheat with that..If someone is on floor 59 and notices that he has no time left and forces a dc to land back at 51 without any k.o to try again..well why should I truly care about it? Since everyone could do that theoretically no one would have a true disadvantage since everyone could choose to use it that way but at the same time us people that are kicked thanks to a dc (so something that is completely out of our hands) are at least not punished like we are now.

At least make it so that if someone disconnects they still have a chance to come back (depending on where you got the dc though this could mean certain death)

Its already hard to not get a k.o with all the random monster spawns, traps and other bad luck, dont make it into something frustrating by punishing people for unstable servers or bad Internet..