Crash Counts As a Loss

IronyMan

Not sure if this has been touched on yet, but there is an issue with crashing.

Now I know all games crash from time to time, no issue there, but if you're in the middle of a PvP match and the game decides to wonk out and close to the home screen of the phone, when you log back in it counts it as a loss/forfeit and leaves you with half the points if you decide to attack the person (as well as a loss of any buffs you decided to use)

Unknown

Yes. And how else could it be handled? The game has no way of knowing that it was a crash vs a force quit vs power running out vs whatever -- so if you did anything other than consider it a loss then you could abuse force quit or other methods to make it look like a crash when your team was losing.

Unknown

The only alternative would be to save the state of the game on the server and resume it on app restart.

Unknown

also had this issue. sent in a ticket. will see if it gets fixed.

Unknown

Similar issue, but RECEIVING A CALL resets the game and counts as a loss. It's incredibly annoying for a phone game.

Unknown

Il Palazzo wrote:

Similar issue, but RECEIVING A CALL resets the game and counts as a loss. It's incredibly annoying for a phone game.

No, it doesn't, at least not in general.

YOUR phone doesn't have enough memory to run both MPQ and its Phone application at the same time. So the OS is forced to kill MPQ in order to get the memory it needs.

You can try closing other apps, restarting your device, etc. -- but it may ultimately come down to "your phone doesn't have enough memory".

Unknown

Zathrus wrote:

Il Palazzo wrote:

Similar issue, but RECEIVING A CALL resets the game and counts as a loss. It's incredibly annoying for a phone game.

No, it doesn't, at least not in general.

YOUR phone doesn't have enough memory to run both MPQ and its Phone application at the same time. So the OS is forced to kill MPQ in order to get the memory it needs.

You can try closing other apps, restarting your device, etc. -- but it may ultimately come down to "your phone doesn't have enough memory".

Is S3 already that bad?
Can't this app be given more priority or something?

IceIX

Il Palazzo wrote:

Is S3 already that bad?
Can't this app be given more priority or something?

Not really. Phone tasks take priority over applications for fairly obvious reasons. There's not much we can do there. We can (and do) try easing memory and battery constraints on a constant basis which helps. Even with added functionality, we're actually now taking up less memory and eating less battery than we were at launch. This doesn't really help your given situation, but hopefully it adds a little perspective. As stated above, trying to close out other active apps and the like may very well help. There are also a couple programs out there that allow you to change app priority if you're rooted, but that's a bit outside our purview.

Unknown

Thanks for the answers, that was helpful. I downloaded an app that kills inactive/empty processes, that for some reason my system favorited over PQ, and since then the game does not auto-shut down on calls.