AQ issue


I'm confused here lol, seen this in another thread that was closed. The support team admitted to have a fix for this issue, and it's supposively gonna be fixed pretty much before the next alliance quest. Then why is kabam hitting us with that bs?
0
Comments
Idk if it's just me, but it sounds like if there were less alliances affected they wouldn't push for a fix as quickly as they have now.