Talk:Battle Arena/@comment-30578224-20170413213545/@comment-25430646-20170426044825

Hi Katali119,

I have two theories that cover what you and I both experience (and I suspect maybe most players).

Theory 1:  The game software has a memory leak (Computer Science term), which basically means that as the program runs, it continues to need more and more memory, until it runs out. The program then crashes, and all memory used by the program is released back to the operating system (Android in your case, iOS in mine). The program can then be restarted. Any thing you changed (like collecting coins, food, winning a battle) that had not yet been sent back to TL/S8 before the crash, is lost, as you will see when the program is restarted. Other than food, battles, and coins, the memory leak seems to also correlate with visiting neighbors with high levels. (i.e. I can only visit 2 or 3 neighbors that are at level 190~200, before it crashes, but several more if I choose neighbors at level 20~80)   So basically there is an accumulation of the memory leak stuff related to pretty much what ever you doo, and eventually the program crashes.

Theory 2:  The program calls back to the mothership (TL/S8) whenever it has accumulated some number of changes that have occured, but not for each and every change. I.e. it batches up the information to reduce the amount of back and forth between your i-Toy or A-Toy. The master copy of the state of your game is held at TL/S8, and your phone/tablet/pad/whatever has a local copy. between batch updates, your local copy is changing (and so is what you see on your screen). When the batch updates occur, there is some mechanism that verifies that both copies are an exact match. If something goes wrong, and TL/S8 detects that after the batch update the two versions are not identical, TL/S8 forces an update to your device of the state it has prior to the update. This is the glitch you and I have observed (and I am guessing most players).

The solution to both of these (and this is what I do when I care) is to force a re-syncronization prior to doing something that would make you sad if either of the above 2 things happened. What you need to do is exit the program completely. On iPhones it is here: https://support.apple.com/en-us/HT201330 and on Android look here http://www.wikihow.tech/Close-Apps-on-Android

You can confirm that you exited the program completely because when it starts up, you get the splash screen instead of the view of your islands. One of the things that is (probably) happening while the splash screen is displayed, is that TL/S8 is making sure your local copy of the game state is an exact match to their copy. When the program has recently been started, I have never seen the glitch problem. I only see it after a lot of changes have been made.

I hope this helps you, and maybe some other players.