The inactivity clock

The days since a member's last recorded battle, and what happens at the day the clan set.

The inactivity clock

When the clan turns on Suggest removals, each member has a clock: the days since their last battle in Elixir's record, or since they joined if they have not battled since. A rise in the battle count on their profile between two reads is play too, so it can only move the clock forward. Logging in and collecting rewards are not battles. The clock passes getting quiet, then at risk, then the policy's removal day, each a number of days without a battle. On the removal day (plus any grace for meeting the minimums) the leader and co-leaders get a Remove from the clan Action; a member at risk is asked Going to be away? first, when the policy asks quiet members. The leader, co-leaders, members on a hold and, unless the clan allows it, Elders are shown as protected on Review and are never put up for removal.

The clock waits only when it cannot be read: Elixir could not read the member's activity just now, the player is no longer in the clan, their battles are not recorded, or there is no battle or join to count from. The next run reads it again. Missing days of profile reads do not hold it.

A removal Action says what it rests on. Its Rests on row names the member's last recorded battle, with its time and mode (or that no battle is recorded), when they joined (or that they were in the clan before recording began), and what the battle count on their profile did across Elixir's reads: when it last rose, that it did not, or that it was read too few times to say. Under it, every removal says: modes the battle log does not carry are not seen, so the leader weighs it. The clan's Discord names only the Action and the member, with a link to it. The morning email adds one line: the days without a battle and the removal day, then that caveat when it fits. A removal raised before this row existed keeps its saved evidence and still carries the sentence.

A removal Action is withdrawn at the next evaluation when the member plays, with the reason in its log; its number, evidence and earlier decisions stay recorded. Every time a removal is opened, drafted, completed or reopened, Clan checks the current record again. A removal that no longer qualifies says so, and withholds its copy, model drafting, completion and reopening; leadership can still explicitly Decline it.

Review counts members under removal four ways: protected by their role, a hold or the waiting period after an earlier decision, not close, too little to go on, and past the removal day. Protected roles and recent recorded play do not become removal cases just because some coverage is incomplete. These labels keep evidence quality separate from relevance; they do not relax the current-evidence checks on an Action. Review counts too little to decide Elder, for promotion and for demotion, separately from removal; one person can count in more than one. The chips below those counts jump to each section of the board.

Two things shield removal eligibility while active:

• A hold, set by the leader or a co-leader on a member who said they will be away. Silence is not a hold.
• An away notice, set by the member under Away, up to the number of days the clan allows. Leaders see it beside the member's name. It waits until the member's player is verified.

Neither resets the activity anchor nor subtracts held time from elapsed time. After it clears or expires, the current evidence and policy are assessed again.