Stop counting as a loss when your game crashes!
June 25, 2020 9:32AM
edited June 2020
It happens all the time in TW and GAC. OK, I read all the warnings and suggestions eg. restart the game and clean the memory/cache before do important matches. But come on! Why can't your game code distinguish the crash/freezing from force quitting? It is fair that the force quitting counts as a loss, but it's not fair counting the same when the game crashes! Why counts it as a loss, and why can’t that team be reused when the game crashes through no fault of my own? Why can't you fix this for years?
3
Replies
You should report frequent occurrences of anything happening. <<Answers HQ>> collects the relevant information that can help them isolate issue like that.
Unfortunately not everyone experiences what you are experiencing. Similar to the above post, I personally have only had 1 instance of the button disappearing as the only instability I have ever seen in the game.
It isn't that harmful but it is wrong, and usually actively encouraged. A TM-loaded NS team usually will not = win in a TW. Just an extra battle.
Better analysis of crashes, client's platforms, and where they occur should be done.
I think they should sim results after timeout too.
The battle takes place on your device. I cant imagine the server is built to be able to take the load of running X number of battles 'at any moment'.
Timeouts are different, and there is at least some strategy to placing a team that will cause a timeout, or using a team that can beat a TO team within the time.
Hard disagree that this is cheating.
+1
I'd love to face a guild that encourages preloading TM 😂
Using airplane mode this way simply replicates the "Forfeit" feature - and you regard it as cheating? For real?
This is the point, it doesnt just replicate it, or people would just use forfeit, you would only use airplane mode if you had been defeated/took a risk for possible win. Forfeit is a required turn/move/command and is therefore strategic!
That being said... not sure I would go so far as to say cheating... more manipulation... or maybe even training wheels !
OK, it replicates the results of using the "Forfeit" feature:
The battle counts, your team is marked as defeated and the team you fought is reset to the state it had at the beginning of the battle.
The solution is
Except it allows you to use it when it isn’t your turn, or after you’ve already lost. So it provides additional benefit. It’s pretty clearly an exploit. It’s also pretty clearly been accepted by CG as an acceptable way to play the game, so it’s not cheating. I do think CG should just build it into the game so a restart isn’t required (add an accept/refuse battle option after a loss in GA/TW).
Improving servers will cost money, and spending money is not the CG way
Not a fan of this Kyno, i did this and MANY others have as well and the response I got was rather lazy and seemingly an auto response with no follow up:
Perhaps you can respond on their behalf?
But you agree the result is the same, right?
The "freeze" is the big issue for many - abs since the recent update there have been many more of those than usual going by the admitadly anecdotal evidence in our guild and shard chats. By virtue of the fact that the game requires a hard reset, my guess is that there would be no way for it to produce an error code.
In game guild: TNR Uprising
I beat the REAL T7 Yoda (not the nerfed one) and did so before mods were there to help
*This space left intentionally blank*