How to track missed war attacks in Clash of Clans (the game deletes them)

Ask a leader what they wish the game did and this is almost always the answer: show me who has been missing attacks. It sounds like a feature request. It is actually a data problem, and understanding it is the difference between solving it and buying another tool that cannot.

What Clash actually keeps

There are two things people call war history and they are not the same.

The war log survives. Everything that identifies a person survives only while the war is running. Once it rotates, nobody — not you, not a bot, not Supercell's own API — can produce the per-member attacks for that war again.

Why the usual workarounds fail

Screenshots

They work exactly once. They are taken by whoever remembered, they live in that person's gallery, they are impossible to search, and the moment the argument is about a pattern across two months rather than one war, they are useless. A screenshot proves a night. Leadership problems are about habits.

The spreadsheet

Better, because it aggregates — and it dies for a reason that has nothing to do with spreadsheets: somebody has to type it in after every war, forever, unpaid, while also playing the game. Every clan that has ever run one can tell you the month it stopped being updated.

Memory

Memory is not neutral. It over-remembers the loud member who missed once and under-remembers the quiet one who has missed six times, and it always favours whoever the leader likes. This is the real reason to write it down: not distrust of the members, distrust of the recollection.

What a missed-attack record needs to contain

Counting missed attacks alone produces a number that is unfair to anyone who has been in the clan longer. Four usable fields, per member:

1. 1Attacks used over attacks available. A rate, not a count — otherwise a two-year veteran always looks worse than a newcomer.
2. 2Wars considered. The denominator, shown openly. A rate over three wars is a rumour; over twenty it is evidence.
3. 3Average stars per attack. Separates the member who shows up and fails from the member who does not show up. Those are completely different problems with completely different fixes.
4. 4Recency weighting. Someone who was unreliable in January and perfect since should read as reliable now. Without this, the record punishes people for improving and they stop trying.

That is exactly what the Reliability Score in RushCheck's clan manager is: attack rate, missed attacks and average stars, weighted towards the last three months, and marked provisional until there is enough evidence to be fair on that member.

Do not forget the raid weekend

Missed war attacks get all the attention because a war has a visible loser. Unused clan capital raid attacks are quieter and cost more over a season, because they compound into capital gold the clan never earns.

They are also the easiest thing in the game to skip without anyone noticing, which is why capital raid attacks are tracked per member per weekend, with a repeat-offender tally across seasons — and why they count towards the same reliability number rather than sitting in a corner of their own.

Chasing without becoming the nagging leader

A record is only worth keeping if it changes something before the war ends. The failure mode is the @everyone message in clan chat, which is read by everyone except the two people it is for.

• Message the individuals who are short, not the clan.
• Send it with hours left, not minutes. A nudge at hour 20 recovers attacks; a nudge at hour 23 is just a complaint.
• Say the number. "You have 1 attack left, 4 hours to go" gets an attack. "Please attack" gets nothing.
• Keep the tone yours. In the manager you write the template once and the details fill themselves in, so it still sounds like you and not like a bot.

Turning the record into a decision

Evidence exists to make three decisions easier, and it is worth being explicit about which one you are making:

Strikes are worth issuing with a written reason and a revoke that leaves the log intact, so a pattern stays visible even after the strike is served. The point is not punishment — it is that the fourth strike conversation should be able to reference the first three.