AQ issue

ForumGuy

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?

ForumGuy

Also, reading this one more time. It says, "while not all alliances were affected, enough were affected that made this a serious concern and we wanted to be thorough in fixing this."

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.