**Mastery Loadouts**
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Comments
Another game freeze + stuck in this window. The -50% health is the subsequent event.
Game Version : 28.1.0
Happens in AQ, LOL haven't tried AOL.
@Kabam Vydious
Android version 8
Huawei nova 2i
Last update : September 2 2020
Same during war... fight timer started, and game freeze, and happend to me and another team members!
I wonder what could happen if there was already that Corvus Glaive " 1% Nerf" . I'm constantly losing half health, barely everyday once a day
1) Samsung Android
2) Galaxy note 9
Device : Oppo f11 pro
Os : Color os version V7
Android version 10
Plz look into this problem n fix it.
Thanks.
Happened today too. It has been over a month since this issue
Wtf!?!?
Mobile : Moto M
Model no : XT1663
Android version : 7.O
Android
10
Please resolve this soon, I haven't been able to play aq for months now
It Just happened now. Last week i've never experienced this issue
Android 10
Happening to me few moments ago
Using an android phone
Plz fix this problem it's been months now n still there is no fix for this 😟😣
Any news on this issue? It's getting annoying.
Device: Huawei p20 lite
Connection: any
Android 8.0
Game version: latest
As best I can tell it happens when we start a fight and still have time on the counter (the one to make sure we start a fight in 60 seconds):
- If the system takes a long time to then start that fight (eg if I start one with 15 seconds on the counter but the game/server takes OVER 15 seconds to start) then it dumps me back at the map and takes the 50% off my current champion. I don't know why the delay - see later - but the key point is that there is a delay, more than the time on the clock.
- If, on the other hand, the game starts before the 60 seconds were up then it generally seems not to have a problem.
- It's possible that if it takes a very long time to start then it may show this bug even if it's still within the 60 seconds, but I haven't experienced that since I started measuring, only before I was measuring, so it's anecdotal.
Now there are two points here:
1) The server issues. Ever since you had that big server issue a month or two ago, it's been very slow to start a fight - 10 to 20 seconds is the norm for me, sometimes 30 seconds! That seems to have made this problem show up. Clearly, that needs to be fixed but I can see it might take time.
2) The game deciding that the above occurrence means we should lose 50% of that champion. I don't know if that's a bug or part of the existing bug/cheating prevention systems, but clearly if we start a fight while there is still time on the clock and then it fails for reasons beyond our control but rather related to Kabam's issues, we should NOT be penalised 50% of that champion. So whether it's a matter of fixing an unplanned bug (simple: store the time remaining on the counter when we press 'Fight', and then if the fight fails to start don't penalise us if the time stored was greater than zero) or temporarily adjusting your cheat prevention systems, it really shouldn't be that tough to solve, at least until you fix the server issues.
Hope that's constructive @Kabam Porthos
Any improvements?