For the 2nd War in a row, we have a terrible mismatch! The War we just finished only 13/25 players had a chance of winning against any of the ENEMY TEAM! Since 20+ of the TEAM was inactive, we did win thanks to TEAMWORK! The Enemy Team has lost 9/10 WARS!

The TEAM we are against this time is “alcolisti dichiarati”! They have lost all 10’oftheir last 10 Wars! They have 2-5 active players in each War! Statistics below!

US: Ranked #3548 (which makes no sense at all)! Won 146 Wars with 6,733 WAR COINS in 90 Days. We have 25 players ranging from Level 25 to 111 with 13 below Level 50! Our MP goes from 449 to 85.6k!

THEM: Ranked #6377 (which seems low for their monsters!) Won 92 Wars with 1,415 War Coins in 90 Days! They have 27 players from Levels 55 to 100. Their MP goes from 2807 to 24,294! Their DEFENSE BASES have 8 with Triple 100 monsters with 5 of those with one monster 105/110/111! They have 4 BASES with 2 Level 100s with a 3rd Monster & 7 monsters with 2 Level 100s! Their only Base that is not like that is 70/70/80! Only 8 of our players have a chance of defeating any of these BASES! We have another 17 that cannot!

Your algorithm is definitely broken!! My way of thinking is if a player has not played in 12 Wars, they should be removed by SP from their TEAM & if they still are not active, they should have their account deleted after 30 Days! This isn’t fair to TEAMS that keep active players!

Don’t get me wrong! We will defeat this TEAM because of their lack of participation BUT we keep losing new players because they cannot play!!

@Jane-Worthington-Vaughan My team runs into the same issue sometimes. The only real way to deal with this is to narrow the gap between top and bottom players. That is easier said than done. We have worked for a long time on our team slowly leveling up and changing our recruiting from accepting on anyone, so only accept people with MP of at least 1500, then 3000, now upping it to 4500. We will probably play with this for awhile going back and forth between 4500 and 3000 when we REALLY want to fill a slot. But on the whole most of our matchups have not been too bad.

Lastly, they purge a person's account because they went inactive. There are plenty of people that I have heard from that stopped playing for a while, but then came back to the game. They would not want to start over, especially if they tied their account to Facebook.

@Jane-Worthington-Vaughan

Your algorithm is definitely broken!! My way of thinking is if a player has not played in 12 Wars, they should be removed by SP from their TEAM & if they still are not active, they should have their account deleted after 30 Days! This isn’t fair to TEAMS that keep active players!

I get you are frustrated with this kind of match up but the solution you suggest isnt a realistic one there are teams that war sometimes and some of them are only to swap cells or do nothing I dont know but they can do what they want.
I dont understand why you dont have a war agains their 25 but that sounds more like a bug then a mismatch.
Also deleting account after 30 days of inactivity, SP would be suit for that and rightfully so.

I only have 11 of my 25 players that can win any attacks! That doesn’t seem very fair to the other 14! Any of our players over Level 30 have “grown up” over the last year on the Team! We are now only replacing 4-5 at a time & fighting with 25 rather than 30! We require new players to attack at least once in the first 3 WARS then they can request Cells in the 4th War! I’m sure most of you have had the player as soon as War starts requesting Cells! We give them 1 War I gotta then kick the 2nd time they do it! It’s part of our TEAM DESCRIPTION so it should be no surprise!

Well maybe not delete the account completely but put on an inactive status & off the Teams that have so few active players! If a player is inactive on ours & there is no explanation & they have been with our TEAM less than 5 WARS, we kick them 2 hours before the WAR ends! We lost this fact at least 5-10 times in PREPARATION DAY & ATTACK DAY!

Closing this topic, there are several already discussing the mismatch problems. Please use the search feauture to join existing conversations.