How it works
clansnitch checks whether your current clan members use their war attacks. Members with battle activity and war attacks left on the same day appear first.
One row for each battle day
Today shows activity and war attacks so far. The war tabs show one finished day per member: the most unused war attacks, then the most battles played that day. Flagged members come first. Open a member to see every day in the selected war.
Active · war left: played today but has war attacks left. Active · missed war: played on a finished day but left attacks unused. Complete: all 4 attacks used. Missed: attacks unused on an assessed day. Not assessed: uncertain clan membership; no missed attacks charged. Unknown: not enough war data.
Wins and losses do not change this check. “Missed” means an unused attack, not a lost match.
This war, last war, and today
We show this war and the last one when records are available. During training, we show the last two wars. Training days never count.
Day 1 is Thursday, Day 2 Friday, Day 3 Saturday and Day 4 Sunday. Dates follow the game’s 10:00 UTC day boundary, not midnight. For example, a match at 08:00 UTC on Friday belongs to Thursday’s battle day.
Today shows war attacks used and all battles recorded since 10:00 UTC. Its count is independent of older history. A plus sign means at least that many battles; “No data” means the log could not be fetched. Activity triggers a warning as soon as it is visible with war attacks left; the day does not have to end first.
During reset, the API may temporarily report the previous period. Finished-day checks exclude matches between 09:30 and 10:15 UTC when their day is uncertain; they cannot create a same-day flag. A completed war uses its own closing record, not a stale live counter.
Season and week come from the war records. The current season is shown only when it follows consistently from the previous record and the live week index.
Battles played
This counts all recorded battles on the same battle day in the clan being checked, including war battles and modes the API does not identify. The mode name is not needed to prove activity. Using all 4 war attacks clears the flag, regardless of other activity. Training days and activity on a different day do not count.
When history is incomplete
War attack totals come from the clan’s war record, which excludes training. A weekly total may confirm a shortfall without identifying the day: daily results stay unknown unless the records establish them. “?” means unknown, and “+” means at least that many. Unknown does not mean inactive.
Each duel round counts as one war attack. Automatic boat defenses do not count as player activity.
The API does not provide join dates. A current roster entry or a weekly counter does not prove membership on earlier days. We require earlier clan records or battles to support membership before a day begins. Days with recorded activity in another clan or without a clan are not assessed. A first partial day is excluded; all four attacks used still confirms completion.
Past war score
Attacks used divided by the capacity of assessed completed wars. A valid counter and earlier membership evidence are required. First or partial wars with uncertain membership are excluded, unless all attacks were used. The current war and missing records are excluded.
100% Fully active · more than 75% Mostly active · more than 50% up to 75% Regularly active · 25%–50% Moderately active · below 25% Inactive. These labels describe war participation only.
The earliest recorded war is not a join date. Consecutive clan war records support continuity, but a recorded clan change or clanless period takes precedence. Unobserved membership changes may still be unavailable from the API.
Earlier clans and donations
When requested, we look for earlier clans in the player's recent battle log and check their available war records. Up to three recently observed clans are checked. This is a partial history: older memberships may no longer be visible.
Donations show weekly activity. They have no individual timestamps, so they cannot trigger a same-day warning or change the war participation score.