Constantly getting kicked from server and rolling back progress.

"

Echothesis#7320 a écrit :

Not updating DB (database) continuously is actually normal for projects like poe because of large DB pipeline load. This isn't some shooter game where your character state is defined by 2 guns/ammo and 3 medpacks. In game with millions of items devs have to implement save checkpoints like entering new instance or logging out, while also making the system dupe-proof, so players couldn't benefit from crashing instance on purpose (yet they still do, finding on-demand crash in poe equals to bannable exploit:)).

"

Xpucmo#0475 a écrit :

@GGG FIX WHEN ?

It's getting out of hand
Rolling back the progress is not a big deal but failing the map because of it is sooooooooooooooooooooooooooooooooo fffffffffffffffffffffff annoying

I have missed more than several progression points because of this DC BS :

https://postimg.cc/XG04mcy5

"

fabsh#4323 a écrit :

"

Echothesis#7320 a écrit :

Not updating DB (database) continuously is actually normal for projects like poe because of large DB pipeline load. This isn't some shooter game where your character state is defined by 2 guns/ammo and 3 medpacks. In game with millions of items devs have to implement save checkpoints like entering new instance or logging out, while also making the system dupe-proof, so players couldn't benefit from crashing instance on purpose (yet they still do, finding on-demand crash in poe equals to bannable exploit:)).

I'm not talking about updating the database continously. I am talking about updating it at all during a play session. This game doesn't save the progress when I portal out of the instance. Obviously, as these rollbacks clearly show. There is a huge spectrum between saving data in realtime and saving data once every 30 minutes or so.

And we are also not talking about a client crash. This is a problem with the server code. The player shouldn't be able to influence what the server does. If they can, that's also a design (and probably security) issue or a bug that needs to get fixed ASAP.

I'm not buying your assumption that this isn't technically possible. 1) Bigger games with as much complexity and more players don't suffer from these issues. I've played pretty much every MMO or ARPG since WOW came out originally and I've never seen behaviour like this. And I've seen plenty of server and client crashes in my time in all kinds of games. 2) I write about infosec, including web applications and their APIs. I've seen the inside of systems that process several hundred payment transactions per second. That's a lot harder and a lot more critical than running a game with a few hundred thousand concurrent players. Those systems can't afford to lose 30 minutes of transactions when the server encounters a fatal error. That's why software solutions exist to solve this crap. Most of them are even open source.

But all of this pales in comparison to not even jumping on the forums for a second and telling people that it's being investigated. That is the worst part about all of this.

"

fabsh#4323 a écrit :

"

Echothesis#7320 a écrit :

Not updating DB (database) continuously is actually normal for projects like poe because of large DB pipeline load. This isn't some shooter game where your character state is defined by 2 guns/ammo and 3 medpacks. In game with millions of items devs have to implement save checkpoints like entering new instance or logging out, while also making the system dupe-proof, so players couldn't benefit from crashing instance on purpose (yet they still do, finding on-demand crash in poe equals to bannable exploit:)).

I'm not talking about updating the database continously. I am talking about updating it at all during a play session. This game doesn't save the progress when I portal out of the instance. Obviously, as these rollbacks clearly show. There is a huge spectrum between saving data in realtime and saving data once every 30 minutes or so.

And we are also not talking about a client crash. This is a problem with the server code. The player shouldn't be able to influence what the server does. If they can, that's also a design (and probably security) issue or a bug that needs to get fixed ASAP.

I'm not buying your assumption that this isn't technically possible. 1) Bigger games with as much complexity and more players don't suffer from these issues. I've played pretty much every MMO or ARPG since WOW came out originally and I've never seen behaviour like this. And I've seen plenty of server and client crashes in my time in all kinds of games. 2) I write about infosec, including web applications and their APIs. I've seen the inside of systems that process several hundred payment transactions per second. That's a lot harder and a lot more critical than running a game with a few hundred thousand concurrent players. Those systems can't afford to lose 30 minutes of transactions when the server encounters a fatal error. That's why software solutions exist to solve this crap. Most of them are even open source.

But all of this pales in comparison to not even jumping on the forums for a second and telling people that it's being investigated. That is the worst part about all of this.