**KNOWN AW ISSUE**
Please be aware, there is a known issue with Saga badging when observing the AW map.
The team have found the source of the issue and will be updating with our next build.
We apologize for the inconvenience.
Please be aware, there is a known issue with Saga badging when observing the AW map.
The team have found the source of the issue and will be updating with our next build.
We apologize for the inconvenience.
Options
Champ stops after 2 hits and stands there to get anailted
![Snaponstewy](https://us.v-cdn.net/6029252/uploads/defaultavatar/n1NX1KZ6AC8ZT.jpg)
After 2 hits my champ stops attacking then gets mollywhoped in the next millennium. Happening a lot and I'm sock of having to deplete my units an resources for no fault of mine
Post edited by Kabam Zibiit on
8
Comments
Also, after about every full quest, or several matches in Arena, would be best to close and restart the game. (and also periodically do a hard reboot of device itself).
I remember your situation happening a lot on my previous device, as if the inputs stopped being recognized after say a MLL or even just ML portions of attempting a full MLLLM because too much load on the processor.
(assuming Hammerbro's remark of 2x Mediums (swipes) without any Lights (taps) inbetween is not what you are doing).
*Sidebar-I honestly think that "Root" node they tested on us last year has something to do with it but because I'm not a dev, I don't have proof that "Root" is the root cause of this.
So betting either occasional server connectivity lag, or resource drain / memory leak over time in game (restart game), or from doing other heavy use stuff like YT videos, etc (reboot device before going back to game)