Game Freezes / Infinite loading screen glitch

"ObiDarthYoda;c-2385323" wrote:

"StarSon;c-2385291" wrote:

"ObiDarthYoda;c-2385283" wrote:

"PeachyPeachSWGOH;c-2385235" wrote:
I'm pretty sure nobody would want to rollback the database for this, if we understood the consequences of a database rollback.

Agreed though that the issue does have wider impact and cause more serious damage in TB and Conquest.

Rollback can be for just one 'transaction' - it's not for an entire database.
https://www.techopedia.com/definition/9229/rollback

JUST like banks, etc. do w/ATMs: if the connection is 'cut' in the middle of depositing or withdrawing money, then the transaction is not completed, and nothing is updated in the field(s).

And for EA/CG, who I assume are using mySQL, here ya' go:
The ROLLBACK operation undoes all the changes done by the current transaction i.e. If you invoke this statement, all the modifications are reverted until the last commit or the START TRANSACTION statement.
https://www.tutorialspoint.com/mysql/mysql_rollback.htm

I don't think you really understand what you're saying. You don't even know that it's a database issue, which is honestly unlikely, since it seems to be related to memory usage based on device settings. If it were a database issue it would be much more widespread.

Also, at this point you can't just rollback. It's weeks of play time for hundreds of thousands of players.

I DO know what I'm saying - and if you read my post, it is for ONE 'transaction' at a time - which means ONE battle, etc. Rollback just means the 'transaction' is not 'committed' since there was zero activity. It is NOT for everyone, for all time.

You also have a basic misunderstanding of how the battle system works. When you click Battle, it tells the server you started. Nothing else is sent until the battle is completed, but energy/attempts/characters are used with the first call. No need for a transaction. There is another post with a neat idea about "re-enter battle" but idk how feasible that is all things considered.

"Ferril9909;c-2385342" wrote:
Not a good business precedent for them to set unfortunately. If the number of payers (note - not players) decreases enough, or enough complaints get back their way through Google/Apple support, maybe then.

It's not a precedent. Business as usual for CG. Nothing will change. This bug will either get fixed or it won't. CG, Google, and Apple won't care either way.