**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
Comments
If not, we'll be missing out on 10 defenders for the week.
Can’t place defenders or join War AGAIN because of “Super Lame” Raids week. Really proved me right on that one, considering you STILL haven’t owned up to this bug. Code the game correctly already.
Glad Kabam was proactive on fixing this…
We are trying different things to see what could be causing the bug but honestly it's pretty poor that there's been no fix since it was raised last season with the really unfortunate thing to happen to SGA nor has there been any communication around it either.
It affects alliances very badly no matter where the alliance is at or its goals. An update on this is needed urgently.
So this is still not fixed and penalizing players who can place defenders, attack to help win, using resources, and kill the fair start between alliance vs alliance. This is absurd - Kabam.
There is a mile long thread addressing this CRAZY tactic which needs to be NERFED IMO. All of the suggestions and actual feedback to consider are there and yet nothing but silence much like this current in-game issue.
So combine the tactic causing players to quit for whatever reason or leadership to replace players. All done before matchmaking - not our first rodeo. The Kabam Support Team can’t seem to help resolve these issues - developers - social media & other platform voices just aren’t delivering any actual meaningful change to fix these issues.
Handicapping an alliance for new players before matchmaking and to compete when round starts is absurd. Leadership asking other players to stay - support - try harder with 9 or less to win is outrageous. We aren’t competing anymore - this is completely out of the players and Leadership (Officers control).
My alliance is in this boat right now and despite tickets are in - we are living on a MCOC prayer. Our Masters run may just be gone now. Every round - every player - every defender - every attacker is needed to start the round 100% vs another alliance. Otherwise the efforts are extremely difficult to ask all not penalized to push - stay positive - etc.
I feel the stress and how powerless of others now - because it has happened to my alliance. Super pissed how this impacts the odds to favor an unknown opponent before the round starts - and hear suck it up.
This issue is something the gameteam has been working on, behind the scenes. Apologies for not being transparent about that sooner.
It appears they have a good idea what's causing the issue and are on the road to fixing it.
A temporary, less-than-ideal workaround is as follows:
Have new Alliance members wait for the next matchmaking period, afterwards they should be able to join any future wars.
More news as we receive it.
Or are you providing an assumption something unknown may be ready after Round 4 to fix future Round 5 and so on? Which means all alliances with this BUG from low to high tier will still be penalized to play handicapped for Round 4 likely resulting a guaranteed loss.
The message versus intent received is causing concerns for players who are just trying to play for an alliance to achieve Team goal. This bug is putting a risk to it and potentially causing a collapse in alliances in which players decide to leave for things outside of their control. A domino effect.
Trying to prepare for the worst if this bug doesn’t have an actual fix before Matchmaking starts in a few hours for Round 4.
Kind of nuts considering the about of time between war ending and the next war match.
This is basically what had been recommended “prior to Raids” ever since Persistent Defense was added.
And that had already been mentioned at the start of this newer Raids-Specific issue. (although some contend that it only first started with the beginning of Raids).
But apparently, the Raids factor seemed to compound that “already existing” problem of new people joining Defense. And Raids somehow interferes with those new people for the entire duration of Raids Weeks (all 3 wars)
This issue is something the gameteam has been working on, behind the scenes. Apologies for not being transparent about that sooner.
It appears they have a good idea what's causing the issue and are on the road to fixing it.
If this is the case - it only seems fair to CANCEL the season. Alliances that can’t play with a full alliance shouldn’t be penalized or just forced to deal with this bug. If this is not reasonable - then what is Kabam’s proposal knowing of this issue prior to Season 48 starting and a new tactic.
Alliances efforts to recruit and players efforts in prep on resources plus both sides making decisions on playing together is tremendous. A BUG like this which is now known that is “a larger issue that will require a larger solution” sends a STRONG message and warning to all alliances.
If players who experience a life changing event and needs to walk away from the game and does this with the time windows to replace that player as we have prior to this BUG, puts the entire alliance efforts and AW finish at risk.
Thank you for communicating this BUG is problem that requires more time for a quality solution. I ask so now that this known - what course of action will Kabam take on this BUG?
I’m looking for a positive/ optimistic answer to provide my guys. Hell - I’m preparing to watch our alliance collapse and also hope to keep 29 committed based on the responses we have to go by as of now.
Pretty simple to me - CANCEL this season. I can’t even figure out a reasonable solution fir last season alliances being impacted.
Compensations are frowned on but this sure seems like a valid reason to step up and do the right thing by Kabam.
Let the planners, players skills, strategy, and those infamous in round adjustments deliver a WIN or a LOSS. Either way it the result is because one alliance did all the things it takes to WIN with no excuses or factors outside of their control.
In this case - a BUG that cripples for multiple rounds. I’m not supporting to tell, joke, troll players you picked the wrong alliance - shouldn’t have left etc.