Constantly getting kicked from server and rolling back progress.

"

OPdHutch#2994 เขียน:

Any acknowledgement in any social accounts yet?

"

fabsh#4323 เขียน:

"

Echothesis#7320 เขียน:

If you see latency spiking, safe option is to immediately quit to desktop, which forces logout and updates you in DB. So far (if done in time) I was always able to keep loot and even return to map instance if managed to relog fast enough.

I just can't get past how badly this design seems to be. It's an always online game that forces you to be connected to a server at all times and when the connection gets terminated (I guess by some process on the server crashing) you lose all progress for the play session? Why the hell doesn't it continously save all progress? Or at the very least every few seconds? Isnt't that how a client/server infrastructure should work? This is 2025. What the hell is this code???

Edit: Fixed typo