What changed, newest first. Open one for the whole entry.
Elixir's worked-examples tool can return either its index or one complete example. Both responses already carried the right information, but the published schema incorrectly said every response had the index. It now describes the two forms correctly, so a cli…
Read it ›Programs reading Elixir's JSON API can now read a clan's recorded war weeks, the same record war_history gives an agent: each week's final rank, boat fame, war trophies and trophy change, over up to twelve seasons. The roster adds what the clan asks of a join…
Read it ›elixir_examples now declares both answer shapes correctly: its index has examples, while a selected example has its transcript and supporting details instead. The responses were already correct; this patch removes erroneous output-schema mismatch logs.
Read it ›clans_roster carries required_trophies and donations_per_week, the clan's own figures from the same newest roster read as its scores, at both verbosities.
Read it ›Elixir Clan, where a clan's leaders run their own policy against the record, has moved from its own address to elixir.poapkings.com/clan, beside the site and the console. A clan's page is /clan/ followed by its tag, and the Clan button in the bar at the top g…
Read it ›The console has moved under one address of its own: your account overview is now /console/account/overview, and every other console page sits under /console the same way. The old addresses at the root no longer open it, so update any bookmark. The site, the d…
Read it ›Three fixes. The milestone mail looked back a fixed 26 hours, so if its hourly check failed for longer than that, a first from the gap was never mailed; it now reads back to the last check that went through, up to a week, so a first can be late but not lost. …
Read it ›An agent acts only while its owner has access. Until now, withdrawing a person's access stopped their own sign-ins and connections but left the agents they own working; now their keys and connected apps read as invalid too, and work again if access returns. A…
Read it ›The privacy and terms pages had grown into long documents that promised more detail than a hobby service can keep current. They are now short and plain: Elixir is a free service, built as a hobby, for folks who like the game; it keeps public game history and …
Read it ›Since participation began listing the members who left and everyone's place at each war finish, the eight-week read of a full clan had grown past what an agent's answer may hold, and it refused. The agent's read is now a table: the column names come once inst…
Read it ›An agent reading your timeline had no way to know it had already told a story: the same sitting read at two different times came back as two different items, and a sitting that grew from 20 battles to 40 looked like news or a repeat depending on the read. Eac…
Read it ›Unlocking a card's Evolution or its Hero is the collection change players care about most, and the one the upgrade advice points at, but Elixir only kept which forms a card has and let the unlock pass without a word. From today it is a named moment: the timel…
Read it ›A clan's participation read used to apply today's roster and roles to every past war week, so a member promoted last week looked like an Elder all along, and a member who had left was simply missing. Each member now carries whether they were in the clan and t…
Read it ›A friendly with a clanmate often runs under an event's rules, and the game tags it with that event. Elixir had filed those friendlies as event battles; they now count as casual play, like every other friendly. Battles in a timed event, such as Royale Shuffle,…
Read it ›Comparing two to four players now warns when Elixir knows one of them is missing recent battles, the same warning a single player's performance read already carried. It names each player whose latest stretch is under 90% recorded, or whose record cannot be ch…
Read it ›The card catalog listed a fifth tower troop, "Archer Queen" with an id the game has never used. It was never in the game's own catalog: a test record from the old Discord bot had been replayed into Elixir as if the game had sent it. It also listed eleven card…
Read it ›clans_participation answers the table form (9.16.0) to an agent on a service token too. 9.16.0 laid out the table only for a person's or an OAuth agent's MCP connection, so a service-token agent still read object rows and its eight-week full read still refuse…
Read it ›clans_participation answers an agent as a table (#124), so the eight-week read of a full clan with the members who left fits the response cap with room. Since 9.13.0 the eight-week full read of the recorded clan had refused with result_too_large (51,875 chara…
Read it ›Every elixir_timeline item carries id, the story it tells, and revision, how far that story has grown (#111), so an agent tells a story once, recognises it in the next read, and updates it when it grows rather than retelling it.
Read it ›An Evolution or Hero form newly unlocked is a timeline moment (#110). Until now the collection kept only which forms a card has, so an unlock passed silently.
Read it ›clans_participation says who was in the clan, and in what role, at each war finish (#46), so a clan's own rules can be replayed at a past finish without applying today's roster and roles to it.
Read it ›Event classification follows Jamie's ruling (#109). A clanmate battle (clanMate, clanMate2v2) is casual even when it carries an event tag: about 62% of clanmate friendlies do, because friends play a friendly under an event's rules. Any other tagged battle is …
Read it ›battles_compare carries meta.completeness_note, as battles_performance and battles_query do (#108). It reads the same capture control once for each compared tag, when the window ends inside the last seven days, and the note has one sentence for each side whos…
Read it ›cards_catalog lists the cards the current /cards catalog lists, 123 today, as 9.12.5 did for tower troops (#44). It had also listed eleven cards known only from battles, such as the event-only Super Archers and Party Rocket, with no rarity or cost; /cards nev…
Read it ›cards_catalog lists the tower troops the current /cards catalog lists, four today, not five (#44). The fifth, 29000000 "Archer Queen", was never sent by the game's API: a test fixture leaked into the retired elixir-bot's raw payloads and was replayed as a cat…
Read it ›Each item in the updates feed now has a permanent address: its own page under /updates. It used to carry a number that shifted every time something new shipped, so feed readers showed old items as new again, and the links went nowhere. Because every address c…
Read it ›Every record link in the console is now a real link: Cmd-click, Ctrl-click or a middle click opens it in a new tab, it can be focused from the keyboard, and its address can be copied. Buttons that do something, like Dismiss or Send another email, are buttons.…
Read it ›Every unexpected fault in the JSON API used to answer 503 with Retry-After, asking a program to retry a bug that would fail again the same way. Now only a database that is briefly unreachable, or a query that ran out of time, answers 503 with Retry-After; any…
Read it ›When two collectors handed in overlapping battle logs at the same moment, the database could refuse one of them, and that fetch was thrown away and made again later. The recorder now tries it once more on the spot, and the daily battle totals it keeps for eac…
Read it ›When a read of the game failed, the recorder used to wait for that subject's next turn: a day for a profile, and for a leaderboard or the events calendar that failed just after the 10:00 UTC reset, the whole day. It now tries again 15 minutes later, then 30, …
Read it ›The Top 100 and Card of the Week are written by a model from a brief the program builds. If the writing finished after the issue's send time, the issue used to miss its week; it now goes out as soon as it passes its checks, while it is still the current issue…
Read it ›A second milestone on the same day used to wait until after midnight, and could be lost if the mail was down then; each new first now gets its note on the next hourly check. The Monday clan report is now the same for everyone who tracks the clan: it covers th…
Read it ›The request and response of a tool call are kept for 90 days, as the privacy page says. Because the storage keeps earlier versions of a file, a call's body could linger as an old version for up to a year after that; it now goes the day after its 90 days end. …
Read it ›When an agent connects, Elixir tells it who you are and how to use the tools. That brief had grown past what some apps pass on (Claude Code keeps the first 2,048 characters), so the part about where to start and how to send feedback never reached the model. I…
Read it ›Every live read, whether your agent asks for one or an app refreshes a profile, is now counted against the same shared request budget the scheduled recording spends. When that budget is spent for the moment, a live read is not queued and costs you nothing; it…
Read it ›A read that runs long, or waits behind maintenance, now answers with a retry hint wherever you ask, in Explore and through the JSON API as well as through your agent, instead of the page or request timing out. The deck-set planners also stop at a time limit a…
Read it ›When an app asks to connect to your Elixir account, the page now shows the address it will send you back to beside the name it chose for itself, and says plainly when it is one of Elixir's own apps. Apps can now disconnect themselves with a standard revocatio…
Read it ›The opening brief arrives whole (review §6.1-6.2). instructions ran about 4,500 characters and Claude Code hands a model the first 2,048, so START, the feedback line and half the rules never arrived. It now fits 2,048 in order of value: who you are (the other…
Read it ›Every live read is charged to the collector fleet's one global request budget when it is queued (review §4.1). When that budget is spent until the next scheduler tick, live: true and live_fetch queue nothing and charge nothing, your daily live quota included:…
Read it ›Every database read is bounded (review §3.1-3.3). A read-only tool waits at most 5 s for a lock and answers query_timeout instead of holding a connection behind a migration. battles_deck_sets and battles_deck_upgrades stop their search at a 4 s time budget as…
Read it ›elixir_timeline shows a clan's leaders-only facts (a member's away) to a leader reading through their own connection; a service key on a person's account reads what the clan shares. The OAuth server gains POST /oauth/revoke (RFC 7009), and the consent page na…
Read it ›The fleet page marks each collector signed when the binary it runs is exactly a release Elixir named, and says dev build, unverified or mismatch otherwise; collectors from v3.0.4 report what they run. Beside it, the release key's fingerprint is drawn as the p…
Read it ›Collector releases are signed, and every collector checks the signature against its built-in release key before it installs an update this server names. The operators page now publishes that key and its fingerprint, a second place to check it beside the colle…
Read it ›Asking for your decks now answers with a light list: each deck's cards on one line with its archetype, its record and how you did with it, a page at a time, so a long history no longer runs into the answer's size limit. Ask about one deck and you get its card…
Read it ›Every round of a Clan Wars duel now counts as a game in the deck and card meta, for every player, not only your own: the eight cards played that round, won or lost by that round's crowns. A war deck that is mostly played in duels now shows up in the war meta …
Read it ›A Clan Wars duel is up to three games, each with its own deck, and until now the war-deck tools never saw them, so a war deck you only play in duels looked like a missing fourth deck. Your duel rounds now count as your games on each deck, won or lost round by…
Read it ›battles_decks answers a page at a time, in lighter rows (Jamie, 2026-09-26). A player's whole history at limit 30 was about 47,000 characters, next to the 48,000-character result cap, because every row carried eight card objects and the archetype object.
Read it ›The meta tools' excluded counts battles again, as at 9.10: at 9.11.0 considered counted a duel as its rounds, so it no longer matched battles_query or battles_trends over the same window (acceptance 188.3, 200.1). A duel is one battle in considered and exclud…
Read it ›A Clan Wars duel counts as its rounds everywhere a deck or card is counted (feedback #363). A duel is up to three games, each with its own deck, and as one row with no deck it was in no one's meta: a war deck played only in duels was invisible, and roughly ha…
Read it ›An award_standing item that names who held first place before carries previous_name beside previous_player_tag, and its sentence says "taking it from <name>" instead of a bare tag: a lead changing hands, which a clan's agent announces, is said with both names.
Read it ›battles_deck_sets takes exclude_decks: deck_hash values no set may choose (any variant names the same eight cards; candidates.excluded_decks counts them), so "a different last war deck" is the other three locked and the current fourth excluded. Read back thro…
Read it ›battles_decks.duel_decks is lighter: at most 8 decks, each with card_names (one string) and archetype_label in place of card objects and the archetype object. At 9.9.0 a player's whole history of duels pushed a 30-deck page past the 48,000-character result ca…
Read it ›battles_decks lists the decks a player played in duel rounds (duel_decks: each round's eight cards with its round record, most rounds first). A duel has no single deck, so it stays outside the rows and their shares, as before; but read back through a clan's a…
Read it ›The war-deck docs have their own page, war-decks (sections deck-sets and deck-upgrades), and battles_deck_sets and battles_deck_upgrades point there. With 9.8.0's text the battle model page had grown past the 48,000-character result cap, so elixir_docs({ page…
Read it ›War decks as their eight cards, duels included (feedback #363 and #364). Clan Wars battles carry no tower troop, so the same eight cards were a Trophy Road deck_hash and a separate Clan Wars one, and a deck's war record never pooled with its ladder record; a …
Read it ›Ask what to upgrade and Elixir now answers from your own war decks: starting from your best four decks that share no card, it tries each upgrade that could matter (a card raised toward the level you play at, or an Evolution or Hero you have not unlocked) and …
Read it ›An eighth email, from Elixir Clan: on a morning when something new in your clan is yours to do (promote a member, welcome a newcomer, answer a departure, say whether you are away), one note lists everything waiting for you, with a link to act. Only if you can…
Read it ›Asking a clan's daily series for a few metrics in compact form now answers those metrics, as the full form does. It used to answer the five standard clan metrics whatever you named, so a compact answer could be larger than the full one. Contract 9.2.1.
Read it ›A clan that runs its awards in Elixir Clan now shares where each race stands while the season is still running: who is first, second and third in each award, by the clan's own rules, updated every morning. Everyone in the clan sees it on their timeline, and t…
Read it ›Ask for your war decks and Elixir now answers with sets you can actually field: four decks with no card in common (an Evolution or Hero form counts as the same card), picked from decks this season's players really played in Trophy Road, Path of Legends and Cl…
Read it ›When a leader tells Elixir Clan whether a member left or was kicked, everyone in the clan now sees it on their timeline, and so does the clan's own agent, which can now say it in the clan's Discord. Until today only the clan's leaders saw it. The game already…
Read it ›An integration can now hold permission to read clans: the participation and roster reads a signed-in person already had, for any clan Elixir records. It is how Elixir Clan evaluates a clan's policy each morning with nobody signed in, so actions are waiting wh…
Read it ›The Elixir family's own apps can now tell Elixir what a person did in a clan: a departure a leader says was a kick or a leave, a promotion made, an award the clan granted, a member away, a message sent to the clan. Elixir Drop can say you set a new personal b…
Read it ›Who has played their war decks today now comes straight from the game's own daily counter, as Elixir last read the race. It used to add recorded war battles placed on the day by the clock, which could run ahead of the game and, for a clan whose day rolls a li…
Read it ›A boat defense, where an enemy attacked your clan's boat and the defense deck answered, is no longer counted as one of your battles in performance, comparisons, trends, card and deck stats, or clan participation. When a record mixes game modes, the answer now…
Read it ›Elixir no longer splits a member's war week by day. The API does not say which day a deck was played, and each race rolls its day at its own moment, which cannot be placed reliably across every clan Elixir records. Clan participation, war history and the curr…
Read it ›battles_deck_upgrades: each option now says which decks of the set it lifts (lifts: the decks whose value it raises, before and after), so an agent can say "Miner lifts your Mortar deck" without comparing sets. Read back through a clan's agent, 9.7.0 left tha…
Read it ›A new tool, battles_deck_upgrades: the other half of a war set, "what should I upgrade so my four decks get better". It starts from the player's best set of decks sharing no card today (the candidates, values and exact packing of battles_deck_sets) and prices…
Read it ›A new attested fact, award_standing: where a member stands in one of the clan's own awards for a season still running (the award's name and id, the season, the place, the value and its unit, as of when, and previous_player_tag when the place changed hands). T…
Read it ›battles_deck_sets: the one wider pass, when the default gates pack nothing, also drops the level floor. A maxed account read back at 9.5.0 still got no set: its main decks are level 16 and most of its other cards are not, so 1,585 of 1,864 season decks held a…
Read it ›battles_deck_sets answers a maxed account. At 9.4.0 a player who fields level 16 got no set: of 889 season decks, 419 were refused for an Evolution or Hero form not unlocked and 334 for a card two levels under, leaving 3. A deck played with a form the player …
Read it ›battles_deck_sets: the best sets of decks a player can field together sharing no card, the question Clan Wars asks (four decks, 32 distinct cards; a card's Evolution or Hero form is the same card). Chosen exactly (branch and bound) from decks this season's re…
Read it ›A departure a leader classified (departure_classified, kick or leave) now reaches the whole clan on the timeline, the clan's own agent included; in 9.2.0 only the clan's leaders saw it, so that a kick would never be narrated. The game already tells everyone i…
Read it ›clans_timeline with verbosity: compact answers the metrics you named, as the full read does; it answered the five clan metrics whatever was named, so a compact read of two metrics came back larger than the full one (the acceptance catalogue's two-metric seed,…
Read it ›Attested facts on the timeline: what a person did in a clan through one of the Elixir family's apps, or what a family app's own game produced for a player, held apart from the game record (which only collectors write) and labelled with who said it, in which a…
Read it ›war_current.decks_today and the timeline's clan war.decks read the game's own decksUsedToday counter for the day in progress, as the race poll recorded it. They took the larger of that counter and the member's war battles placed on the 10:00Z policy day, whic…
Read it ›The war trophies note names the field each response serves: war_history over seasons carries our_clan_war_trophies, and the note named clan_war_trophies there. It no longer names another tool's field either (the acceptance suite's notes check, on the 9.1.0 de…
Read it ›The consistency pass (Jamie, 2026-09-25): decisions that had reached one tool now reach every tool they apply to, and the war family's old names go.
Read it ›War facts are weekly aggregates on every war tool (Jamie, 2026-09-25). The API does not say which day a war deck was played, and each race rolls its day at its own moment in the half hour before 10:00 UTC, which cannot be placed reliably across every clan Eli…
Read it ›Participation keeps weekly war-deck facts and drops unreliable daily allocations (Jamie, 2026-09-25).
Read it ›Sign-ins, signups and feedback were the last events Elixir's servers sent to Tinylytics, the site's analytics. They are gone too: the servers send it nothing now. Page views and mail opens are still counted, anonymously, as the privacy page describes.
Read it ›Elixir used to count every tool call in Tinylytics, the site's analytics, by tool name. It no longer does: your call record already holds every call, with more detail, and nothing leaves Elixir for it. Page views and mail opens are counted as before.
Read it ›The meta tools now split Trophy Road into three: under 10,000, 10,000 to 13,999, and Trophy Road complete (14,000, the cap). The old five bands were finer than the recorded games could fill, and they mixed players still climbing with players who have finished…
Read it ›The version before open beta carries two changes that could break a strict client. Asking for decks played by at least two players now counts only players who played the deck more than once, so one player's long run can't be passed off as a popular deck. And …
Read it ›When the game serves an incomplete Path of Legends board just after the daily reset, Elixir now reads it again half an hour later and keeps the complete one. Every tool answer now carries its notes and a documentation pointer, a card's profile counts players …
Read it ›Asking for decks played by at least two players could still lead with one player's long run and two others' single losses. Deck meta rows now say how many battles their busiest player accounts for, and a note names any row one player carries. Contract 7.2.7.
Read it ›A full test pass over every Elixir tool family before opening to beta users found and fixed: tower troop usage for players who play war, a busy timeline that could not page past a late item, the leaderboard collections showing yesterday's board, the card name…
Read it ›When you connect an app or agent to Elixir, the sign-in page now asks which extra things it may do, in plain words: track players for you, edit your collections, remember who is talking to it, send feedback. Your own connections start with only reading allowe…
Read it ›A deck is eight cards and a tower troop, and Elixir now reads the tower troop like a card. The meta card list can show tower troops (how often each is used and how it wins, over the same players and window as the cards), and a card's page answers a tower troo…
Read it ›Training days now sit in the record as days of the war week like any other: members play the same four war decks, and training days are where they get reps in before each deck can be played only once on a war day. Rebuilt training days now split where your cl…
Read it ›The Elixir Gym's sixth run over the timeline. A clan's summary line now ends every shortened list with how many more there were, so "back:" naming three members no longer reads as the whole list. A timeline read for one member says when a play session was cut…
Read it ›Elixir now records the practice decks members play on a war week's training days. On a training day, the current race shows who has practiced and how many decks; war history totals each member's practice for the week. Practice earns no points and never counts…
Read it ›The Elixir Gym's fifth run over the battle tools. A meta, card or trends read for your clan now says that it counts the clan's members as of today across the whole window: a member who left is not counted for the weeks they played, and a new member's battles …
Read it ›The clan ladder now says where your own clan stands: its rank when it is on the board, or its clan score and how far it is below the last place when it is not. The clan roster shows the clan's score and war trophies. The game clock says whether a week is Colo…
Read it ›The Elixir Gym's fourth run over collections and rankings. A clan read for meta decks, trends, synergy or badges now counts only the members Elixir records, and says how many that is; a member seen only as an opponent's teammate in someone else's battle no lo…
Read it ›A signed-in walk of the console found, and this fixes: battle pages in Explore that failed to open, a player's deck list too large to load, war weeks that showed no rank or fame, a clan's members all reading "never" for their last battle, and the activity cha…
Read it ›The Elixir Gym's fourth run over the player tools. A player's profile now includes their latest Merge Tactics, 2v2 League and seasonal Trophy Road standings. The legacy "season trophies" fields are labelled as what they are, a mirror of Trophy Road rather tha…
Read it ›The Elixir Gym played a clan leader's first week. When an enemy attacks your clan's boat, the member whose defense deck answered did not play a battle, and those defenses no longer count as war days battled. A member who left and came back keeps their origina…
Read it ›An overnight audit of the console for a first-time visitor. Choosing "UTC (default)" as your timezone now works after another zone was set. A console tab left open across an update reloads onto the new version instead of failing to open a section. The Timelin…
Read it ›The Elixir Gym played a new user's first session. Meta deck lists can now require a deck to be played by more than one player, and say when a list is mostly one player's personal deck. Badge rarity for a single player says it is not a rarity ranking. Asking t…
Read it ›The Elixir Gym's first full run over the newsfeed timeline. A clan's timeline can now be read for one member: pass a player tag and get just their moments. Filtering by kind or section no longer shortens the feed, a member who left and rejoined on the same da…
Read it ›The Elixir Gym's fourth run over the clan tools. Standings and participation now point out members who joined partway through the period, whose counts include battles from before they arrived, and the missed-battles warning covers the period you asked about r…
Read it ›The Elixir Gym's third runs over the war and player tools. Rivals now show their points, not just their fame: fame pays for where a clan placed each day, so a rival could look strong on fame while playing a fraction of what your clan did. Player profiles show…
Read it ›The Elixir Gym's third run over the timeline. Looking back at a past window now shows the clan's war as it stood then, not the week's final result, and that week's donations from the members who were in the clan at the time. A finished war week shows the fame…
Read it ›The Elixir Gym's third run over the game tools. Asking the game clock about a date keeps every caveat it gives for an exact time, including when river races close. The events calendar names a season change inside any window you ask about, even one ahead of to…
Read it ›Three trophy bands (Jamie, 2026-09-24), inside v8 by his call: trophy_band on battles_meta_decks, battles_meta_cards and cards_synergy is under_10000, 10000_13999 or trophy_road_complete (14,000 is Trophy Road's cap: the players who have finished it). The fiv…
Read it ›players_profile snapshot.progress.current compares each bucket with the newest profile read, not the newest bucket: a player whose only side-mode bucket had ended (a Merge Tactics season last read 08-31 beside a 09-24 profile) read it as current (#329).
Read it ›The major before open beta (Jamie, 2026-09-24): two breaking changes, nothing else.
Read it ›Jamie's pre-beta follow-ups (feedback #342 and the journey r3 open questions).
Read it ›Badges, war and rankings after the pre-beta Gym pass (feedback #337-#347), and the card vocabulary.
Read it ›Cards, players and clans after the pre-beta Gym pass (feedback #324-#336).
Read it ›The consent page asks, and says what each capability is for (Jamie, 2026-09-24).
Read it ›Participation tenure is the current stint (Jamie, 2026-09-24; Gym #264).
Read it ›war_current.decks_today covers every day of the race week (Jamie, 2026-09-24): training days are the same four war decks, played for reps.
Read it ›The war tools after the Elixir Gym's fourth run on them, the first on a live war day (feedback #311-#313).
Read it ›The collections tools after the Elixir Gym's fifth run on them (feedback #308-#309).
Read it ›The clan tools after the Elixir Gym's fifth run on them (feedback #305-#307).
Read it ›Training days are race-week days like the war days (Jamie, 2026-09-24): a member plays the same four war decks all week; on a war day each can be played once and scores, and training days are reps with them.
Read it ›The timeline after the Elixir Gym's sixth run on it (feedback #302-#304).
Read it ›Training-day decks before 2026-09-24 are rebuilt from recorded battles (Jamie, 2026-09-24).
Read it ›Training days are recorded (Jamie, 2026-09-24): the practice decks members play on a race week's training days had been dropped, a holdover from elixir-bot.
Read it ›The battle tools after the Elixir Gym's fifth run on them (feedback #300-#301).
Read it ›The game tools after the Elixir Gym's fourth run on them (feedback #296-#298), and a clan's own place on the clan ladder (#294).
Read it ›The collections and rankings tools after the Elixir Gym's fourth run on them (feedback #286-#293).
Read it ›The card tools after the Elixir Gym's fifth run on them (feedback #281-#285).
Read it ›The badge tools after the Elixir Gym's fifth run on them (feedback #279-#280), and a badge stamp the players gate caught.
Read it ›The player tools after the Elixir Gym's fourth run on them (feedback #275-#278).
Read it ›From the Elixir Gym's clan-leader journey and its fifth run on the timeline (feedback #263-#274).
Read it ›From the Elixir Gym's first-engagement journey: a new agent's first ten questions (feedback #256-#262).
Read it ›elixir_timeline after the Elixir Gym's fourth run on it, the first on the 7.x newsfeed (feedback #244-#255).
Read it ›The clan tools after the Elixir Gym's fourth run on them (feedback #236-#243).
Read it ›The war and player tools after the Elixir Gym's third run on them (feedback #223-#235).
Read it ›elixir_timeline after the Elixir Gym's third run on it (feedback #211-#218), with the week-fame fix it shares with the war tools (#223).
Read it ›The game tools, after the Elixir Gym's third run on them (feedback #219-#222).
Read it ›An agent can now track more than the clan it was made for: a rival clan it is asked to watch, the other clans of a family, or a player worth following. Its console has a Tracking page for it, and an agent can also do it itself with elixir_track_clan and elixi…
Read it ›The top of the console's menu is now an account selector: you, and each agent you own. Choosing an agent opens its own console, the same pages scoped to it: its overview (its key, its last call, anything refusing it, and the address to connect it at), its tim…
Read it ›The timeline is a stream of what is new, so it now leads with what happened most recently everywhere you read it: elixir_timeline, the console's Timeline and each agent's, the moments in the Wednesday Tracking report, the joins, departures and role changes in…
Read it ›The console now shows times in the timezone set on your Profile, the zone your tools already answer in: the timeline, your MCP requests, emails and account events, a call's or an email's record, feedback, Verify, the Status page and its charts, Explore's batt…
Read it ›The console's Timeline, what happened to the players and clans you track over the last seven days, is now its own item at the top of the menu, between Overview and Explore, instead of the first view inside Activity. It lists the newest first and shows the sam…
Read it ›The Elixir Gym's third run over the ranking tools. A leaderboard now counts as moving only when someone's rating changed or a newcomer climbed in, not when a player dropped off the bottom, so a finished event no longer reads as live. Asking about a season tha…
Read it ›The Elixir Gym's runs over the collection and card tools. A missing years-played figure now says it usually means an account under a year old, not a profile Elixir has not read. Passing a clan collection where players are expected now explains how to ask abou…
Read it ›The Elixir Gym's fourth run over the battles tools. Past 14,000 trophies the game files the seasonal Trophy Road as an event, but those battles still win and lose trophies. Weekly battle counts now include them among the trophy battles played, so the trophies…
Read it ›The Elixir Gym's third run over the clan tools. A clan's weekly donation total now keeps the highest number seen that week, as each member's already did, which repairs two weeks that read 10. Clan standings and participation now name any member whose battles …
Read it ›The Elixir Gym's fourth run over the badge tools. A shortened list of the rarest badges now says how many badges it left out, and a badge that has an old and a new identifier still gives its true number of holders when only one of the two is on the page. Cont…
Read it ›Elixir sees hundreds of thousands of players, most of them only as someone's opponent. The home and data pages now lead with the players and clans Elixir actually records, with the ones only observed as a secondary line, and badge counts for a clan leave out …
Read it ›The Elixir Gym's third run over the card tools. A tournament battle records the player's score in that tournament where a Trophy Road battle records trophies, and those scores had been filed as the lowest trophy band, so "how does this card do at low trophies…
Read it ›The Elixir Gym's third run over the battles tools. Weekly battle trends now start at the time you give them instead of the Monday before it, so a last-7-days read counts only those seven days. Event battles are labelled as events, not casual play. A meta read…
Read it ›The Elixir Gym's second run over the timeline. When a long window is split across pages, continuing from where the last one stopped no longer loses a moment at the split or repeats one. Every standout session is listed, not just the first five. And a look bac…
Read it ›Elixir's JSON API at /api/v1, until now for connected platforms, admits people too: sign in with Elixir for the API, and GET /api/v1/me says who you are to Elixir and which players you track. Agents keep using MCP; programs use the JSON API, and a token for o…
Read it ›The Elixir Gym's second run over the clan tools. A player's weekly donations only go up until the game resets them to zero, so Elixir now takes a week's donations as the highest number it saw that week. A read just after the reset can no longer wipe the week …
Read it ›The Elixir Gym's second run over the card tools. A card's usage and win rate for a custom date range now come from the same population as a whole-season read, without event battles or drafted decks. The same card over the same days no longer gives two answers…
Read it ›The Elixir Gym's second run over the battle tools. The meta tools already left out event battles and drafted decks for whole seasons. They now do the same for custom date ranges and single players or clans, so a week's meta no longer mixes in a boosted event …
Read it ›The Elixir Gym's second run over the badge tools. Some badges exist twice, an original and a newer version that most players now hold. The badge tools now name both and count the distinct players holding either, so asking about Royal Tournament Rank no longer…
Read it ›The Elixir Gym's first run over the war tools. A week's war trophies are the clan's figure going into that race, and the week's own gain or loss lands in the next week's figure. The tools now say so, so a closed week is no longer read as finishing on the numb…
Read it ›The Elixir Gym's first run over the ranking tools. The global clan ladder has hundreds of clans tied at the top clan score, and the game lists them in its own order, so the ladder now says they are tied instead of letting rank 1 read as a winner. The mode lea…
Read it ›The Elixir Gym's first run over the player tools. A player's top deck no longer counts battles in decks an event handed them, and those battles are filed as event rather than casual play. The best deck now says the trophies it was played at, since a 10-0 run …
Read it ›The timeline caps a single read so it stays readable, and until now a full read quietly dropped its newest items while telling the reader to carry on from the end of the window. An agent reading on its pointer lost them for good. A capped read now stops just …
Read it ›The Path of Legends top-100 collections and the top 10 clans are rebuilt from the live leaderboard every day, so their membership changes. More than a third of the global 100 can turn over overnight. They used to call themselves a snapshot. They now say which…
Read it ›When a clan's boat crosses the finish line early, the war keeps going for the members who still have decks, but those decks earn nothing. In each of the last two war weeks, 15 to 19 per cent of the decks POAP KINGS played came after the finish, so a member wi…
Read it ›The Elixir Gym's first run over the card tools. The most useful fix: naming an eight-card deck with cards_archetype works now, where it used to time out every time. The one that changes answers: the trophy bands were quietly counting Path of Legends players, …
Read it ›A river race duel is best of three games, and the player who wins two wins the duel. Elixir was deciding the result from the crowns summed across all three games, so a duel won 0-3, 1-0, 1-0 was recorded as a loss at 2 crowns to 3. The Elixir Gym found 7 of o…
Read it ›Three things the Elixir Gym found on its first run over the badge tools. First, the date on a badge holder was when the badge last changed, not when Elixir last looked, so a clan read yesterday showed most members as untouched since early September. A holder …
Read it ›A clan in Clash Royale has two numbers that both get called a score: its clan score, a five- or six-figure strength rating a profile shows, and its war trophies, a four-figure ladder it climbs twenty at a time. The river race payload reports the second one un…
Read it ›Elixir has always recorded both sides of a battle and then left you to difference them yourself. Elixir leaked is the clearest case - the number means almost nothing alone, and everything against what the other player leaked - but the same is true of deck lev…
Read it ›An agent can track (Jamie, 2026-09-23: a clan agent "may be asked to track a competitive clan", and a family agent had no way to be configured at all).
Read it ›The timeline is a newsfeed (Jamie, 2026-09-23: "we had the whole concept of Timeline backwards; think of it like the newsfeed in a social app"). What happened most recently comes first, everywhere the timeline is read: elixir_timeline, the console, and the ma…
Read it ›The ranking tools, after the Elixir Gym's third run on them (feedback #208-#210).
Read it ›The collection tools after the Elixir Gym's third run on them (feedback #201-#203), and the card tools after its fourth (feedback #204-#207).
Read it ›The battles tools, after the Elixir Gym's fourth run on them (feedback #199-#200).
Read it ›The clan tools, after the Elixir Gym's third run on them (feedback #195-#198).
Read it ›badges_rarity with limit, after the Elixir Gym's fourth run on the badge tools (feedback #193-#194).
Read it ›The card tools, after the Elixir Gym's third run on them (feedback #191-#192).
Read it ›The battles tools, after the Elixir Gym's third run on them (feedback #186-#190).
Read it ›A clan segment on the badge tools counts the clan's current members with a profile read, as before 6.36.3. The recorded-now filter 6.36.3 added also dropped a current, covered member, and it is held for a decision. The coverage note stays: it says how many of…
Read it ›The badge tools, after the Elixir Gym's third run on them (feedback #183-#184).
Read it ›The 6.36.1 notes name other tools' fields in the tool.field form (war_history.closed_at, war_history.progress_earned, war_rivals.mean_fame), so a response never names a field it does not carry.
Read it ›The war tools, after the Elixir Gym's second run on them (feedback #179-#181).
Read it ›The ranking tools, after the Elixir Gym's second run on them (feedback #174-#177).
Read it ›The player tools, after the Elixir Gym's second run on them (feedback #171-#172).
Read it ›game_clock says that a clan's race closes each war day before the 10:00Z grid, in the half hour before it and per race (observed 09:30 to 10:00Z). war_day_closes_at is the policy boundary, not the moment a race stops taking battles, and war_current carries a …
Read it ›An elixir_timeline page is sized to fit the result cap as well as the 150-item cap. Items are taken in the order they were observed until the page reaches 40,000 characters, and the cut falls on the first item that would not fit: the same observed_at cut, so …
Read it ›elixir_timeline holds 150 items a page, down from 200, so a compact page fits the 48,000-character result cap now that every session_standout is an item (a 7-day compact read had reached 54,766). The rest page through next_cursor. elixir_updates and the elixi…
Read it ›elixir_timeline, after the Elixir Gym's second run on the elixir family (feedback #162-#167).
Read it ›collections_get says what years_played is: the account's age in whole years (the game's YearsPlayed badge level), not time in the collection, and null until a profile poll has read the badge. Its description no longer calls it tenure, or calls open_members an…
Read it ›The clan tools after the Elixir Gym's second run on them (feedback #157-#158), and a rule for weekly donations.
Read it ›cards_synergy's raw-window mode split uses the season rollup's mode-group rule, so a battle of an odd API type reads casual on both paths, not other on one (#154).
Read it ›The card tools, after the Elixir Gym's second run on them (feedback #153-#155).
Read it ›On a raw window the meta tools apply the meta population to the battles they consider, not only to the decided ones. excluded.considered then equals decided_battles plus the excluded buckets again, as on a season read (6.31.0 had counted an event battle as co…
Read it ›The battle tools, after the Elixir Gym's second run on them (feedback #148-#151).
Read it ›badges_rarity and badges_holders on the corpus count only the players recorded now (#145). The corpus had pooled every profile the record ever read, about twice the recorded population, with badges and clans as old as March. A note says what players_considere…
Read it ›The badge tools, after the Elixir Gym's second run on them (feedback #144-#146).
Read it ›The 6.29.0 war-trophy timing note names only fields its response serves: our_clan_war_trophies on the weeks list and clan_war_trophies on an exact week's standings. The war_rivals note no longer names a trophy_change its rows do not carry.
Read it ›The war tools, after the Elixir Gym's first run on them (feedback #140-#142).
Read it ›The ranking tools, after the Elixir Gym's first run on them (feedback #136-#138).
Read it ›The player tools, after the Elixir Gym's first run on them (feedback #129-#134).
Read it ›The game family, after the Elixir Gym's first run on it (feedback #125-#127).
Read it ›The elixir family, after the Elixir Gym's first run on it (feedback #118-#123), and every tool with an outputSchema.
Read it ›The collection tools, after the Elixir Gym's first run on them (feedback #114-#116).
Read it ›The clan tools, after the Elixir Gym's first run on them (feedback #110-#112).
Read it ›The card tools, after the Elixir Gym's first run on them (feedback #102-#108).
Read it ›The battle tools, after the Elixir Gym's first run on them (feedback #95-#100).
Read it ›The badge tools, after the Elixir Gym's first run on them (feedback #91-#94).
Read it ›Faster level gaps and trends, and three more tools on the analytical budget. Wire shapes are unchanged.
Read it ›Three small honesty fixes from the Gym's open questions and the usage audit.
Read it ›The war family's clan_score is WAR TROPHIES, and now says so (feedback #88).
Read it ›The boat note quoted its share against the wrong denominator (feedback #89).
Read it ›The comparisons a battle row always held both halves of, and what its signature proves about how long it ran.
Read it ›Friday now has an issue, and it is about one card. The card is chosen by a program rather than by us - the ten most-played cards of the season that have not been written up in the last year, with one drawn from those ten - so nothing gets featured because som…
Read it ›Clash Royale game modes are played as different games. A river race battle only somewhat resembles Trophy Road, and neither tells you much about Path of Legends - and in some modes you do not even pick your deck. Elixir had one blunt fold for this, keyed on t…
Read it ›A river race duel is up to three games recorded as one row, and Elixir has been telling people it could not speak to the games inside it - that a duel's tower hitpoints describe the final round only, that it has no elixir differential. That was true of what E…
Read it ›The Elixir Gym's second war run checked yesterday's fixes against today's numbers - all confirmed - and found three more things in the same family. The race's day-by-day is the game's own, and on the day a boat crosses the line the game caps that day's closin…
Read it ›Event content is its own mode group, and it no longer informs the meta. Game modes are played as different games, and Elixir was pooling them.
Read it ›A duel can answer for its own rounds, and a battle says whether you met a ranked opponent.
Read it ›The Elixir Gym's second war run (feedback #84-#86), on the day-by-day and the exact-week path of war_history.
Read it ›The acceptance suite's first day found that players_collection at full verbosity refused for any mature collection - the answer ran to 55,000 characters against the 48,000 cap, and with no limit to narrow, the refusal could not even say what would fit. Thirty…
Read it ›The Gym's war run left one question for Jamie rather than a bug: a player who fields Evo Royal Hogs bridge spam asked the meta for decks that fit, and the top row - Evo Royal Hogs cycle, the same card at a faster pace - read as costly to adopt as Three Musket…
Read it ›Two agents running a weekly meta report filed the same wall on the same evening: ask battles_meta_decks or battles_meta_cards for the whole corpus over the last seven days - what's rising, what's falling - and the call timed out, every time, while the whole-s…
Read it ›The Elixir Gym's war run found the flag the docs promised on every war week - finished_early, true when the boat reached the 10,000-fame line - served on no row at all. It was computed as fame exactly 10,000; the race log caps fame there, but the live race re…
Read it ›players_collection at full verbosity fits again. A mature collection's full answer was ~55k characters against the 48k result cap - every read refused, and with no limit to narrow, the refusal could not price a retry. 31k of it was the catalog repeated per ca…
Read it ›The middle rung of adoption cost (the Gym's open question after its 6.10.0 run; Jamie's call 2026-09-21: the win condition dominates the family). A player fielding Evo Royal Hogs bridge spam was shown Evo Royal Hogs cycle on the bottom rung beside Three Muske…
Read it ›The corpus meta on a week's window, and a compact size for the meta tools (feedback #77-#80: every 7-day corpus read of battles_meta_decks and battles_meta_cards timed out, and four full payloads crossed a turn's ceiling).
Read it ›The Elixir Gym's war run (feedback #81, #82): finished_early was documented, named in every war_history note and served on no row - it was computed as fame exactly 10,000, and the record keeps the boat's progress past the line (10,134, 10,305) that the live r…
Read it ›The largest bucket of unnamed decks left after the debug pass was Rune Giant with Lumberjack, Golden Knight and Lightning - about three thousand battles with no building-targeter at all, the tower damage coming from enchanted troops behind the tank. The wiki …
Read it ›A few hundred recorded decks read beside their labels. The labels landed where they should on the classic shapes; what they missed was the new meta: a quarter of this season's battles were decks Elixir could only name by cost, and the cards defining them were…
Read it ›One tool for the two questions a player asks in one breath. Give it a name - 'bridge spam', 'Royal Hogs bridge spam', 'LavaLoon', '2.6 Hog' - and it says the family and win conditions it means, the other names for that shape, and how much of this season's rec…
Read it ›A read-only page for the maintainer: every catalog card with its archetype role (win condition and tier, bait unit, bridge partner) and the public source that attests it, the vocabulary version in force and which commit of the reference repository it was impo…
Read it ›battles_meta_decks now folds a population by archetype - group_by 'archetype' for rows like 'Royal Hogs bridge spam' and 'Hog Rider cycle', group_by 'family' for the six families - and on a clan, player or collection each row names the members who play the sh…
Read it ›Players say 'Royal Hogs bridge spam', 'Hog cycle', 'Log Bait' - not eight card names - and Elixir now speaks that language in both directions. Every deck it serves carries its archetype: the family (beatdown, control, cycle, bait, bridge spam, siege), the win…
Read it ›An agent recommended a deck from the corpus meta that the player could not play: two of the top four rows ran a card he does not own, and the top row, at his actual card levels, sat two mean levels below what he had been fielding all month. The population's d…
Read it ›A pass over the console for places that showed a clan tag or a player tag with no name beside it. Agents: the clan an agent acts for read as its tag on the agent's page, in the agents table and on Connections, and the create-agent form's clan picker promised …
Read it ›The Elixir Gym's regression run on the rankings tools found a label, not a data gap: the live Path of Legends board the recorder keeps is the API's top 1,000 places (checked directly: the API offers a page cursor at limit 5 and none at 1,000, and a cursor pla…
Read it ›A card that names a deck without being its win condition (the Rune Giant read). Some decks have no building-targeter at all - the tower damage is chip from enchanted or support troops behind a tank - and the deck sites lead the name with the tank: 'Rune Giant…
Read it ›The debug pass: a few hundred recorded decks read beside their labels (the {archetype_sample} operator read), and what it changed.
Read it ›The resolver (design §5.2; Jamie, 2026-09-20: the product is still evolving, the tool-list weight is not the constraint).
Read it ›Deck archetypes, phase 2 (design §6, §7, §12.2): the archetype is stamped on every deck, so a whole population can be folded or filtered by name, and the fit reader says which shapes a player already fields.
Read it ›Deck archetypes (docs/reviews/2026-09-20-DECK-ARCHETYPES-DESIGN.md; Jamie, 2026-09-20: players talk about decks by name, and Elixir has to name a deck and know what a name means). Every deck object now carries archetype - the deck's family (beatdown, control,…
Read it ›The population's decks against what one player holds (feedback #70, 2026-09-20). A corpus deck sorted by win rate reads as advice, and the payload carried nothing about the caller's collection: an agent recommended a deck the player could not field - two of t…
Read it ›A name beside every tag the console had been showing bare. Three envelopes gain a last-observed name so a reader need not make a second call to say who a record is about.
Read it ›The rankings family, after the Elixir Gym's regression run (feedback #71-#74 and #76, 2026-09-20). The material one is a label: the live Path of Legends board is the API's top 1,000 (probed: limit=5 returns a cursor, limit=1000 and 2000 return 1,000 rows with…
Read it ›The recorder was losing about 4% of all battles - some 7,000 a week - and knew it only as a count of 'gaps'. Measured against the game's own lifetime battle counter, the loss came almost entirely from long sittings that began inside a long wait: the old sched…
Read it ›The 24-by-7 'when they play' tile under the battle-activity year came down. It was built to place battle-log reads where a player's expected battles crossed the log's batch; scored against a week of reads it did not place them (players sit down in hours the h…
Read it ›The fleet list said 'active' for a collector that had not checked in for forty hours; the lifecycle state was true and the reading was not. elixir_collectors and the fleet page now say what a collector is doing: active when it checked in within the hour, sile…
Read it ›Two pieces of agent feedback this afternoon, one bug and one negative result. The bug: a duel's elixir differential was a number when the spec said null, because each side's counter on a duel is a sum over two or three games played on different decks. The neg…
Read it ›A year of the record was put to Pilot Score - a player's win rate minus what their card-level advantage 'should' have won - and it did not hold: most of the battles it scored had no level gap at all (Ranked and casual equalize levels), the adjustment barely r…
Read it ›Profile is who you are and what your tier gives you; the six email switches and the list of what was sent to you now live at Profile → Email, and your signed-in sessions at Profile → Devices. The 'send me this now' button beside each switch is gone - it never…
Read it ›The privacy page is restructured around the distinction that matters. Game data is public and recorded, and no sponsor owns any of it. Your account's own records - calls, emails sent, events, feedback, connections - are kept because the product is made of the…
Read it ›A milestone mail read 'You earned MasterySkeletonWarriors (level 5)', which is the game's internal name for the Guards Mastery badge; the API carries no display name for a badge, only an icon. Every surface that says a badge now says it the way a player would…
Read it ›An agent re-ran every 3.13.0 fix and found all of them holding, then found three places where the guard sat beside the field that needed it. A weekly row's trophy_battles counted only the ladder games the game reported a trophy delta for, so a player parked o…
Read it ›Elixir now sends mail from the record: a Monday clan report, Tuesday's your week in the Arena, Wednesday's tracking report, Thursday's Top 100 (one shared issue), Sunday's collector activity for operators, and a milestone note when something you or an alt did…
Read it ›The five releases since the record redesign each put a new name beside an old one so nothing broke mid-week; this release keeps the new name and retires the old, in one deploy, with every first-party client updated the same evening. A series point has day; a …
Read it ›The things consumers worked around are served. A consumer of the timeline names its own read pointer (reader), so two bots on one account stop moving each other's window and the 'anything new?' hint on every response finally means something for a bot that mar…
Read it ›The same words now mean the same things on every tool. Every window says which season it starts in and every season roll it crosses, so a sixty-day read across the roll is named as one before an agent averages it; 'this season' is one argument (season) on the…
Read it ›3.13.0 put the mode split, the level gap, the trophy floor and the clipped-week mark beside the five tools that had misled an agent; this release carries the same controls to every other tool that serves a rate, a trend, a rank or a sum. players_summary says …
Read it ›The recorder has kept more than the tools showed: a battle's event and tournament tags and how its deck was chosen, a boat attack's towers, each war day's points and rank for every clan in the race, the rivals' clan scores and repair points, a player's past P…
Read it ›A review of the interface after the record redesign found fourteen places where a description, a note or a docs sentence said one thing and the wire did another, and this release fixes every one without changing a name. A closed war week's whole roster (war_h…
Read it ›Two readings that were wrong about the fleet and the catalog (2026-09-19).
Read it ›The leaked-elixir counter travels as one object with its caveat on the value (feedback #65 and #66, 2026-09-19). The 3.13.0 note beside the row was served, read and overridden by a consuming agent the morning it shipped, because the number sat beside crowns a…
Read it ›Pilot Score is gone (Jamie, 2026-09-19: a mirage). Three reviews on the year of the record (docs/reviews/2026-09-19-PILOT-SCORE-ASSESSMENT.md, -PILOT-SCORE-EVOLUTION.md, -ELIXIR-LIFT-TWO-POPULATIONS.md) found that 70-76% of the observations it scored carried …
Read it ›Badges as a player says them (Jamie, 2026-09-19: the milestone mail read 'MasterySkeletonWarriors (level 5)'; it is Guards Mastery). The API names a badge by Supercell's internal identifier and carries no display name, so every surface that says a badge now c…
Read it ›The 3.13.0 guards, landed on the field that needed them (feedback #61, #62, #63, the 2026-09-19 regression run: every 3.13.0 item held, and three new defects were a guard sitting beside the number rather than on it).
Read it ›The batched major (docs/reviews/2026-09-19-INTERFACE-REVIEW.md Part 5.3, Phase 6): the names and shapes the additive releases 3.14.0 to 3.18.0 doubled are settled to one, with no deprecation window (every client of this server is first-party and was updated i…
Read it ›The seam (docs/reviews/2026-09-19-INTERFACE-REVIEW.md Part 3.2, 6 and 7, Phase 5).
Read it ›One grammar, one vocabulary (docs/reviews/2026-09-19-INTERFACE-REVIEW.md Part 2, Phase 4).
Read it ›The control next to every number (docs/reviews/2026-09-19-INTERFACE-REVIEW.md Part 4, Phase 3): every tool that serves a rate, trend, rank or sum carries the control the 3.13.0 principle names, and a note fires only on a detected confound.
Read it ›The record reaches the wire (docs/reviews/2026-09-19-INTERFACE-REVIEW.md Part 1.3, Phase 2): every collected column an agent would ask about is served on the tool that owns the question, no migration.
Read it ›The fourteen verified defects of the interface review (docs/reviews/2026-09-19-INTERFACE-REVIEW.md), Phase 1.
Read it ›An agent reading this service reached six wrong conclusions from correct data in one session, and each time the payload had withheld the fact that made its number interpretable: it moved a war-only deck to Trophy Road because its 79% beat a ladder deck's 42% …
Read it ›The record has kept a day-grained history of every polled clan and every member of it since 2026-09-17, backfilled from the archive to March, and now it answers. clans_timeline returns a clan's day series (clan score, war trophies, member count, required trop…
Read it ›Every aggregate ships the control next to the number (feedback #54, #55, #56, #58, #59, #60: six wrong conclusions from correct data in one agent session).
Read it ›The daily series as readers (docs/reviews/2026-09-18-TIME-SERIES.md Part 7). Every daily series is keyed by the GAME day (10:00 UTC to 10:00 UTC, named for the date it starts on; docs: clocks#the-game-day), and every point carries its stamps: observed_at, pro…
Read it ›A clan's roster is read up to 96 times a day and, until today, the record kept four identity columns of it and threw the rest away while polling the same players' profiles separately for the same numbers. Every polled clan now has a daily row of its own (clan…
Read it ›A player's daily snapshot was filed under the UTC calendar date it was taken on, while war days, the season roll and every clan's policy day run on the 10:00 UTC grid: the snapshot taken in the hour before a season rolls (Monday 09:00 UTC) sat on the new seas…
Read it ›war_current and the clan timeline said which river race day it was from the clan's last observed period, so a clan whose polls lagged, or that the recorder had only just started following, could read a stale day or none at all. The record now holds every poli…
Read it ›A corpus-wide card or deck meta read scanned every recorded battle on every call - 8 to 13 seconds warm, and nine timeouts a week. The record now keeps one rollup per season and mode (deck, card by form, card pair, and the totals every rate is a share of), re…
Read it ›A war battle's week and day used to be stamped onto the record at ingest, and only when the clan's next race poll happened to follow the battle inside a fortnight, so three quarters of the war battles the record held carried no day at all and were invisible t…
Read it ›The card, deck and synergy meta tools answered a rolling 28 days, which on 17 September was 14% last season and 86% this one with nothing in the response saying so; balance changes land on the season roll, so those are two populations. The record now holds ea…
Read it ›players_profile's output schema declares the shapes of snapshot.path_of_legend, league_statistics and lifetime with every key nullable (a key the API omitted is served as null since the objects render from typed columns), which moves the tools fingerprint in …
Read it ›battles_meta_decks, battles_meta_cards and cards_synergy answer a corpus-wide season read (the default window, or season) from the season's rollup instead of a scan of every battle: the same population and the same fields, with players_as_of (when the distinc…
Read it ›The season is a row and the meta tools read by it (docs/reviews/2026-09-16-SCHEMA-REVIEW.md 1.1). battles_meta_decks, battles_meta_cards and cards_synergy default to the CURRENT SEASON TO DATE (applied.window.source: 'season') instead of a rolling 28 days, wh…
Read it ›A Discord bot on the timeline was still firing on a wall clock for most of what it posted, and spent ten tool calls a day rebuilding a member's win streak and trophy swing from battles_performance. Now a member's session that crosses a disclosed rung (5, 10 o…
Read it ›The timeline as a trigger for a clan bot (docs/reviews/2026-09-16-TIMELINE-FOR-PROACTIVE.md). elixir_timeline: a member's session that crosses a disclosed rung (5/10/20 wins in a row, 150/300/500 ladder trophies net, 20/40 battles in one sitting) is a session…
Read it ›Each cell of the battle-activity year on Console now carries two things: its hue is the day's win share, from red (all losses) through purple (even) to blue (all wins), and its shade is still the volume, four steps scaled to the player's busiest day. Tap a da…
Read it ›The bar now reads Elixir, and its right-hand side carries the family's three products as buttons: Console (this record's own pages), Clan (clan.poapkings.com) and Drop (drop.poapkings.com, which opens in a new window and says so). The one you are inside is gr…
Read it ›Two natural agent reads of elixir_my_feedback crossed the 48,000-character delivery cap: twenty full reports plus maintainer responses can be much larger than twenty ordinary rows. Worse, the read marked every response seen before the protocol replaced the bo…
Read it ›The connection instructions have said 'days/weeks are sugar' since 1.0.0, and five tools honoured it while the rest refused with bad_request - an agent that had just used clans_standings({days: 1}) sent days: 1 to battles_performance and lost three calls lear…
Read it ›The arena move got its battle this morning; the other three threshold moments now carry theirs, one shape everywhere (opponent, crowns, trophy change, and the instant as the item's at). A ranked battle is stamped with the league it started in, so the promotio…
Read it ›Trophy Road arenas have floors: reach the floor and you are in, and a loss never takes you below it again - the game reports a loss on the floor with no trophy change at all, and the last floor, 14,000, is where Trophy Road ends. So the promotion is one ident…
Read it ›A clan member reached Royal Crypt at 06:52Z on 2026-09-15 and the clan's timeline said so at 14:27Z, when the eight-hour profile poll came round; the battle log, read many times in between, had carried the new arena on every entry. A battle's arena is the hig…
Read it ›Until today the only place a played card lived was the deck's JSON on each battle, so every card question - card meta, synergy, which battles had a card - re-read every deck in the window, and on 2026-09-14 three clans asking at once pushed those reads past t…
Read it ›The clan's own recorder kept six months of raw reads the record had never seen. They were replayed through the same admission as a live fetch, with their original fetch times: battles from January, daily snapshots and profiles from March 7, every war week fro…
Read it ›elixir_my_feedback returns lossless bounded pages: pass next_offset as offset until null; total counts the filtered ledger. A page may contain fewer rows than limit when full feedback and maintainer text would exceed the delivery cap. Only responses actually …
Read it ›days and weeks are accepted on every windowed tool, as the server instructions have said since 1.0.0: battles_query, battles_performance, battles_cards, battles_decks, battles_meta_decks, battles_meta_cards, battles_compare, battles_opponents, cards_synergy, …
Read it ›elixir_timeline: ranked_promotion carries facts.promoted_by (the last win played in the league below - a ranked battle is stamped with the league it started in); best_trophies_band carries facts.band and facts.crossed_by (the Trophy Road win whose result firs…
Read it ›elixir_timeline: arena_changed items carry facts.promoted_by when the record holds the crossing - the win whose result first reached the new arena's floor: opponent {player_tag, name, starting_trophies}, crowns, crowns_against, trophy_change, trophies_after, …
Read it ›elixir_timeline: an arena move is polled for as soon as the player's own Trophy Road battles vouch for it (a battle entered with at least the opponent's trophies, since a battle's arena is the higher side's), so arena_changed lands within the battle log's cad…
Read it ›battles_query renders each participant's deck from the recorded card rows: the same {cards:{id, name, level, evolutionLevel?, starLevel?}, supportCards?} shape, or {rounds:{cards}} for a duel, with names from the catalog; the storage-only norm marker is gone.…
Read it ›Cards played are recorded as rows (deck, deck_card, battle_participant_card), so every card question is an indexed lookup instead of a scan of every deck's JSON. battles_query gains with_cards (several ids, all present in your deck); with_card and against_car…
Read it ›game_events now carries first_sighting_day and its horizon note reads the table rather than a date in the code: the elixir-bot backfill placed sightings from 2026-06-13 before the daily reads that began 2026-09-11. Same backfill, no shape change elsewhere: PO…
Read it ›Deck meta now keeps only a participant key for each deck's latest qualifying observation during its aggregation, then reads the full deck only for the returned rows. It no longer sorts and collects every full deck JSON before applying the result limit. Counts…
Read it ›Deck meta, card meta and clan standings now cancel over-budget queries and return query_timeout with a request id and retry hint, leaving time to record the failure. Their MCP query budget is at most 18 seconds; a narrower from/to window reduces work, while l…
Read it ›rankings_players with board mode and location list now names the recorded leaderboard ids, including Merge Tactics; an unknown mode points to that discovery call. The contract changelog fits the response cap by returning up to 20 releases per page, with next_…
Read it ›Deck meta no longer aggregates every full deck JSON before applying the result limit. It keeps the latest qualifying observation's participant key per deck, then reads the returned decks through that primary key. Counts, unrounded rates, shrinkage, scope, and…
Read it ›Heavy MCP reads (battles_meta_decks, battles_meta_cards and clans_standings) now share an 18-second query budget, shortened when Lambda has less time left. PostgreSQL cancels over-budget work and returns query_timeout with an executable retry and meta.request…
Read it ›Mode-board discovery now works: rankings_players({board: 'mode', location: 'list'}) returns the recorded leaderboard ids, names and enabled state, and an unknown mode points back to that executable discovery call. elixir_changelog now delivers complete histor…
Read it ›elixir_events is elixir_timeline. It answers what happened to the players and clans you track since your read pointer, as items in order: a battle session (a gap of 30 minutes breaks one; single battles never appear), a badge by name, an arena or ranked move,…
Read it ›elixir_events no longer hands an agent a pile of topic rows with counts to drill. It returns one entry per subject since you last looked: a sentence a person can read, then the facts under it, always in the same sections. For the players you track that is the…
Read it ›game_clock now answers the next boundaries of each kind: when this war day closes, when the next war day opens, when training resumes, when the week ends. A scheduled agent reads those once and decides for itself when to look, instead of waiting for the feed …
Read it ›The Verify challenge no longer hands you eight random cards. The target is now the deck you played most in your last ten recorded battles, with two cards swapped for cards you own of similar elixir cost; the two swaps are marked in the brief. A deck you have …
Read it ›The console now opens on a battle-activity graphic, with a chip per tracked player, and the record of each tracked player carries the same one: a year of UTC days coloured by recorded battles, and a 24-by-7 rhythm of when that player plays, rotated into your …
Read it ›The Admin collector table counted both requests every completed fetch must make — its lease and its submitted result — but compared that pair with one fetch. A perfectly efficient collector therefore appeared to make two calls per fetch. Calls/fetch now start…
Read it ›elixir_events is now elixir_timeline. The response carries the TIMELINE: items in order, each with an instant, a subject, a kind, a section, a sentence and its facts. Battles appear as sessions (a gap of 30 minutes breaks a session), never one by one; badges,…
Read it ›elixir_events is an activity feed of ENTRIES, synthesized at read time: one per subject since your bookmark, each with a summary sentence a person can read, always-present sections (a player's battles, trophies, arena, ranked, collection, badges, clan, war, p…
Read it ›Feed payloads now carry what the Events page always promised: member_role_changed has prev_role, new_role and direction (promoted | demoted), and member_left has the departing role. war_current and the clan pulse's decks_today gain race_finished_at (also top-…
Read it ›Collectors now check in and the door answers with the next interval instead of holding a poll open. One released Python collector still expected the earlier idle fallback in its configuration, so the door keeps sending that compatible value while it also send…
Read it ›The tool-choice guide still said four tools could request a live read, even though the leaderboard tools had joined that lane. Its count now comes from the MCP registry, the same source as the generated tool reference, so the website and the guide served over…
Read it ›The roster gate treated the game's last-seen stamp as proof that a member could not have played. The capture audit proved otherwise: a completed session can fill the roughly 30-battle log before that stamp is observed again. It still skips an unchanged profil…
Read it ›Elixir was asking for sign-in more than it should have, and a census of the owner's own sessions showed why: sessions were not expiring, sign-ins were happening beside live ones. Four causes, fixed. When the page could not reach Elixir it showed the sign-in w…
Read it ›A clan's own participation rules need the same few facts about every member: battles and ranked battles per week, the donation counter at week end, war decks per day, when the record first saw them, when they last played. Getting those for fifty members meant…
Read it ›A web product in the family can now use Elixir as its sign-in. It asks for one extra capability, account:email, and GET /oauth/userinfo answers the address the code already proved, so Elixir Clan and Elixir Drop know you are the same person you are here. The …
Read it ›The first Verify waited for your profile's current deck to show the eight cards. On the owner's own account it never did: the API kept reporting the old deck for over an hour after the slot was selected, with the game closed. The battle log has no such lag, s…
Read it ›A claim on a player was taken on trust. Console ▸ Verify now proves it with the one field the game lets you set and the API shows to everyone: your active deck. Elixir names eight cards you own, shown two rows of four like the game; you put them in an empty d…
Read it ›The first day of the roster gate was measured against the review that proposed it. Battle-log fetches halved as promised and the web door's cost fell 97%, but capture gaps rose from 0.1% to 1.5%: a roster read every 4 to 24 hours (an incidental clan, polled o…
Read it ›The event guide's example called the pulse's war discriminator day_kind and showed roster changes as member lists. The digest has always returned war.kind and numeric joined/left counts. The example now matches, explains when war_day and decks_today appear, a…
Read it ›NEW TOOL clans_participation: every open member's participation week by week in one call. Per member, columns aligned to the top-level weeks (ISO, 1 to 8, default 5, current week partial): battles, ranked_battles, donations (the weekly counter at week end, nu…
Read it ›OAuth gains account:email and GET /oauth/userinfo, for web products in the Elixir family that sign a person in with Elixir. The scope is granted only to a client that names it: it is not part of the default grant, is never offered ticked on the consent page, …
Read it ›Four card-meta reads arriving together exhausted the MCP door's 25-second limit: player, clan and collection windows were filtering time after the battle join instead of using the participant-time index built for exactly that access path, and the card query s…
Read it ›Last fetch on Status > Collectors now reads to the second (3m 12s ago, not 3m ago) - five rows all saying 3m ago is how a fleet fetching in lockstep went unnoticed. A VERSION column shows the client each collector last submitted with, so a machine that has no…
Read it ›Told the same fifteen seconds from the same empty queue, every collector in the fleet came back on the same second and hit the door as a pack after each scheduler tick. The door now gives each active collector its own slot in the idle cycle, evenly spaced acr…
Read it ›Running a collector is a favour, so the favour gets to choose its face: when you raise your hand at Status > Collectors you now pick the Clash Royale card your collector is named for, and a collector you already run can change its card from its own page. A ca…
Read it ›A collector that fetched a thousand payloads of nothing looked identical to one that fetched a thousand payloads of news. Every receipt now records what its fetch was worth - rows the projection inserted or changed, the bytes read from the API, the time the a…
Read it ›Six in ten battle-log polls came back with nothing new, and most profile polls confirmed a profile that had not moved. A clan roster already carries the game's own lastSeen for every member in one small fetch, so the scheduler now reads it first: when a roste…
Read it ›Asking for a live read used to hold your call open while a dedicated collector long-polled for it - and held two collectors long-polling around the clock for the sixteen such calls a week. Now live: true means: answer from a read no older than the API's own c…
Read it ›players_collection now reads a player's cards and tower troops from the record - levels on the in-game 1-16 scale, counts toward the next level, which forms are unlocked - instead of a payload cache that has been empty for most players most of the day since t…
Read it ›The global Path of Legends board was snapshotted every hour: twenty-four copies of a thousand places a day, for a board that only needs to be remembered as it stood at each reset. It is now read once per board-day, in the first planning tick after 10:00Z, so …
Read it ›Every clan was read every 15 minutes around the clock — a heartbeat inherited from the single-clan bot, applied to 288 clans, 258 of them polled only because a top-ranked player happens to be a member. It was 31% of everything the recorder had ever fetched, f…
Read it ›A battlelog is a player's last 25 battles, and every poll used to carry all 25 to the service, which then discovered it already had most of them. Now the service remembers the newest battle each player's log has delivered, hands that mark to the collector wit…
Read it ›Three small additions to what a collector's config call returns, for the preflight command the next collector release carries (collector doctor): the address your requests arrive from, which is the one to allowlist on your Clash Royale key; the one Clash Roya…
Read it ›This morning's finals backfill fetched each season's final board by a bare number and took that number for the season the game clock counts — it is the position in the API's own list of seasons, eight higher. What the record called the S135 final was December…
Read it ›Every Path of Legends season's final standing since S97 — the settled board at full depth, 9,999 places — is now in the record, backfilled, and each new season's final is fetched the day after it rolls. The clan ladders (clan score, clan war trophies) are rec…
Read it ›The CR API shows a ranking as it is this minute and forgets it. Elixir now keeps it: the global Path of Legends board every hour, and every one of the 262 locations the API lists once a day — a snapshot per fetch that changed, a row per placed player with ran…
Read it ›Scoped battle intelligence now uses the participant-time index for player, clan and collection windows instead of filtering time only after joining back to battles. battles_meta_cards also derives its denominator from the same card expansion rather than scann…
Read it ›live: true is asynchronous. It means: answer from a read of the game no older than the API's own cache (60 s for players, battle logs and boards; 120 s for clans and the river race) if one is in hand; otherwise queue one priority fetch and answer NOW from the…
Read it ›The card collection is recorded. players_collection reads a player's cards and tower troops from the record (levels on the 1-16 scale, counts, forms), not from a payload cache that went empty two hours after each profile poll - since 0071 it had answered card…
Read it ›The season finals were filed under the wrong season numbers, and eight were missing. 1.4.0 fetched a final by a bare number and took that number for the season game_clock counts (S136 = September 2026); it is the position in the API's own seasons list, eight …
Read it ›Everything else the API forgets about a season. FINALS: rankings_players and rankings_clans take board: pol_final with a season id - every Path of Legends season's final standing at full depth (9,999 places) since S97, backfilled, and each season's final fetc…
Read it ›The leaderboards are recorded. rankings_players reads a board - the global Path of Legends board by default, any of the 262 locations by id or country code - as of the latest snapshot or any earlier instant (as_of), paged with limit and offset, verbosity comp…
Read it ›Elixir is free to use and independently run, and there is now a page that says what keeping it going costs and how to help pay for it: GitHub Sponsors at three suggested amounts, with running a collector set beside it as the other way to contribute. The page …
Read it ›Three reports from the agents using the record are fixed in contract 1.2.0. war_current now keeps period_points, the score a clan has earned in the current war day, beside fame, the cumulative boat score banked when a day closes — so day-one fame can honestly…
Read it ›The player tag on your access request is claimed and recorded the moment you are approved, and the clan that player is in is followed too, at activity scope — the one clan slot every tier has, which is exactly what it is for. Sign in and the console already k…
Read it ›Every update is its own page now, so you can send somebody one, and the tool-contract changelog is part of the same stream rather than a second page saying the same thing — a version's summary, the tools it added and what it broke sit with the release that ca…
Read it ›Report this call on a request record now attaches that request as a field on the report — the arguments, the answer and the timings ride along, so there is nothing to describe. Agents can do the same: elixir_feedback takes request_id (contract 1.1.0), which e…
Read it ›Profile shows the same eight limits the Tiers page publishes, with what you are using beside each one, instead of four meters. A warning about an expired credential still being presented can be dismissed — it comes back if it happens again another day. Busies…
Read it ›The access-request form now lives on the sign-in card in the console, as the other half of one question: you are either signing in or asking to. Every Request access button leads there. The form used to have a second copy on the home page, and it was failing …
Read it ›Every page now carries the Open Graph and Twitter metadata a shared link needs: the page's own title and description, and one share image with the mark and the tagline. Paste a docs page into Discord, Slack or a post and it renders as a card instead of a bare…
Read it ›Every tool now follows the same rules, and the rules are written down. The two tools that start recording are named for what they do: elixir_track_player and elixir_track_clan (tracked means recorded, as before). Every windowed tool takes from and to, with da…
Read it ›The Feedback page is a table now, like Notifications: one line per note with its first line, state and whether the maintainer has replied, and the whole note one click away. A note and its reply render as the Markdown they were written in, so paragraphs and l…
Read it ›The Feedback page is a table now, like Notifications: one line per note with its first line, state and whether the maintainer has replied, and the whole note one click away. A note and its reply render as the Markdown they were written in, so paragraphs and l…
Read it ›An agent reading the documentation through elixir_docs was getting the source rather than the page: template variables where the numbers should be, and links with nothing to resolve them against. The corpus is now rendered with the same data the site uses, it…
Read it ›The eleven examples used to be illustrations: invented clanmates, invented numbers, a citation chip under each answer. Each one has been re-run for real against the live service, as King Thing of POAP KINGS, and the answers are what came back — the tools unde…
Read it ›Use cases are now Examples: eleven pages, one per example, each with the rail of all eleven beside it, the exchange typed live, what it reads, the steps to set it up as buttons, and three more like it. The family page is one page per product with the same rai…
Read it ›Every console screen and site page was compared against the design it was built from, and the gaps closed. Usage shows both quotas as meters with the reset time, fourteen days of calls, and who spent them — your clients, your agents and the console each on th…
Read it ›Six tabs, a wordmark and a Console button do not fit on a phone. The tabs now collapse behind one button on the right, and the sheet drops below the bar rather than covering the page — six links is a menu, not a modal. The Console button stays on the bar at e…
Read it ›The home page used to lead with a counter panel. A number says the corpus is big; it cannot say what it is for, which is the only thing a home page has to do. It leads with a conversation now — a real question, the answer, and under the answer the citation na…
Read it ›The console outgrew a row of tabs across the top, so its sections moved into a rail down the left: Overview and Explore, then what we record for you, then who can call on your behalf, then how the service is running. Two things changed with it. Overview is no…
Read it ›Three player-reported gaps closed together. WAR CURRENT: standings add period_points, the current war day's score, beside fame, the cumulative boat score banked at the day close; the note says why fame can still be zero while members have points. WAR HISTORY:…
Read it ›elixir_feedback takes request_id: the meta.request_id of the call the feedback is about. Every response already carries one, and attaching it hands the maintainer the exact request, its arguments and its answer beside your words - the console has had a Report…
Read it ›The 1.0 contract: one set of conventions across every tool, from the review of the whole surface (docs/REVIEW-2026-09-10). NAMES: elixir_add_player and elixir_add_clan are elixir_track_player and elixir_track_clan (the console's word; an 'add' tool that remov…
Read it ›The service documents itself over MCP. elixir_docs returns the documentation index (every page with its section and lede), one page as Markdown by slug, or the pages matching a query with an excerpt around the first hit; elixir_examples returns the eleven wor…
Read it ›Clash Royale reports when each clan member was last active, but only inside a clan's member list - a player's own profile endpoint does not carry it. Every roster poll delivered it and we threw it away, which meant it was unrecoverable for any moment we did n…
Read it ›A clan leader counted 44 people in this week's race against 49 in the clan, and had no way to tell a recording gap from a real one. It was real: checked against the game's own live payload, its current-river-race participants list returned the same 44 and lef…
Read it ›An agent can connect either over OAuth or with its service key. Editing capabilities only reached the first: an OAuth connection's capabilities live on its grant and are edited on Account -> Connections, but a service key's live on the key, so an agent connec…
Read it ›Account -> Connections now lists the capabilities of every live connection and lets you edit them in place. Tick a capability to add it, untick one to take it back; the change applies to that connection's next call, with no reconnect and no new token, because…
Read it ›Connecting an app used to grant exactly what that app requested, and nothing else could be added afterwards. Since the read-only challenge advertises only cr:read, an app that never asks to file feedback or change recordings could never be allowed to, and the…
Read it ›A round of agent playtesting found places where the service was hard to trust or hard to report. Failures now answer in the same shape as successes: a database that cannot be reached and a rate limit both return error.code, a message, a hint and a meta.reques…
Read it ›The capture charts only ever showed completed fetches. A new 'Work waiting' gauge above them shows the other half as a queue, in pipeline order: subjects due for the next scheduler tick (the planner runs every five minutes, so due work piles up between ticks …
Read it ›Both capture charts on the Status page gap-fill up to the current minute, so the right-most bar was always the bucket in progress and read as zero for the first minutes of every five-minute window, which is exactly how long the scheduler waits between ticks. …
Read it ›The docs now carry the wire contract, not only the product: a protocol reference (transport, OAuth discovery and registration, PKCE and the resource parameter, the five scopes and the step-up challenge, every error code at every layer, the 48,000-character re…
Read it ›Two changes to how the recorder decides when to fetch a player's battles. First, asking about a player through any tool now keeps that player's battlelog within an hour for the next day; until now a friend who plays a few games a day sat on the daily fairness…
Read it ›Feedback filed on the site or through a connected agent, and tier-upgrade requests, now email the maintainer the moment they land: the category, a short excerpt, and which account or agent sent it (never an address), with a link to act on it. Until now only a…
Read it ›The explorer on the website now follows the same discipline as the MCP connection: the hourly rate limit and daily call budget are the same buckets, oversized results come back as the same bounded failure, and it serves read-only tools (nicknames excepted, wh…
Read it ›An agent's live Clash Royale fetches now come out of its owner's daily live budget, the same way its tool calls already did; until now each agent quietly carried a fresh live allowance its owner never had, so several agents on one account multiplied the one s…
Read it ›Eleven pieces of feedback from one agent session shipped together, because they shared a shape: the record held the detail and each tool exposed only one way to group it. battles_opponents groups a player's battles by opponent, so 'have I faced this player be…
Read it ›Account - Connections now shows, per connected client, when it last actually called (rather than when it last collected a token), the address and country it called from, and how many calls it made this week - alongside the disconnect button that was already t…
Read it ›An agent's page now shows where it connects from - address, country and what the client calls itself - and warns when something is still presenting a credential that no longer works, which until now was invisible because a refused call never becomes usage. Re…
Read it ›Submitting the authorization form twice - which phones do on their own after filling a one-time code - no longer replaces a successful connection with an error page. A repeat within two minutes repeats the same answer and returns you to your client, with ever…
Read it ›A code sent for connecting an AI client and a code sent for signing in to the website are now kept separate. Previously the most recent code of either kind was the only one that could be used, so requesting one while the other was open made the other impossib…
Read it ›An agent's page now revokes its key, reports when it was last active across every key it has held, and says outright when the current key has never been used - the signature of a runtime still presenting the previous one, which produces no errors because a re…
Read it ›An agent's page now shows the URL to connect a client at, with a copy button, and creating one shows that URL beside the key it hands over once. Agents can also be renamed after creation; the name stays unique among your live agents and travels with the agent…
Read it ›An agent connection omitting clan_tag now resolves to the clan the agent acts for, as its opening instructions have always promised. Clan defaults were previously derived from claimed players, which an agent does not have, so clan tools answered that the conn…
Read it ›The game's own lastSeen is captured and served instead of discarded. Clash Royale exposes it only inside a clan's memberList - /players/{tag} does not carry it - so it was obtainable on every roster poll and thrown away, and every un-stored poll was gone for …
Read it ›war_current reconciles the race roster against the clan roster: participants_count, member_count and members_not_in_race name the current members this week's race leaves out, each with reason not_in_race_roster. Verified against the live API rather than assum…
Read it ›A round of agent playtesting, fixed together. ERRORS: every refusal now carries the same envelope a success does. A database the door cannot reach answers 503 with {error:{code,message,hint}} plus meta.request_id and Retry-After, instead of a bare Internal Se…
Read it ›Arguments are validated against each tool's declared inputSchema before the handler runs: an unknown property, a wrong type, a value outside enum/minimum/maximum/length bounds, or a missing required argument is refused with bad_request naming the argument, ne…
Read it ›An agent's live fetches (live_fetch, players_profile live: true) are charged to its OWNER's daily live budget, matching how its tool calls were already charged, so every agent on one account shares one live allowance and meta.quota.live reads the same balance…
Read it ›Eleven feedback items from one agent session, shipped together because they share a shape: the corpus held the detail and exposed one grouping axis per tool. NEW AXES: battles_opponents groups a player's recorded battles by opponent (record, first/last met, m…
Read it ›elixir_my_players now returns relationship (primary | alt | friend | watching) and your private nickname for each player, so "my alt" and "my friends" resolve from the response instead of being guessed from handles - the account owner had recorded those disti…
Read it ›Admin → Integrations now provisions platform keys, permissions, independent budgets and collection enrollment grants. The versioned API provides a game calendar, recorded player profiles, asynchronous refreshes and idempotent automatic recording enrollment. E…
Read it ›Account → Connections now suggests questions your recorded history can support. Copy one into your connected AI client to review your player snapshot, recent battles, decks, two recorded weeks or a recorded clan war. View the full question before copying; man…
Read it ›Account pages, API routes and maintenance commands now have smaller, focused modules. Successful account and agent journeys are tested against the real API on disposable databases, including first capture, agent creation, key rotation, suspension and resumpti…
Read it ›Response metadata is checked against the shared contract before a tool result is returned. The response guide now uses a generated, tested example, with UTC timestamps, explicit unknown freshness, and the current contract version. Valid answers and statistica…
Read it ›Deck and card meta now count only wins and losses in their decided totals, usage and shrinkage baseline; draws and unresolved results no longer depress that baseline. Empty samples report an unknown rate. Personal and clan Pilot Scores now share the same leve…
Read it ›Your account overview now guides you from adding a player through the first capture to asking your own MCP client. Suggested questions follow the data actually recorded: a player snapshot first, then battle reviews, deck comparisons and comparisons between tw…
Read it ›Performance summaries now count the whole period you ask about, including histories longer than 2,000 battles. Freshness follows the data used: a recent profile poll can no longer make an old battle log look current, and war answers show when the race was las…
Read it ›Creating an agent used to be a one-way door: you could make one and revoke its key, and that was the whole story. Revoking was worse than a missing feature, because there was no way to issue a replacement - the only path back was deleting the agent and buildi…
Read it ›The signed-in application went unmeasured for a few days, and the reason was a fix that did not fix anything. Analytics had been taken off the application because third-party code running inside your session is genuinely worth avoiding - but the same script s…
Read it ›Your connection now identifies itself as data, not only as prose. initialize has always said who you are connected as inside the instructions - 'YOU ACT FOR POAP KINGS' - which suits the model reading it and not the program hosting it, so a client wanting to …
Read it ›Response metadata is checked against the shared contract at construction and at the tool registry boundary. The existing timezone_applied field is now declared; timestamps, optional history, source freshness, counters and receipt IDs are checked. Public respo…
Read it ›Clarify numerical precision in statistical tool notes: calculations use unrounded aggregates; rates and scores are independently rounded to three decimals. Recomputing a shrunk rate or score from displayed rates can differ in the final decimal place. Calculat…
Read it ›Statistical alignment: deck/card meta exclude draws and unresolved outcomes from decided totals, usage and shrinkage baselines; empty segments return segment_win_rate: null. Both return methodology and window_to. Card meta rejects reversed windows and exclude…
Read it ›Performance summaries now aggregate the entire requested window; last_n_battles remains an explicit sample. Player response metadata distinguishes the oldest relevant poll, individual source_polls, earliest stored recorded_since, and recording_active_since. w…
Read it ›The daily clan pulse now says whether a quiet member is really quiet. 'Days quiet' has always been counted from the last battle we recorded, so for somebody we had stopped polling it measured our own blind spot rather than their inactivity - and telling the t…
Read it ›Players you add can finally be told apart. Relationship - primary, alt, friend, watching - shipped as a column months ago and your connected agent has been reading it the whole time, but nothing could ever set it, so every player you added was announced as 'w…
Read it ›The event feed now carries milestones, and it reaches agents through the clan they run. Badges, arena changes, personal-best trophies, career-win thousands, collection levels and Path of Legends promotions all nod at you now - none of them ever did before, be…
Read it ›Every tier now tracks 50 players, up from 3-25 - one comprehensive clan watch already records about that many, and recordings are shared, so a clanmate of a clan already being captured costs nothing to add. Your connection now tells you who you are. The openi…
Read it ›game_clock answers what season and war day it is with no clan and no player - the calendar is a property of the game, not of anyone playing it. Connections now describe the job they are for: an agent acts for a clan and no longer sees the personal identity to…
Read it ›Every response now carries meta.request_id, naming the audit row that produced it — quote it when reporting an answer that looks wrong. Calls made with a service token are recorded against that token, not just the account behind it.
Read it ›Every page here used to be one file. Whatever address you opened - the docs, the tool list, the changelog - the server sent back the same home page, and your browser drew the rest. That works for a person clicking around and fails everyone else: search engine…
Read it ›Connecting an agent used to ask for read access while its token could also change recordings, collections, nicknames, event state, and feedback. That mismatch is closed. The authorization page now lists each capability before you enter the code, read-only acc…
Read it ›Clash Royale resets war days at 10:00 UTC as policy, but it matches clans into races of five as matchmaking fills, so every clan's day really starts a little off that hour by its own amount. Following each clan's own drift is right for a single clan and wrong…
Read it ›A round of fixes to what collections actually do. Raising a collection's scope to comprehensive now deepens the members it already holds, instead of only the ones you add afterwards - so a collection that says it captures battles captures them. Deleting a col…
Read it ›The admin console has always said that no admin can change the owner's account, or another admin's. The role controls enforced it; the approve/deny control did not, so an admin could deny a privileged account out of the service. Access decisions now answer to…
Read it ›OAuth grants now mean what the consent page says. cr:read calls every read-only tool but cannot edit collections, change recordings, update nicknames/event cursors, or file feedback; those actions require collections:write, recordings:write, account:write, or…
Read it ›War days now follow the 10:00 UTC POLICY reset for every clan. Clash Royale matches clans into races of five as matchmaking fills, so each clan's real period start drifts off that hour by its own amount; Elixir MCP is multi-clan and cannot honour every clan's…
Read it ›war_current: period_end_nominal and week_end_nominal were wrong whenever the ~10:00 UTC reset drifted early. A period first seen open at 09:57Z reported its end as 10:00Z that same morning - about 24 hours early, and already in the past by the time anybody re…
Read it ›Putting a player or clan in a collection now records it, for as long as it stays there. Until today a collection was only a list, so curating one recorded nothing and you had to add every subject to your account separately. Each collection also says how deepl…
Read it ›Every collector is somebody's machine, quietly fetching on a home connection so the archive keeps growing. The status page now says whose: each collector is credited to the player who runs it, beside the Clash Royale card it was named for. Only the game ident…
Read it ›The capture chart told you how much was fetched but not by whom. Both charts are now stacked by collector, and hovering any bucket breaks it down - who fetched how many, and how many were rejected. Underneath it sits a second chart covering the last 24 hours …
Read it ›The status page and the admin table were showing different times for the same collector, and both were right: one counted the last data we accepted, the other counted the last time the collector said hello. A collector that is polling happily but has nothing …
Read it ›Collectors only install the exact binary version and hash this server names, which is what stops a compromised release page from pushing code to operators. That naming step had never been used, so released collectors were quietly staying on whatever version t…
Read it ›Provisioning a collector token in Admin used to succeed silently: the token is staged for the operator's one-time reveal on their Collector page, so the Admin table just refreshed and looked like nothing happened. Admin now confirms the token is staged, keeps…
Read it ›The collector fleet was rebuilt overnight around a simple rule: operators cannot be assumed safe. Collectors are now pure API clients - a bearer token we issue, three HTTPS routes, no AWS credentials of any kind - and the server computes what to fetch, stamps…
Read it ›An independent review of the whole system produced a punch list, now shipped: war-day events and the current-war view survive season rollover (the period index resets each season - the anchors now know that), staying signed in actually works (sessions slide w…
Read it ›Feedback items are now real pages - open one from your feedback list (or the admin queue) to see the whole conversation at a linkable URL, and maintainer responses are now composed right there. Collections opened up the same way: open a collection to edit it …
Read it ›The Architecture page grew real depth: collectors in detail (card identities, credits, self-update, the capture audit), the push lane and Clan Pulse, how the feedback loop actually closes, and the no-NAT outbound relay design. It also now maps the public GitH…
Read it ›Elixir MCP now has a mailing list for occasional product updates, run on Buttondown the same way Elixir Drop's is: signing in enrolls you, every issue carries an unsubscribe link, unsubscribing sticks forever, and the email is pixel-free. Details on the priva…
Read it ›The site now counts visits with Tinylytics - anonymous page hits, visitor countries, and a few product events (a tool call happened, feedback was filed). No cookies, no cross-site tracking, nothing attached to your account, and the sign-in page loads no analy…
Read it ›Every clan you've added now sends one daily clan_pulse digest to your event feed: 24-hour battle activity, top players, members quiet five or more recorded days, war-day deck counts, and roster changes - facts only, the judgment stays yours. A war_day_open ev…
Read it ›Two honesty upgrades. Clans you've added now feed your notification pipe with the things that actually happen: members joining, leaving, and changing role (before this, the only clan event was the weekly war boundary - technically working, practically silent)…
Read it ›The Explore lookup now resolves names and your private nicknames, not just tags - type 'tyler' and land on the player you call Tyler (nicknames rank first), type a game name and get the record or a short pick-list when several match. Same honest miss when the…
Read it ›Data > Status is the live operational dashboard: pipeline health at a glance, every queue's depth and age (DLQ above zero shows red - that's an incident), each collector's heartbeat and hourly fetch rate, and the last hour of capture in 5-minute buckets with …
Read it ›To you, Raquaza is Tyler. Now Elixir knows that too - privately. Set a nickname on any player's record page (or have your agent call elixir_nickname), and it's yours alone: search finds 'tyler' and ranks it first, summaries and rosters show the nickname besid…
Read it ›The arena-climb was confusing flavor, so it's gone. What running a collector actually earns is now front and center: every 10 fetches adds +1 to your daily tool-call quota (capped at 4x your base), plus bonus recording slots while it runs. Each collector keep…
Read it ›The whole site moved to the new design language - Clash display type for the brand shell, gold reserved for what's YOURS (the star on your tag, your clan), purple as the working accent, denser tables with honest footnotes as first-class components. The headli…
Read it ›Provisioning a collector no longer means credentials over a side channel. Once the maintainer provisions your gateway, Account > Collector offers your complete configuration as a ONE-TIME download - it disappears from the server the moment you fetch it. You a…
Read it ›Web/agent parity closes out. The player explorer gains a Pilot Score tab - your score with its approximate standard-error field (not a calibrated confidence interval), the monthly trend, and the full Level Curve. Explore > Meta shows the observed deck and car…
Read it ›players_profile now answers the player as a game entity, not just a name and a clan tag. clan gains badge_id and the player's role in it; a new attributes block carries arena_id, best_trophies, favorite_card_id, years_played and account_age_days; and a badges…
Read it ›collections_edit: curate a collection you own from an agent or a service token. add and remove adjust membership, set replaces it wholesale - the shape an external system syncing a roster wants. Everything in a collection is recorded for as long as it stays t…
Read it ›Collections now cause recording. A player or clan named in a collection is collected for as long as it stays there - curating a list used to record nothing, so you had to add each subject to an account as well. Each collection carries how deeply to record wha…
Read it ›elixir_events with a topics filter no longer acknowledges the events it hid. The seen-cursor is one number per account, so a topic-specific poll used to mark everything below the last returned event as seen - a war-only routine could silently clear an unread …
Read it ›Correctness fixes in adding and removing players, both of which agents hit directly. elixir_add_player with make_primary now SWITCHES the primary instead of failing on a uniqueness violation, and works on a player you have already added. elixir_remove_player,…
Read it ›Hardening from five agent-persona test passes. Unknown enum values (mode, outcome, sort, metric, granularity) and impossible card ids now REFUSE with valid-value hints instead of returning silent empty results; players_timeline garbage dates get a structured …
Read it ›Clan Pulse: a daily clan_pulse feed event per added clan (24h battle activity, top players, members quiet >=5 recorded days, war-day deck counts, roster changes - facts, never judgments) plus a real-time war_day_open event when a new war day is first observed…
Read it ›Clan notifications actually notify: member_joined, member_left, and member_role_changed now flow to the event feed for clans you've added (the only clan topic before was the WEEKLY war boundary - working as designed, but the design covered almost nothing). Al…
Read it ›Private player nicknames: elixir_nickname stores YOUR name for a player (account-scoped, never visible to anyone else). players_search matches nicknames and ranks them first - 'tyler' resolves to the player you call Tyler; players_summary and clans_roster car…
Read it ›battles_query gains two addressing modes for the record browser (and agents): battle_id alone fetches ONE battle with both perspectives; deck_hash alone sweeps the corpus for that exact deck and returns deck_stats (battles, W-L, distinct pilots, span - delibe…
Read it ›Account gained two pages. Activity shows three views of your own account: every MCP request your agents made (tool, timing, errors - the debugging view), your account's event history, and your notification pipe (with unread rows past your agents' cursor bolde…
Read it ›Elixir MCP now shows its work in public. The new Data area carries the corpus dashboard - battles recorded per day, players observed, collector activity, full history - and the rendered contract changelog. The front page touts the live totals, and the public …
Read it ›Three new intelligence tools, grounded entirely in recorded battles. battles_meta_decks and battles_meta_cards show what's actually being played and winning - across the whole corpus, one clan, one player, or a collection like the pros - with shrunk win rates…
Read it ›The model got simpler, at Jamie's direction: adding a player or clan IS recording it - no separate watch toggle, no follow bookmarks, no approval queue. Your tier's slots are the only gate, and the one per-subject setting left is the notification bell: whethe…
Read it ›Clan watching is now self-serve: add any clan to your account for free, and turn watching on or off yourself - activity or comprehensive - within your tier's slots. No more waiting for approval; the role ladder is the gate. The ladder itself gained its top ru…
Read it ›Three ships in one. ROLES: five tiers (member, leader, family, partner, admin) now set recording slots and daily budgets - never what you can read; the full ladder is public under Docs > Roles, and upgrades are self-serve from Account > Overview. SELF-SERVE: …
Read it ›The site grew faster than its nav, so the nav got rebuilt: four areas - Explore (player, clan & war, collections, collectors), Account (overview, agents, usage, feedback), Docs, and Admin - each with its own page row underneath. Collections are now browsable …
Read it ›Round two, built from feedback about the feedback system itself: an MCP-visible changelog (elixir_changelog - what shipped since any contract version), machine-readable ship links on responses, a meta hint when a maintainer reply awaits you, and server instru…
Read it ›Two big ones. All recorded game data is now readable by every account - the same access the game's own public API gives anyone (we add history, not exposure); account data stays private. And Collections arrive: curated groupings of players or clans - starting…
Read it ›The first feedback ever filed through the MCP write tool asked for three things - and shipped the same night: clans_pilot_scores ranks a whole clan's Pilot Scores in one call (was 18), players_search resolves clanmate names to tags, and battles_levels takes i…
Read it ›Filed feedback now comes full circle: the maintainer can reply, and you (or your agent, via the new elixir_my_feedback tool) see each item's status and response. Nothing gets actioned invisibly - triggered by the first real agent-filed feedback, which deserve…
Read it ›KHAOS drafts, Crazy Arena, Showdown - the rotating event modes were recorded all along but hard to discover. battles_performance group_by 'mode' now lists every named mode you've played with its record, and battles_query takes a game_mode filter ('chaos' find…
Read it ›Grounding affordances (agent feedback #8 - an inference-error case study, filed at the user's request): war_current now carries an explicit period block (period_index, war_day, started_observed_at, period_end_nominal, week_end_nominal) so temporal claims cite…
Read it ›Observed meta + segment trends (META-INTEL 2-3, grounded in recorded data only). battles_meta_decks and battles_meta_cards aggregate any segment - the corpus, a clan, a player, or a collection like 'pros' - with EB-shrunk win rates, distinct-pilot counts, and…
Read it ›Metadata truth pass for the added-means-recorded structure: every description now matches behavior (no stale watch/claim/entitled-scope language); server instructions teach the add + notify + events_pending flow. players_search now searches the WHOLE recorded…
Read it ›ADDED = RECORDED. The watch/follow distinction is gone: adding a player or clan starts collection within your tier's slots, and the only per-subject setting is notify (does it feed your event pipe). elixir_add_player and elixir_add_clan replace the watch tool…
Read it ›One entitlements system and self-serve clan watching. The ladder gains its top rung: owner (super admin, exactly one) above admin; admins see the console with day-to-day powers. elixir_watch_clan now STARTS recording directly within your tier's clan slots (ac…
Read it ›The entitlement ladder and the push lane. Roles (member/leader/family/partner/admin) set collection and call-volume quotas - roles NEVER gate visibility, universal reads stands; see the public Roles doc. elixir_events: your per-account event feed (event types…
Read it ›Leaderboards via live_fetch (agent feedback #6, filed unprompted): /locations/{id}/rankings/players and /locations/{id}/pathoflegend/players join the allowlist - top-100, and every ranked tag accretes into the corpus for immediate use with the player tools.
Read it ›Feedback interface round two (agent feedback #4/#5): this changelog tool; structured ship links (shipped_in, related_tools) on feedback responses; feedback_responses_pending hint in response meta when a maintainer reply awaits you; status/since filters on eli…
Read it ›UNIVERSAL READS: all recorded game data readable by every account (the public-API posture); account data stays private. Collections: curated player/clan groupings (first: 'pros', 11 professional players).
Read it ›First agent feedback actioned: whole-clan Pilot Scores in one call; name-to-tag search; include_curve flag.
Read it ›Feedback loop closed: maintainer responses with status visible to the requester. Feedback is never actioned invisibly.
Read it ›Event modes findable: battles_performance group_by 'mode' lists every named mode played (Chaos/KHAOS drafts, Crazy Arena...); battles_query gains a game_mode substring filter.
Read it ›Two new intelligence tools, grounded entirely in recorded battles. battles_levels measures what card-level advantage is actually worth (a 66,000-observation curve) and scores any player's Pilot Score - performance relative to an in-sample level-gap baseline, …
Read it ›New clans_standings tool: every member's recorded win rate over a window, ranked against the clan median - the 'am I above average?' answer, built for agents (including Elixir, the POAP KINGS clan agent, whose stats answers are moving onto Elixir MCP).
Read it ›Clan recording now comes in two scopes: activity (the clan itself - roster, war, standings) and comprehensive (all of that plus every member's battles and profile, following the roster as membership changes). Existing recorded clans stay comprehensive.
Read it ›Tool names now lead with their domain - players_summary, battles_query, war_current, elixir_feedback - so every client lists them grouped: Players, Battles, Clans, War, Cards, Live, and Elixir MCP itself. The service domain also grew four tools: watch a playe…
Read it ›Three fresh agent testers, thirteen fixes: war attendance now counts recorded battles (polls alone undercounted), opponent decks and names appear in battle detail, weekly trends align to real ISO weeks and show trophy-eligible counts, summaries add best-deck …
Read it ›Running a collector now means cloning one small repo (elixir-mcp-collector on GitHub) instead of the whole server codebase. Existing collectors migrated in place and keep self-updating.
Read it ›Every payload the collectors fetch is now archived durably to S3 the moment it is admitted — the full raw history behind your record is kept forever and stays queryable, while the database keeps only the hot serving set.
Read it ›Honesty batch from agent playtesting: unknown war-day attendance is now null instead of a false zero, war participants say whether they are still in the clan, the seasons filter applies to member weeks, and comparison windows state plainly that they cover rec…
Read it ›Long-lived API tokens for trusted services — the first step toward elixir-bot consuming Elixir MCP instead of running its own recorder.
Read it ›Running a collector now raises your daily tool-call quota (every 10 fetches = +1 call, up to 4x), and every gateway gets a Clash Royale card as its avatar on the ladder.
Read it ›A new Docs section: what Elixir MCP is, how privacy and terms work, and the architecture — maintained alongside the code, so it is always current.
Read it ›The new Explore page renders exactly what your agent sees: summary, battles, weekly trend, decks, collection, war, and coverage — every view is a real MCP tool call.
Read it ›Send feedback from the dashboard or have your agent call send_feedback — either way it lands on the maintainer's desk attributed to you.
Read it ›get_performance can return a weekly win-rate series, get_player_summary answers "how am I doing?" in one call, and deck performance gained sorting and share-of-battles.
Read it ›The elixir-bot archive was replayed into the recorder: battles back to mid-May, war seasons 133-135, and daily snapshots from July.
Read it ›Level Curve + Pilot Score (wins your card levels can't explain, with monthly trend and experience cohorts) and the war Scouting Report.
Read it ›Domain-first tool names (players, battles, war, elixir...) and four service tools.
Read it ›Tool taxonomy: every tool classified and annotated (grouped titles, read-only hints).
Read it ›Round-3 playtest batch: war attendance counts recorded battles, opponent decks at full verbosity, ISO week_of, draws + best_deck on summaries, stricter validation (forged cursors, empty tags, bounds).
Read it ›War-tool honesty batch: null-never-false-zero attendance, in_clan flags, seasons scoping, payload-mirror notes.
Read it ›Recording, the MCP server, clan war data, and the gateway fleet — live from day one.
Read it ›