Alliance War ending issues [Merged Thread; Title edited for clarity]

Brutus2099

So in a 13 min period placement happened, war began and finished?

Comments

So what happens if a rewards email is sent and people claim it, I havent seen it yet but it could happen. What happens to those who claim it.

It did happen, my alliance already got them

SundayRed85

Happened to my alliance as well. We just lost a war match with an alliance we were never even matched with.

Olo66

Nicoluc24

Shortest war in history. Now missed next enlistment. At least ‘won’ the 5min war

Robmpaul90

How did we just finish a war 4 hours ago but another started and we lost just that quick??? That's not right something really messed up happen here.

Olo66

Guys something just happened.could you explain me what is going on? ...

KristianoRae

Literally 30mins ago we were waiting for matchmaking to begin, when all of a sudden a war was found, 2 minutes later it begun then 2 minutes later ended. Not sure on exact times but it all happened pretty quick. We got a loss and lost 100 positions in G2 tier. In Alliance Quest my first fight booted me from the game. Logged in with 25% HP. Third fight same happened. Please fix this issue and we would like and deserve compensation and the 60 war points we lost for the glitchy defeat. Also some AQ pots to compensate for all the deaths the game has caused would be really nice.

Same for us as well.

Happened to my alliance as well. We just lost a war match with an alliance we were never even matched with.

Have you been unenlisted in the next war matchmaking as well?

KristianoRae

Bugmat78

Same for my alliance. 5 minute placement phase and 3 minutes attack. Instant defeat!

Also noticed earlier the 3-day item use read as "2-day" and the 7-day SA read as "6-day". Seems to be a glitch with the server clocks!

Devender

Happened with us as well. But we won

KristianoRae

Bugmat78

Same for my alliance. 5 minute placement phase and 3 minutes attack. Instant defeat!

Also noticed earlier the 3-day item use read as "2-day" and the 7-day SA read as "6-day". Seems to be a glitch with the server clocks!?!

Furrymoosen

Keep in mind guys that you haven't missed the "next enlistment." The matchmaking phase for this war takes 4 hours, the bug just circled those effected back into that matchmaking phase (which still has 2.5 hours left) but since we "completed" a war we are no longer enlisted for this one. It isn't affecting the next one because we are still several hours way from the enlistment period for it. Either way hopefully none of this will matter because they should shut the season down. Last time they shut it down the game was down for 12 hours. This is essentially a 48 hour war shutdown.

KarolinensBön

Yeah we got the same thing in my alliance too. We lost the war even one of us did not participate the war . Guess this is some kind of bug that needs to be fixed

OldMan73

We won but didn’t get any rewards

KristianoRae

@Kabam Zibiit @Kabam Vydious @Kabam Lyra @Kabam Porthos

RonD9

that stinks....

Nicademuz84

Another Season Gone Wrong... End it while you aren't too invested time wise. Speed up the reward delivery this time around. Roll back to end of last season ranking, and just give those tier rewards. Start up another in a week, problem solved. @Kabam Miike

Forget that... We were gold 3 last season and worked our way to gold 2 so far this season. Just end the season where everyone was at the end of the war that was supposed to end today.

JVoorhees

I thought I was seeing things as well. I was running some EQ then Placement popped up for 3 minutes...next thing you know it was the Attack Phase. I hopped in w/2 star champs & won

- Also got rewards*

Brutus2099

Keep in mind guys that you haven't missed the "next enlistment." The matchmaking phase for this war takes 4 hours, the bug just circled those effected back into that matchmaking phase (which still has 2.5 hours left) but since we "completed" a war we are no longer enlisted for this one. It isn't affecting the next one because we are still several hours way from the enlistment period for it. Either way hopefully none of this will matter because they should shut the season down. Last time they shut it down the game was down for 12 hours. This is essentially a 48 hour war shutdown.

While that is technically true, the effected alliances will miss out on a substantial amount of points which in turn effects overall leaderboard

Brizzley_34

This is just insane

BigBoiKilla

Baseballs14d

Keep in mind guys that you haven't missed the "next enlistment." The matchmaking phase for this war takes 4 hours, the bug just circled those effected back into that matchmaking phase (which still has 2.5 hours left) but since we "completed" a war we are no longer enlisted for this one. It isn't affecting the next one because we are still several hours way from the enlistment period for it. Either way hopefully none of this will matter because they should shut the season down. Last time they shut it down the game was down for 12 hours. This is essentially a 48 hour war shutdown.

My other alliance was not effected, and will run war regularly. The problem is while they get full season points for war this round, my other alliance will only get a fraction of the season points. Even losing we would’ve gotten 5-600k more points for this day of war.

Drkara

My alliance also affected

Fantasy_91

Guess the question is... is everybody getting this error? So basically if nobody placed defenders or explored they got a tie and lost out on all pts from the war towards the season (not even getting the 50k for the win bonus. While those that were quick enough to place or attack...half of those won getting 50k+ while the other half lost with no or little season pts. That would be more than 50% at a disadvantage for the season. And the bigger question, has it been fixed so those that will be matched later during the matchmaking window still get a full AW to steamroll over the alliances that had the glitch?

The only saving grace from not being put back into enlistment during the rest of matchmaking is that any bugged ally cant win multiple AWs during this messed up matchmaking period.