Actions
An action is one call the clan's policy hands to a person: promote, welcome, answer a departure. Clan suggests it with its evidence and words to send; the person decides, and makes the change in the game.
Clan never acts in the game and never decides for anyone. When the clan's policy says something should happen, it raises an action: one numbered call for the person or role who can make it, with the evidence, the rule that raised it, and the words to send when there are any. Someone decides it, makes the change in the game, and the action's log keeps what happened.
Inspect a member's recorded activity
Roster names, current members in the award races, Standing and Season, and member Actions link to the member's own page under Members, for a current member of a clan you belong to (the counts are recorded game data; the page lives inside Clan). It shows four weeks, each from Monday's reset to the next, of clan-scoped recorded battle counts and recorded donation counters, the recorded war weeks' deck usage and points, and paged battles grouped into recorded sessions. Each battle opens its full detail page. Weekly contributions and war weeks stay distinct; decks are never assigned to war days. Battle modes use the same names as the battle detail page; an unrecognized mode retains its recorded name. Roster search is kept when opening activity, returning to the roster or refreshing the page.
Battle detail is clipped to the member's current recorded stint and only battles whose participant names this clan. A returning player's earlier stint and other-clan play do not enter these counts. Donation counters are unknown for a week that starts before the current recorded stint. Earlier war weeks are omitted; weekly totals crossing the stint or fixed read boundary remain unknown rather than being split into days. Missing or failed coverage reads remain unknown. Profile-counter intervals ending in the last seven days can show missing battles, but do not prove that the entire displayed window was seen. No recorded battle is not proof of no play. Saved Action evidence retains its original timestamp and policy version; the activity view is a new read. Removal eligibility is always checked against current profile readings.
The kinds
| Action | Goes to | Words to send |
|---|---|---|
| Promote to Elder | the leader and co-leaders | clan chat |
| Demote to Member | the leader and co-leaders | clan chat |
| Remove from the clan (the inactivity clock) | the leader and co-leaders | a line for clan chat |
| Classify a departure | the leader and co-leaders | optional farewell after classification |
| Share a newcomer’s introduction | elders, co-leaders and the leader | the published Timeline paragraphs |
| Going to be away? | the quiet member alone | none |
| Share this week's award standings | the leader and co-leaders | clan chat, with a durable Inbox alternative |
| Announce the season's awards | the leader and co-leaders | clan chat, with a durable Inbox alternative |
| Tell the clan how it runs | the leader and co-leaders | clan chat, with a durable Inbox alternative |
Award announcement titles name the season and the awards covered by that message. A manual award granted after an announcement was completed can raise a separate Action for that later recipient; the completed announcement stays unchanged. A leaders' pick in the season still being fought raises its announcement at once; the season's announcement at close leaves out any pick already sent. Notification mail uses the same award scope as the Action.
Every kind but one is off until the policy turns it on. Promotions and demotions come with ranking Elder by participation (Standing); removals, departures, welcomes, away questions and the two announcements each have a switch of their own. Award standings have no switch: they come with the clan's awards.
When one appears
Clan reads the clan every morning from 11:00 UTC, and again when someone opens Standing or chooses Refresh suggestions in Run › Waiting. The Timeline and Waiting normally open the saved evaluation with its as-of time, keeping decisions quick; its first reading or a changed policy also evaluates the record. A member has at most one open action of each kind. An action that stops being true is withdrawn, with the reason in its log: the member left, played again, or rejoined; a welcome waited a week past the join.
- Elixir introduces each newcomer it sees join in Clan news. The introduction can recognize an earlier stay, a favorite deck or a recorded achievement. An eligible clan gets an Action to share those same paragraphs in chat.
- A departure is raised when someone leaves and no removal action explains it, because a leave and a kick look the same in the record: say which, so the clan's history knows. A removal marked Done explains the leave and raises nothing. If the member's removal Action was still open when they went (a leader kicked them before marking it), the departure still asks, but it names that removal ("Elixir recommended removing them in Action #N") and offers Kicked first. Nothing is recorded until a leader presses it, and Left or Ignore stays open. The removal is withdrawn, and its withdrawal and History point to the departure.
- Going to be away? goes to a member who has reached at risk on the inactivity clock, asking them before anyone else is.
- An announcement is raised when a season's awards are decided, when a leaders' pick is granted, or when the leaders save a new version of the policy.
- Award standings are raised after a war week closes, when the clan has at least one award set up; a leader can also ask for the current season's standings from Standings.
Deciding one
Open an Action to read its reason and numbers, then its folds: What this comes from, its message, and History, the saved log and comment form. The buttons come last. These labels do not change which decisions your role may make.
The Timeline lists what is waiting for you first. Once an Action closes, it leaves your list. Closed Actions are for the leader and co-leaders: they have Waiting and Decided under Run, every decision, newest first. Its Who came and went shows recent recorded roster changes, capped at the newest twenty events, rather than the entire history since roster recording began. Earlier changes are not listed in that section.
| Action | The choices |
|---|---|
| Promote, demote, remove | Confirm the change you made in the game, or Decline with a reason |
| Departure | Kicked, Left or Ignore, with an optional note |
| Welcome | Copy for clan chat, Mark paragraph sent, or Skip remaining sharing |
| Announcement | Done, once the message is marked sent, or Decline |
| Going to be away? | Mark me away, or I'm not away |
After promoting the member in the game, review their tribute and choose I promoted them. Clanmates can read it immediately. Share it in chat when you choose. Each paragraph has its own copy button and send receipt. Elders can share welcomes. Leaders and co-leaders handle role changes and departures.
After Done, Clan watches the record: if the role change or the removal shows up within the clan's outcome window (48 hours to start), the log says it was confirmed; if not, it is flagged. After a Decline, the same kind for the same member waits before it can come back: a week for a removal and two weeks for a promotion or demotion, to start, or what the clan set.
Every action has a log: when it was raised and by which rule and policy version, every comment, every draft, the decision and the outcome. Anyone who can see it can comment, up to 1,000 characters. A Drafted by the clan's model entry keeps what the model wrote, exactly as it wrote it, before anyone edited it. Only the leader and co-leaders see those words; an elder or a member who can see the action's log sees that a draft was made, not what it said. An older draft's entry has no words.
An award standings update has one numbered Action containing every message in order, in compact game copy; as-of times and coverage stay in the app for review. Edit and copy a part, send it in the game, then choose Mark message N sent. Copying alone records no delivery. Each receipt keeps the actual words, sender and time; retries preserve it. Done becomes available after every part is marked sent. Decline closes the update, skipping the remaining messages and keeping parts already sent. A failed Elixir recording can be retried by the original sender without sending the game message again.
Each part records its chosen channel and exact reviewed words. An interrupted reply asks you to check the saved receipt before retrying; it never resends the game message. Mixed chat and Inbox deliveries keep their separate receipts. Review later · leave open returns to the list without completing or declining an Action. It does not schedule a send or change a clan decision.
Verified leaders and co-leaders can open a declined Action from Decided and choose Reopen action. It returns the same numbered Action to Waiting, keeping the original decline in its log and retaining any parts already marked sent. Completed, withdrawn and fully delivered Actions cannot be reopened. Reopening keeps the original evidence and does not send a message.
The words to send
A Clan Leader Message is the game's leader message: only the leader and co-leaders can send one, it has a title of up to 24 characters and a body of up to 180, and appears in members' Inbox, separate from chat. Routine messages default to Clan chat, where members normally talk. For award standings, final award announcements and important rule changes, choose Leader Message when you want members to keep it in their Inbox. For a welcome, role change or departure, copy the published Timeline paragraphs into clan chat. Each fits one game message. Each field counts characters and warns about known chat-filter problems. Copying a field waits until its text fits; your edits stay in place to shorten. Nothing is ever posted for the clan automatically.
Every chat field is a separate send, bounded to 200 characters; a long heading and body can require two fields. A merged game chat bubble does not establish a larger single-message limit. Channel choices keep separate edit buffers in this browser tab, including across reloads and ordinary refetches. A changed Action context starts a new draft; closing the Action or signing out clears its local draft words. Copying records no delivery.
Leaders report a limit of one Leader Message per day. Elixir cannot see sends outside these Actions or determine the reset rule, so it never predicts remaining capacity or disables delivery from completion history. Choose which important message to send first and leave the others open until the game allows another. Approximate reports describe busy chat aging out in a day or two and Inbox messages lasting longer; these are not retention guarantees.
Check the game text after sending. A delivered Inbox message can have its body masked with asterisks, and may have consumed the daily slot. Known text warnings cannot guarantee readable delivery or identify every filter trigger. Elixir cannot verify game delivery or readability and never automatically resends. Completed decisions and saved receipts do not change.
Older lifecycle Actions keep the drafts and delivery choices they originally offered. For those Actions and for announcements, with the clan’s own model set up under Run › Model & voice, an open message, welcome or removal action offers leaders and co-leaders Draft in our voice. It uses the clan's Anthropic key to draft a promotion, demotion, awards announcement or policy-change announcement, a welcome, or a chat line to use after a removal decision. After a leader confirms Kicked or Left, the departure Action can also draft a respectful departure message or farewell. A recorded departure alone does not say which happened; an unconfirmed or ignored departure has no voice draft.
The model is told what Elixir records, so the words can be about this member and this clan rather than anyone's:
- The clan: its name, its recruiting words and declared goals, its member count and its last few finished war weeks (place and war trophies).
- Elixir's own words for the Action, the ones the card shows with no draft. A draft says at least that much, then more of the member.
- What happened: the Action's own evidence in plain words. For a promotion, what the rules counted (war decks, donations, time in the clan) against the policy's bar; for a demotion, only that the Elder moves back to Member for now, never why; for the season's awards, each award with its winner and number; for a policy change, what the policy now says; for a welcome, the frozen return or recorded career detail with when it was seen; for a confirmed departure, the leader's classification and the recorded tenure.
- The member, by name: trophies and best, arena, career wins, collection level, time in the clan and any earlier stint, their recent war weeks as decks used and points, their recent moments in the clan's timeline and the awards they hold here. For a demotion only their time in the clan and the awards they hold. For a removal or a departure only their time in the clan and the weeks they played: never their trophies, a week they missed or why they were removed.
- More of their record, when the draft is about one member: every
war week they played in the clan over the last year as decks and
points, with their best week and their longest run of weeks in a row;
their donations here week by week over the last 12 weeks, and in their
career; from their game profile, years playing, favourite card, cards
at the top Mastery level, legendary badges, their best Ranked
league by name in a season Elixir recorded (Ultimate Champion, the top
league, also from the profile's own best when that season is older
than the record) and their Clan War Wins badge; their decks over the last 28 days, each
mode on its own, named by archetype with games, wins and losses; their
milestones over the last 28 days; and their role changes here. Elixir
then picks up to four story angles from it, strongest first, and every
number in an angle is in that record. Reaching Ultimate Champion leads
a welcome's or a promotion's angles.
- A demotion is told only what they gave before the policy's recent weeks, so the message can thank them for it: never those weeks' numbers, a zero, a missed week or how long it has been.
- A removal or departure is told only the war weeks they played.
- A promotion or a welcome is told all of it.
- The clan's voice: How our messages sound, as its leaders wrote it (below).
- What you ask for in What should it say?, as you wrote it.
Never sent: a tag, a note saved on the Action (yours or another leader's), a hold, a removal's rationale or inactivity numbers, a member's share of the clan's fame, or anything the record does not hold. A fact the record lacks is left out. A draft says at least what Elixir's own words say, then two to four facts that belong to this member, each said for what it means, one to a sentence. It never judges a member (no score, rank or standing) and gives no advice on how to play. A demotion thanks the member for what they did before and never says or hints why.
In clan chat a draft is lines, each its own send of up to 200 characters: up to three for a promotion, two for a welcome, a demotion or a farewell, and one for the words after a removal. The card shows a field for each line, with its own copy button; completing a welcome records every line as you edited it. An awards or policy announcement keeps its heading and message. In the Inbox a draft is a title and a message; it aims for 150 characters of the message, short of the 180 leaders report the game takes, because that limit is reported, not published.
A draft is marked for you to check before sending when it carries a number or a name the model was not given, says less of the record than Elixir's own words, hints at why in a demotion, or has a line the chat filter may mask or that runs past the limit. It is still your draft to edit. The model never decides whether to promote, demote or remove anyone. Drafts are bound to the Action's context: a changed confirmation or frozen detail clears older words and rejects an in-flight result. A careful draft can take longer than one request; the page keeps asking until it lands, for up to about 100 seconds.
The clan's saved words in Recruit say what it is about, and How our messages sound in Clan settings says how it sounds: the leaders' own words, given to the model as written. They set the tone and the wording, never the facts: everything above still holds, and a voice never lifts a rule or adds to what is sent. The clan's Discord activity editor reads the same voice. For a welcome or a farewell, choose a tone and add a short note in What should it say? on what to stress; the words after a removal take only a tone; a promotion, a demotion or an announcement takes the note. Review and edit the answer. Put back what I had restores your previous words. Elders can edit and copy welcomes without using the clan's model. Drafting completes no action and sends no game message. While a draft is loading, copying and action decisions wait for it to finish. Review the returned words before sending and marking the action complete.
When a call's outcome is unknown, that attempt counts toward the daily limit. Check the use log under Run › Model & voice before requesting another draft; Elixir does not automatically repeat it. The daily use limit is not a dollar cap. The use record counts attempts; an unknown result is not confirmation of a provider charge. Review your provider's usage record for billing. The worker checks for an existing reply before starting a request. A missing reply or claim is confirmed separately from denied access; a denied read of an existing object still fails without starting another model call.
Who sees what
The Timeline lists what is waiting for you. You see the open actions that are yours, by your name or by your role, and no others: another's action number, or a closed one's, answers that there is no such action. Only the leader and co-leaders see closed actions. Nobody below co-leader ever sees a removal action or who is on the clock, and nobody below co-leader sees a promotion or demotion before it's done: not here, and not in the clan's Discord, where none of these is posted (Actions in the clan's Discord). The leader and co-leaders also have Decided, under Run, every action the clan has had with its outcome, and the holds.
Everyone opens a clan on the Timeline (Finding your way).
You need a verified player to decide or comment; until then you can read your own actions.