https://elixir.poapkings.com/updates Every user-visible change to Elixir MCP, newest first. en Fri, 18 Sep 2026 12:00:00 GMT https://elixir.poapkings.com/updates#2026-09-18-1 https://elixir.poapkings.com/updates#2026-09-18-1 Fri, 18 Sep 2026 12:00:00 GMT 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 trophies, weekly donations) with the aggregates over that day's members (total and average trophies, how many rows the day has) and, on request, the profile-derived ones (average wins and collection level, the 12,000+ / 14,000+ / six-years+ / collection-1,000+ counts). clans_members_timeline returns every member's series for a clan: trophies, donations, rank, arena and the game's own last-seen for everyone, plus any profile metric for recorded members; compact keeps first, last and the delta per member. players_timeline grows to every metric of the day row, takes kind (the pre-reset row is the honest weekly donation total) and progress_key for the side-mode seasons. Every point carries the instants that produced it, its source and its kind, and every series is keyed by the game day (10:00 UTC to 10:00 UTC). clans_roster now carries each member's lifetime block, tenure and badge count. Contract 3.12.0. https://elixir.poapkings.com/updates#2026-09-17-2 https://elixir.poapkings.com/updates#2026-09-17-2 Thu, 17 Sep 2026 12:00:00 GMT 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 score, war trophies, member count, required trophies, weekly donations), and every member on every polled roster has a daily row in the same series a recorded profile writes: trophies, donations, clan rank, arena at the roster's cadence, and the game's own last-seen as a series rather than a single latest value; an arena move the roster sees lands on the timeline at the roster's cadence rather than the profile's. The profile keeps its half of the same row, with its lifetime block (now including total donations, challenge and tournament counters and the king tower level), the progress buckets per season as their own series, the previous season's final Path of Legends standing kept once, and the frozen Clan Wars 1 counters on the player. The race poll keeps the rivals' clan score, repairs and badge and the race's day-by-day results; the war log fills the last war day's attendance. No tool changes shape yet; players_timeline already returns the roster-written days, and the readers over the new series follow with the next contract bump. https://elixir.poapkings.com/updates#2026-09-17-3 https://elixir.poapkings.com/updates#2026-09-17-3 Thu, 17 Sep 2026 12:00:00 GMT 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 season's Monday, and a snapshot at 03:00 UTC was a different day from the war day it was played in. Every snapshot row now sits on its game day, the date whose 10:00 UTC start it follows; where a day's early-morning poll and the previous day's late one landed on the same game day, the later observation is the row, which is the rule the table always had. players_timeline points, players_summary.trophies_as_of and clans_participation's donation columns read the same way with the corrected days; no tool changes shape. https://elixir.poapkings.com/updates#2026-09-17-4 https://elixir.poapkings.com/updates#2026-09-17-4 Thu, 17 Sep 2026 12:00:00 GMT 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 policy day as a row, and the day is looked up by the clock: always current, for every clan, with the clan's own first sighting of that day reported beside it when the recorder has one. Windowed battle reads also take their bounds from the participant row the indexes are built on, which is the same answer sooner. Contract 3.11.1. https://elixir.poapkings.com/updates#2026-09-17-5 https://elixir.poapkings.com/updates#2026-09-17-5 Thu, 17 Sep 2026 12:00:00 GMT 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), rebuilt nightly from the raw rows and topped up hourly with the battles recorded since. battles_meta_decks, battles_meta_cards and cards_synergy read it whenever the window is exactly one season, which is their default; the response carries players_as_of and a note, because distinct-player counts are as of the last rebuild and the counters trail by up to an hour. A clan, player or collection read, and any explicit window, still scan the raw rows exactly as before and only take the corpus prior from the rollup. Contract 3.11.0. https://elixir.poapkings.com/updates#2026-09-17-6 https://elixir.poapkings.com/updates#2026-09-17-6 Thu, 17 Sep 2026 12:00:00 GMT 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 to attendance in war_current, war_days in war_history and the per-day columns of clans_participation; a March-to-July import had brought its own labels, and 3,230 of those contradicted the battle's own time. The war calendar is now rows in the record, one per policy day of every season on the 10:00 UTC grid every clan shares, and a war battle is filed by where its time falls on it for the clan the player was in. Nothing is stamped, nothing depends on which poll came first, and history recorded long after the fact counts the same as history recorded live. No tool changes shape; the numbers those fields carry are corrected. https://elixir.poapkings.com/updates#2026-09-17-7 https://elixir.poapkings.com/updates#2026-09-17-7 Thu, 17 Sep 2026 12:00:00 GMT 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 each season as a row, first Monday 10:00 UTC to first Monday 10:00 UTC under the month the API names it by, with the river race season number derived from the month and confirmed against every war log entry it admits. battles_meta_decks, battles_meta_cards and cards_synergy default to the current season to date and take season: 'current', 'previous', '2026-08' or 135; battles_trends takes it too. Every such response says which season the window starts in, lists each season roll it crosses (empty when clean) and how old the season is, and a thin new season points at 'previous' rather than quietly widening. What is deliberately not there: balance changes themselves, and the in-game Pass season, neither of which the API exposes. Contract 3.10.0. https://elixir.poapkings.com/updates#2026-09-16-8 https://elixir.poapkings.com/updates#2026-09-16-8 Wed, 16 Sep 2026 12:00:00 GMT 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 or 20 wins in a row; 150, 300 or 500 ladder trophies net; 20 or 40 battles in one sitting) is a session_standout item on the clan's timeline, at the battle that crossed it, once per rung and never repeated; the clan entry lists its five strongest under standouts.sessions. The record's first sight of a new war week is a bracket_observed item naming the four rivals and whether each is recorded - the week's start time stays the clock's. kinds keeps only the item kinds you wake on. Badge and card moments name the member again (facts.name; the badge or card is facts.badge / facts.card), badge items appear only at a final level or a multiple of five, and collection-level steps widen as a collection grows, so a maxed account no longer writes a milestone a day. clans_standings answers trophy_net and current_streak per member in the same call. Contract 3.9.0. https://elixir.poapkings.com/updates#2026-09-15-9 https://elixir.poapkings.com/updates#2026-09-15-9 Tue, 15 Sep 2026 12:00:00 GMT 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 day and the caption says the record - '6 battles · 4 wins, 1 loss, 1 draw' - and the two-week list gains a won/lost column. Draws and unresolved results count toward volume and toward neither side; a day with nothing decided keeps the neutral purple. The nightly histogram now stores wins and losses per day alongside the count, so a day the job has not rebuilt yet is drawn as before until the next run. https://elixir.poapkings.com/updates#2026-09-15-10 https://elixir.poapkings.com/updates#2026-09-15-10 Tue, 15 Sep 2026 12:00:00 GMT 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 green; the others are gold, the way over. The same bar, with the same tabs, is drawn on the documentation pages, in the console and in Elixir Clan, so moving between them never changes the shape of the page. The service is still Elixir MCP; the wordmark names the family it belongs to. https://elixir.poapkings.com/updates#2026-09-15-11 https://elixir.poapkings.com/updates#2026-09-15-11 Tue, 15 Sep 2026 12:00:00 GMT 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 body with result_too_large, so the agent could lose its pending signal without seeing the reply. The tool now returns bounded, lossless pages with total and next_offset; pass next_offset as offset until null. A page may be shorter than limit when the text is large, and only replies actually delivered on that page are marked seen. Additive; contract 3.8.0. https://elixir.poapkings.com/updates#2026-09-15-12 https://elixir.poapkings.com/updates#2026-09-15-12 Tue, 15 Sep 2026 12:00:00 GMT 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 learning the difference. Every tool that takes a window now accepts days and weeks as sugar for from, ending now: the battles family, opponents, synergy, the timeline, rankings_timeline, game_events, and players_timeline (there as N days of snapshots, today included). from/to given still win. Additive; contract 3.7.0. https://elixir.poapkings.com/updates#2026-09-15-13 https://elixir.poapkings.com/updates#2026-09-15-13 Tue, 15 Sep 2026 12:00:00 GMT 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 promotion is the last win played in the league below - 'promoted to Master 2, on a 1-0 win over XTRAXTOR, +30'. A new best names the Trophy Road win whose result first reached the 500 band - 'set a new best of 6,087 trophies, crossing 6,000, on a 3-0 win over Jotaro (5,976), +30 to 6,000'. A career-wins mark names the 1,000th win itself, but only when every win between the two snapshots is on the record: the window's wins must reconcile with the lifetime counter, or the moment carries no battle. The rule for all four is the same: absence over a guess. https://elixir.poapkings.com/updates#2026-09-15-14 https://elixir.poapkings.com/updates#2026-09-15-14 Tue, 15 Sep 2026 12:00:00 GMT 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 identifiable battle: the win whose result first reached the floor. arena_changed on the timeline now carries facts.promoted_by - the opponent (tag, name, starting trophies), the crowns, the trophy change and the trophies it landed on - and the item's instant is that battle's, not the poll's: 'moved to Royal Crypt from Executioner's Kitchen, on a 3-0 win over Jotaro (5,976), +30 to 6,000'. The floor is read from the record (the lowest trophies any snapshot has shown in that arena, or the player's own gated loss), and when the record does not hold the crossing the moment carries no battle rather than a guess. The opponent's own arena is not the condition: on 2026-09-15 a member was promoted by beating an opponent still in the old arena, confirmed by a profile read fourteen minutes later. https://elixir.poapkings.com/updates#2026-09-15-15 https://elixir.poapkings.com/updates#2026-09-15-15 Tue, 15 Sep 2026 12:00:00 GMT 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 higher side's, so a player just under a gate sees the next arena on their own log whenever they meet someone standing on it - the log cannot be the fact, but it can be the trigger. When a Trophy Road battle the player entered with at least their opponent's trophies names an arena the latest snapshot does not carry, the profile is polled at the next planning tick, roster gate or not, and the profile remains the authority. Separately, every profile-derived moment was diffed against the previous DAY's snapshot while the day's row was rewritten on each poll, so a later poll the same day re-emitted it (a promotion to Master 2 appeared at 07:22Z and again at 16:22Z on 2026-09-14). Moments now diff against the latest observation and are written once; the Monday donation reset likewise. https://elixir.poapkings.com/updates#2026-09-15-16 https://elixir.poapkings.com/updates#2026-09-15-16 Tue, 15 Sep 2026 12:00:00 GMT 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 the 25-second door. The record now holds a deck table (one row per deck identity), its cards, and what each participant played in each battle with the level they played it at, written in the same transaction as the battle and backfilled for all 454,654 recorded participants. battles_query takes with_cards for several cards at once; card meta, synergy and deck lists read the rows. A card the daily catalog has not seen yet is recorded from the battle and the catalog is fetched at once, so a release day never pauses recording. https://elixir.poapkings.com/updates#2026-09-15-17 https://elixir.poapkings.com/updates#2026-09-15-17 Tue, 15 Sep 2026 12:00:00 GMT 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 from season 129 (February 16) with its standings and participation, per-day war attendance from March, the game-events calendar from June, and observed membership tenure from March 12 - first_observed_in_clan on clans_roster and clans_participation now says when a member was first seen, not when this record started. elixir_coverage and war_history state the horizon; a week with points but null war days is coverage, not absence. https://elixir.poapkings.com/updates#2026-09-14-18 https://elixir.poapkings.com/updates#2026-09-14-18 Mon, 14 Sep 2026 12:00:00 GMT 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, rates, shrinkage and the latest-observation example are unchanged, and the query budget still bounds slow calls. https://elixir.poapkings.com/updates#2026-09-14-19 https://elixir.poapkings.com/updates#2026-09-14-19 Mon, 14 Sep 2026 12:00:00 GMT 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 lowering limit only trims returned rows. Corpus meta avoids a redundant scan with the same population and shrinkage math. An unrecorded rival roster now names the exact live retry, without starting an ongoing watch, and clan standings advertises the existing one-call short-window member scan. This is a reliability boundary, not a promise that every 28-day query will finish under load. https://elixir.poapkings.com/updates#2026-09-14-20 https://elixir.poapkings.com/updates#2026-09-14-20 Mon, 14 Sep 2026 12:00:00 GMT 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_offset to reach the rest and the same since filter throughout. The tool-choice guide now shows the existing short-window clan standings and exact-deck clanmate drill, and makes the race-finished caveat explicit. Live-quota tool names come from the registry, and the timeline guide distinguishes player notables from clan standouts and states the ledger's indefinite retention separately from the 30-day read window. https://elixir.poapkings.com/updates#2026-09-13-21 https://elixir.poapkings.com/updates#2026-09-13-21 Sun, 13 Sep 2026 12:00:00 GMT 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, a new best, a card unlocked, a join, a departure, a role change, the boat crossing the line, a week resolving, a member crossing a quiet rung or coming back, and your own account events. Every item is a sentence a person can read with its facts beside it. The per-subject entries stay as the summary of the same window. mark_read moves the pointer to the top; a dry run passes false. The console's Activity page shows the same timeline. https://elixir.poapkings.com/updates#2026-09-13-22 https://elixir.poapkings.com/updates#2026-09-13-22 Sun, 13 Sep 2026 12:00:00 GMT 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 their battles and record, trophies and bests, arena and ranked moves, collection and badges, clan moves, war decks, and whether they went quiet or came back. For a clan it is the activity, who joined, left or changed role, the war state and the weeks that resolved, members crossing quiet rungs or returning, the standouts, and the week's donations. Nothing in an entry is advice, and nothing in the feed announces the time: a routine that cares about war reads game_clock and schedules itself. The old topic rows and the daily pulse are gone from the tool. https://elixir.poapkings.com/updates#2026-09-13-23 https://elixir.poapkings.com/updates#2026-09-13-23 Sun, 13 Sep 2026 12:00:00 GMT 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 to announce the time; war_day_open is therefore deprecated and keeps firing only through a deprecation window. Two feed payloads now match what the Events page promised all along: a role change says which roles and which direction, and a departure says the role that left. And war_current, like the clan pulse, marks race_finished_at once your boat has crossed the line, so a list of members with decks untouched is read as who played today rather than who still owes the race. https://elixir.poapkings.com/updates#2026-09-13-24 https://elixir.poapkings.com/updates#2026-09-13-24 Sun, 13 Sep 2026 12:00:00 GMT 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 played in the last month is never the target, and only a player with no recorded battles still gets a random eight. The proof is unchanged: one battle, played after the brief, with exactly those eight cards. https://elixir.poapkings.com/updates#2026-09-13-25 https://elixir.poapkings.com/updates#2026-09-13-25 Sun, 13 Sep 2026 12:00:00 GMT 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 clock. Both are rebuilt nightly from the battles already recorded. Every day with recorded battles is drawn with its count, however the battles arrived. An empty day is zero only when a read of that player's battle log covered it; otherwise it is a hatched not-recorded cell, never a zero. The same histogram is the first step toward placing battle-log reads where a player actually plays; the schedule itself is unchanged until a week of histograms has been checked against the capture audit. https://elixir.poapkings.com/updates#2026-09-13-26 https://elixir.poapkings.com/updates#2026-09-13-26 Sun, 13 Sep 2026 12:00:00 GMT 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 starts at that required pair, so 1.0 means no extra check-ins; the fleet's scheduling, pacing and shared Clash Royale API budget are unchanged. https://elixir.poapkings.com/updates#2026-09-12-27 https://elixir.poapkings.com/updates#2026-09-12-27 Sat, 12 Sep 2026 12:00:00 GMT 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 sends the check-in interval. Collection and the shared rate budget are unchanged. https://elixir.poapkings.com/updates#2026-09-12-28 https://elixir.poapkings.com/updates#2026-09-12-28 Sat, 12 Sep 2026 12:00:00 GMT 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 MCP include every tool with a live flag. The tools, live-fetch allowances and asynchronous read behavior are unchanged. https://elixir.poapkings.com/updates#2026-09-12-29 https://elixir.poapkings.com/updates#2026-09-12-29 Sat, 12 Sep 2026 12:00:00 GMT 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 profile, where a delayed stamp cannot lose history, but battle logs now always follow their yield, burst and reader limits. Status keeps publishing the gap count so this correction is measured rather than assumed. https://elixir.poapkings.com/updates#2026-09-12-30 https://elixir.poapkings.com/updates#2026-09-12-30 Sat, 12 Sep 2026 12:00:00 GMT 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 wall; now it retries once and then says Elixir didn't answer, and never calls you signed out for a request that did not get through. Every OAuth consent went to your inbox even when you were signed in; now the consent page honours your sign-in (one Authorize), and consenting by code signs you in to the site too. The idle window is thirty days instead of nine (ninety at most, as before). And a sign-in started on one screen and finished on another - the link opened in the phone's mail app - now signs in the screen that asked, at once from the same address and after a yes from a different one; the sixth email in an hour is answered honestly instead of promised. New on Console ▸ Profile: Devices, every place you are signed in with a sign-out for each and one for everywhere else. https://elixir.poapkings.com/updates#2026-09-12-31 https://elixir.poapkings.com/updates#2026-09-12-31 Sat, 12 Sep 2026 12:00:00 GMT 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 a call per member. clans_participation answers all of it for every open member in one call, per ISO week for up to eight weeks, with each war week's per-day decks where a poll saw the day and null where none did, and the recording horizon stated (tenure_known is false for anyone already present at the first roster poll). It measures and never rates: no score, no threshold, no rank. Elixir Clan reads it to run a clan's policy; any consumer can. https://elixir.poapkings.com/updates#2026-09-12-32 https://elixir.poapkings.com/updates#2026-09-12-32 Sat, 12 Sep 2026 12:00:00 GMT 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 capability is the one exception to the consent page's ticked-by-default list: it appears only when an app names it, it can never be widened into from a checkbox or from Connections, and it is never advertised in a 401 challenge. Nothing changes for MCP clients and agents; no tool reads it. https://elixir.poapkings.com/updates#2026-09-12-33 https://elixir.poapkings.com/updates#2026-09-12-33 Sat, 12 Sep 2026 12:00:00 GMT 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, so Verify now asks you to play one battle with the deck, any 1v1, win or lose, and shows that battle's result as the proof. Challenges stay open for an hour, a restart hands back the same eight cards for a day, the page lists only your primary player and your alts (players are added under Tracking), the unlock says how many seconds after the battle Elixir saw it, and verified players carry a checkmark wherever they are listed. https://elixir.poapkings.com/updates#2026-09-12-34 https://elixir.poapkings.com/updates#2026-09-12-34 Sat, 12 Sep 2026 12:00:00 GMT 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 deck slot and select it, and the page beside the brief shows what Elixir last saw, card by card, refreshed every fifteen seconds until all eight light up. Then the claim is marked verified and you switch your deck back. Challenges last twenty minutes, resume across a refresh, and the reads they ask for are not charged to your live-fetch allowance. Nothing is gated on it yet; the fact now exists for products that will. https://elixir.poapkings.com/updates#2026-09-12-35 https://elixir.poapkings.com/updates#2026-09-12-35 Sat, 12 Sep 2026 12:00:00 GMT 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 only because a recorded player sits in it) was holding back the battle-log polls of players who then played a full 25-battle session before it noticed. Now only a tracked clan's roster, read every 15 to 60 minutes while members play, can gate. Also today: a player's last-seen stamp moves at most daily instead of hourly (it was the busiest write left), the per-battle observer table is no longer written, and collectors below 2.0.30 are refused work with a clear message instead of served through the old long-poll path. https://elixir.poapkings.com/updates#2026-09-12-36 https://elixir.poapkings.com/updates#2026-09-12-36 Sat, 12 Sep 2026 12:00:00 GMT 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, and points to the individual roster-change events. No tool or payload changed. https://elixir.poapkings.com/updates#2026-09-11-37 https://elixir.poapkings.com/updates#2026-09-11-37 Fri, 11 Sep 2026 12:00:00 GMT 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 scanned its denominator twice. Both are fixed. The two pending counters in every response now say 0 when their queues are empty instead of disappearing, so a scheduled agent does not re-read its feedback ledger just to discover nothing changed. Contract 1.7.1. https://elixir.poapkings.com/updates#2026-09-11-38 https://elixir.poapkings.com/updates#2026-09-11-38 Fri, 11 Sep 2026 12:00:00 GMT 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 not picked up a named release stands out without opening its page. https://elixir.poapkings.com/updates#2026-09-11-39 https://elixir.poapkings.com/updates#2026-09-11-39 Fri, 11 Sep 2026 12:00:00 GMT 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 across the fleet and measured against the clock rather than against the last call: five collectors check in one every three seconds, a collector that just drained a burst of work falls straight back into its own slot, and a machine joining or leaving re-spaces the rest within a cycle. Nothing to update on a collector - it already sleeps exactly what the door says. https://elixir.poapkings.com/updates#2026-09-11-40 https://elixir.poapkings.com/updates#2026-09-11-40 Fri, 11 Sep 2026 12:00:00 GMT 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 card belongs to one collector - a taken one is shown dimmed, and the record refuses a double pick even when two operators reach for it at once. The form no longer hides once you run one: raising a hand is the only way a collector comes to exist, it is always yours, and you can raise as many machines as you run. https://elixir.poapkings.com/updates#2026-09-11-41 https://elixir.poapkings.com/updates#2026-09-11-41 Fri, 11 Sep 2026 12:00:00 GMT 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 admission took - and the fleet pages show it: yield (the share of the last day's fetches that changed the record), the share of battle-log entries dropped at the edge before the wire, and door calls per fetch. The budget line on the status page says how much of the hour's spend changed the record. Forward-only from today. https://elixir.poapkings.com/updates#2026-09-11-42 https://elixir.poapkings.com/updates#2026-09-11-42 Fri, 11 Sep 2026 12:00:00 GMT 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 roster fresher than a member's last poll shows they have not been in the game since, that poll is skipped. A sighting under two hours old never gates, so a session in progress is always followed. Profiles have no floor any more - an idle player owes the record no snapshot - and are read every eight hours once the roster shows them active. https://elixir.poapkings.com/updates#2026-09-11-43 https://elixir.poapkings.com/updates#2026-09-11-43 Fri, 11 Sep 2026 12:00:00 GMT 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 cache if one is in hand; otherwise queue one priority fetch for the next collector that checks in and answer at once from the record, with live_status saying it is pending and when to call again. A subject with nothing recorded answers live_pending. Collectors check in instead of polling, the door tells each one when to come back, and any collector in the fleet picks up a live fetch first. Receipts now say what a fetch was worth - new facts, ingest time, bytes read - and a collector earns a point only for a fetch that returned data. https://elixir.poapkings.com/updates#2026-09-11-44 https://elixir.poapkings.com/updates#2026-09-11-44 Fri, 11 Sep 2026 12:00:00 GMT 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 this morning's cache change. Two new nods on the event feed: card_unlocked when a card the player did not have appears, and card_leveled when a level goes up. Counts ticking toward the next level are recorded but never announced, and a player's first observed collection is silent. Collections fill as profiles are polled; nothing is backfilled. https://elixir.poapkings.com/updates#2026-09-11-45 https://elixir.poapkings.com/updates#2026-09-11-45 Fri, 11 Sep 2026 12:00:00 GMT 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 a season's last daily snapshot is the board going into the roll. The golden board for a finished season is unchanged: the API's own final standing, fetched once and kept in full. Every other leaderboard was already daily and now shares the same anchor. https://elixir.poapkings.com/updates#2026-09-11-46 https://elixir.poapkings.com/updates#2026-09-11-46 Fri, 11 Sep 2026 12:00:00 GMT 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, for rosters whose membership changes zero to three times a day. Now the roster's own lastSeen stamps set the pace: a clan you track is read every 15 minutes while three or more members are in the game, hourly once nobody has been for an hour (unless people are joining and leaving), and every four hours once nobody has been seen for a day. A clan read only because a recorded player is in it is read a few times a day on the same signal; that player's profile polls carry their clan tag, so their membership history is never lost, only coarser. live: true on clans_roster still reads the game this minute. https://elixir.poapkings.com/updates#2026-09-11-47 https://elixir.poapkings.com/updates#2026-09-11-47 Fri, 11 Sep 2026 12:00:00 GMT 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 with the lease, and the collector drops everything at or before it before submitting — the body is still exactly the API's array, just the new entries. The collector also reports how many it saw and how many it dropped, which is the capture audit stated plainly: a full log with nothing dropped rolled past what the service had. Live reads are untouched; an agent asking for a player's battles right now still gets the whole log. Collectors that don't yet honour the filter keep working, just as before. https://elixir.poapkings.com/updates#2026-09-11-48 https://elixir.poapkings.com/updates#2026-09-11-48 Fri, 11 Sep 2026 12:00:00 GMT 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 Royale path the collector may read to prove that key works from there; and an answer for a token that is installed but not yet promoted — pending reads config and nothing else, so the operator sees "not yet promoted" instead of the same 401 a typo gets. A revoked token is told so on config, once. The operators page now states the payload ceiling as it actually is, 5 MB compressed, not the 250 KB it inherited from the SQS era. https://elixir.poapkings.com/updates#2026-09-11-49 https://elixir.poapkings.com/updates#2026-09-11-49 Fri, 11 Sep 2026 12:00:00 GMT 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 2025's; the eight finals since, January through August 2026, were never fetched. Every held final is relabelled (S89 through S127, October 2022 onward), the missing eight are being fetched now, and finals are fetched by the API's own name for a season from here on — the month it started in. That name is also accepted as the season argument (2026-08 beside 135), and the snapshot carries both. Contract 1.5.0. For the record there are three season numberings in play: the game clock's (S136 is September 2026), the in-game Pass's (Season 87, which the API never mentions), and the API's YYYY-MM. https://elixir.poapkings.com/updates#2026-09-11-50 https://elixir.poapkings.com/updates#2026-09-11-50 Fri, 11 Sep 2026 12:00:00 GMT 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 recorded daily for global, the US and Japan; the game-mode leaderboards (Merge Tactics, Touchdown, 2v2 League…) are enumerated from the API so a rotating board is followed, never named; and the events the game lists as running are recorded daily as sightings, since the API gives no dates, so the season has a calendar. Three new tools read it — rankings_clan_ladder, rankings_timeline (a player's rank at every snapshot, a clan's, or the board's own floor and summit), game_events — and rankings_players takes board pol_final with a season, or board mode with a leaderboard id. Contract 1.4.0. Also fixed: since last night's deploy every board was being re-planned every fifteen minutes as never-fetched — about 1,500 extra fetches an hour — because admission stamped the board's freshness under the wrong key. https://elixir.poapkings.com/updates#2026-09-11-51 https://elixir.poapkings.com/updates#2026-09-11-51 Fri, 11 Sep 2026 12:00:00 GMT 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 rank, rating, name and clan. Two new tools read it back: rankings_players for a board as of now or any earlier instant (who was #1 on the 3rd), paged because a board can run to a thousand places; rankings_clans for which clans have the most rated players, counted over everyone above the rating floor rather than a top-100 slice. And a top-200 appearance on the global board now records the player — every battle, with the rank and rating each one carried — until the next season roll plus three days, so the season's story of its eventual #1 is captured from the first hours. Contract 1.3.0. https://elixir.poapkings.com/updates#2026-09-10-52 https://elixir.poapkings.com/updates#2026-09-10-52 Thu, 10 Sep 2026 12:00:00 GMT 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 is mostly a promise repeated three times — sponsorship gives no extra quota, retention, features or priority, at any amount, because Supercell's Fan Content Policy forbids selling access and reading is universal here by design. Collectors are the one contribution that does change an account, and the page says so plainly rather than letting the two blur. The corpus counters on it are the same ones the Data page reads, from the same build-time bake. https://elixir.poapkings.com/updates#2026-09-10-53 https://elixir.poapkings.com/updates#2026-09-10-53 Thu, 10 Sep 2026 12:00:00 GMT 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 be zero while members already have points. war_history can take season_id and section_index together and return every recorded participant for that exact week, including which numbered war days each member fought; one closed-week roster no longer takes a call per member. elixir_coverage now names unmeasured_tail_hours instead of leaving the stale tail as prose, and a player somebody tracks directly gets a profile at least every eight hours even when dormant. The existing clan-wide yield schedule remains for members nobody follows directly. https://elixir.poapkings.com/updates#2026-09-10-54 https://elixir.poapkings.com/updates#2026-09-10-54 Thu, 10 Sep 2026 12:00:00 GMT 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 knows who you are. Two related fixes: tracking a player another account already records now shows you their history instead of an empty page (the recording belongs to the player, not to whoever asked first), and the Tracking page's nudge to follow your own clan offers the slot you actually have rather than a comprehensive one it would refuse. https://elixir.poapkings.com/updates#2026-09-10-55 https://elixir.poapkings.com/updates#2026-09-10-55 Thu, 10 Sep 2026 12:00:00 GMT 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 carried them. The Data section is five pages instead of one long scroll, and the growth chart is battles per day as bars rather than a cumulative monthly curve: a running total only ever goes up and to the right, which hides the day a collector stalled. https://elixir.poapkings.com/updates#2026-09-10-56 https://elixir.poapkings.com/updates#2026-09-10-56 Thu, 10 Sep 2026 12:00:00 GMT 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 every response already hands you as meta.request_id. In the console, feedback and maintainer replies render as the Markdown they were written in on both sides of the queue. https://elixir.poapkings.com/updates#2026-09-10-57 https://elixir.poapkings.com/updates#2026-09-10-57 Thu, 10 Sep 2026 12:00:00 GMT 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. Busiest tools on Usage open the requests for that tool. Admin got the email address on Accounts, a record page for each account, a page listing every account's connections with a revoke, and a collector fleet that is a list of five columns with the actions moved onto each collector's own page. Player tags in URLs no longer carry an encoded hash, so the links from Overview into Tracking and Explore work. https://elixir.poapkings.com/updates#2026-09-10-58 https://elixir.poapkings.com/updates#2026-09-10-58 Thu, 10 Sep 2026 12:00:00 GMT 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 in the quietest possible way — your request was recorded, and the page did not move, so there was nothing on screen to tell you it had been sent. If you asked for access and never heard anything, the request is with us; nothing was lost. https://elixir.poapkings.com/updates#2026-09-10-59 https://elixir.poapkings.com/updates#2026-09-10-59 Thu, 10 Sep 2026 12:00:00 GMT 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 URL. The .txt surfaces (llms.txt, robots.txt) also declare UTF-8 now; a reader without a charset was showing an ellipsis as three symbols. https://elixir.poapkings.com/updates#2026-09-10-60 https://elixir.poapkings.com/updates#2026-09-10-60 Thu, 10 Sep 2026 12:00:00 GMT 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 days and weeks as shorthand, and every windowed answer echoes an applied block saying which window it used and whether you chose it, the tool defaulted it, or nothing bounded it; battles_decks no longer returns all-time without saying so. verbosity: compact is the one way to ask for less, on the roster, the current war, the level curve, your collection and the card catalog as well as the battle list. clans_roster and war_current take live: true for any clan, recorded or not, and battles_query can poll a player's log once before answering; live_fetch refuses a raw battle log, which never fit the delivery cap anyway, and points at that. The caveats on an answer are a notes list of single sentences plus a docs pointer into the page that carries the formulas, and the documentation grew four pages to carry them: Choosing a tool, the Glossary, The battle model and Time and clocks. The documentation, examples, changelog, updates and card catalog are also MCP resources, and the eleven examples are prompts, so a client that cached its tool list weeks ago can still read the manual. Connecting a client offers every capability, ticked, on the consent page instead of the read-only minimum. Every response says whether the event feed or a feedback reply is waiting, so an agent polls only when there is something to read. Two error codes are new so an agent can branch without reading English: no_subject when there is nobody to answer about, and result_too_large when the answer needs narrowing. https://elixir.poapkings.com/updates#2026-09-10-61 https://elixir.poapkings.com/updates#2026-09-10-61 Thu, 10 Sep 2026 12:00:00 GMT 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 lists come through. The rail's identity block shows the address you signed in with and leads to Profile, which replaces Settings & tier as the one page about your account: your email, how you sign in, your timezone, your tier with its slot meters and the upgrade request, and today's quota. Old links to Settings & tier land there. https://elixir.poapkings.com/updates#2026-09-10-62 https://elixir.poapkings.com/updates#2026-09-10-62 Thu, 10 Sep 2026 12:00:00 GMT 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 lists come through. The rail's identity block shows the address you signed in with and leads to a new Profile page: your email, your tier, how you sign in, and the timezone control, which moved there from Settings & tier. https://elixir.poapkings.com/updates#2026-09-10-63 https://elixir.poapkings.com/updates#2026-09-10-63 Thu, 10 Sep 2026 12:00:00 GMT 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, its links are absolute, the agent tool count is generated rather than typed, and the quota example names a reset that has not happened yet. Search matches by word instead of exact phrase, prefers pages that hold every word, says when it fell back to any word, cuts its excerpt around the densest cluster of hits, and names the section each match sits in; a page can be read one section at a time. Two examples changed too: the roster example is kinder to the members it names, and the scouting example compares POAP KINGS against the five clans in the Clans to Watch collection, twelve races each on record. https://elixir.poapkings.com/updates#2026-09-10-64 https://elixir.poapkings.com/updates#2026-09-10-64 Thu, 10 Sep 2026 12:00:00 GMT 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 under every window are the ones that were actually called, every number in an answer is from them, and the answers are written the way a model writes them, in Markdown, with the provenance in the sentence rather than in a chip. The home page's conversation and its three cards are the same three examples. The three builder examples read the documentation over MCP, which the service now serves through its own tools, so an agent asked how to set up a Discord bot answers from the Agents page itself. https://elixir.poapkings.com/updates#2026-09-10-65 https://elixir.poapkings.com/updates#2026-09-10-65 Thu, 10 Sep 2026 12:00:00 GMT 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 rail. The documentation got the rail the design drew for it: a search box, four groups with a glyph on every page, the tool families under Tools, the page's own sections under the page you are on, and the machine-readable surfaces at the foot; each page carries its lede, an outline on the right that follows you as you scroll, a link to edit it, and when it last changed. Data and Updates got their head rows and glyphs, and Updates now carries every contract version beside the product updates. The footer keeps to the same column as the top bar on a wide screen. And the service documents itself over MCP: three read-only tools return this documentation, the examples and this list, built from the same files the site renders, so an agent asked how to use Elixir MCP answers from the same text you read here. https://elixir.poapkings.com/updates#2026-09-10-66 https://elixir.poapkings.com/updates#2026-09-10-66 Thu, 10 Sep 2026 12:00:00 GMT 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 their own line. Settings & tier shows your slots and your quota with the same numbers Overview and Usage show, because all three now read them from one place. Feedback is a list of your notes with the maintainer's answer one click away, and a Send feedback button that opens the form in place. The rail carries counts on Collections, Connections and Feedback, a dot on Activity while notifications are unread, and a warning on Connections while a credential that no longer works is still being presented. Tracking tells players from clans at a glance and shows when each clan was last polled. Every record page ends with the docs that explain that kind of record. Four things that were simply broken are fixed: the collector page an operator opened crashed on a field name; the war-week lookup could not parse the form its own hint suggested; every clan record said it had never been polled; and the transcripts on this site named tools that did not exist while the page said they all did — every tool named under a window is real now and links to its reference. On the site, the home page carries the use-case cards, the pipeline, the counters and the machine-readable paths; the use-case pages have a rail of all eleven, live transcripts and setup buttons that go somewhere; the family page finally links to each product; the corpus page has an on-this-page rail; and Updates can be filtered by kind and jumped to by month. https://elixir.poapkings.com/updates#2026-09-10-67 https://elixir.poapkings.com/updates#2026-09-10-67 Thu, 10 Sep 2026 12:00:00 GMT 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 every width: it is the way into the product, and putting it behind a menu would cost a tap on the one thing most people came for. Both halves of the site render the same markup at every width and let a single media query decide which is showing, so the bar you see on a marketing page and the bar you see in the console are the same bar. With JavaScript off the six links are still in the page and still work. https://elixir.poapkings.com/updates#2026-09-10-68 https://elixir.poapkings.com/updates#2026-09-10-68 Thu, 10 Sep 2026 12:00:00 GMT 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 naming what was read to produce it, with the tools it called linked to their own reference pages so you can check that every one exists. Three chips switch between your play, your clan and your friends. The whole exchange is in the page itself and reads fine with JavaScript off. The counters moved to /data, which is now the corpus proof: five totals, a cumulative growth curve bucketed by when battles were PLAYED, what we collect and how long it is kept, and the machine-readable surfaces — all baked at deploy, so a crawler, an agent and somebody who has not signed in read the same thing. Eleven use cases got real pages, one per audience, each with the exchange that makes it concrete and the two steps to set it up. /family says what each POAP KINGS product is and how it fits, and puts the Clash Royale things we merely like in their own group with a byline that says outright they are not connected to us. The tool reference stopped being a wall: forty-four tools on one page are now eight family pages, one per group, nested under Tools in the documentation rail. https://elixir.poapkings.com/updates#2026-09-10-69 https://elixir.poapkings.com/updates#2026-09-10-69 Thu, 10 Sep 2026 12:00:00 GMT 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 now a report - a five-line readiness list saying whether your agent can answer about you yet and, for each line that is not done, what it is waiting for, plus your players and clans in brief and your tier's slot usage. Nothing on it can be got wrong, because every control moved to the page that owns it: Tracking is where players and clans are added, changed and removed, and Settings & tier is where the upgrade request and the timezone live. Every page now ends with the same docs strip, naming the pages that explain that page rather than a general link to the documentation. Status moved out of Data into its own Service section and takes the collector fleet with it, so the pages that answer whether the recorder is healthy sit together; the machine-readable /api/public/status is unchanged and still needs no session. Old links redirect. Below 900px the rail becomes a row above the content naming the section you are in, which opens into the same list - it never covers what you were reading. https://elixir.poapkings.com/updates#2026-09-09-70 https://elixir.poapkings.com/updates#2026-09-09-70 Wed, 09 Sep 2026 12:00:00 GMT 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 not store. It is kept now, and shows up on a player's profile and on every roster row as last_seen_in_game. It answers a question nothing else here could: last_recorded_battle only moves when somebody plays a battle we captured, so a member who opens the game daily without battling looked identical to one who has gone. It is also the rule the game uses to decide who is in a river race - members last seen before the race began are left out of it entirely - so a quiet member missing from the war roster can now be told apart from a recording gap. It cannot be backfilled: it starts filling from the next roster poll. https://elixir.poapkings.com/updates#2026-09-09-71 https://elixir.poapkings.com/updates#2026-09-09-71 Wed, 09 Sep 2026 12:00:00 GMT 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 left out the same five people, so what we served was right all along - just silent about the difference. war_current now returns participants_count, member_count and members_not_in_race, naming the current members the race roster leaves out. The game gives no reason for the omission, so neither do we; the reason reads not_in_race_roster and nothing is invented. The omissions cluster on the least active members, which is exactly where a leader is looking, so the gap being visible matters more than it being small. The behaviour is written up in the public Clash Royale API reference for anyone else who hits it. https://elixir.poapkings.com/updates#2026-09-09-72 https://elixir.poapkings.com/updates#2026-09-09-72 Wed, 09 Sep 2026 12:00:00 GMT 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 connected the usual way had no capability control anywhere. The agent's own page now edits them, with the same checkboxes and the same rules. A key issued before capabilities existed holds all of them, and is shown that way rather than as a key that can do nothing. Separately, renaming an agent could refuse every name with 'lower-case letters, numbers and hyphens' even when the name was perfectly valid: an agent's name is its live key's name, so an agent whose key was revoked has nowhere to keep one, and that failure was being reported as though the name were malformed. Each refusal now says which one it is, and the revoked-key case tells you to issue a new key first. https://elixir.poapkings.com/updates#2026-09-09-73 https://elixir.poapkings.com/updates#2026-09-09-73 Wed, 09 Sep 2026 12:00:00 GMT 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 a token's capabilities are read from the grant on every request. The list also covers your agents' and integrations' connections, which each authorize at their own address and hold their own grant - previously they appeared nowhere and could not be managed at all. Reading recorded data stays switched on for every connection, since a connection without it can do nothing. https://elixir.poapkings.com/updates#2026-09-09-74 https://elixir.poapkings.com/updates#2026-09-09-74 Wed, 09 Sep 2026 12:00:00 GMT 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 refusal it got pointed at a consent-page control that did not exist. The consent page now lists every capability your app did NOT ask for as an unticked checkbox. Tick one and it is added to the connection; tick nothing and the grant is exactly what the app requested, as before. Only capabilities Elixir MCP defines are accepted, the request that reaches the consent page is the one that was bound when your code was emailed, and the app is told what it actually received. https://elixir.poapkings.com/updates#2026-09-09-75 https://elixir.poapkings.com/updates#2026-09-09-75 Wed, 09 Sep 2026 12:00:00 GMT 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.request_id you can quote, instead of a bare 'Internal Server Error' or a bare 'rate_limited' string, and the rate limit sends Retry-After. three_crown_rate no longer counts a duel that summed three crowns across its rounds as a three-crown victory - numerator and denominator both exclude duels and boat attacks now, and head_to_head_battles is returned so the division can be checked. battles_performance returns decided_wins and decided_losses, because the documented win_rate formula could not be reproduced from the fields that were on the wire. Deck responses show the evolution form and tower troop that deck_hash is built from, so two decks with the same visible cards no longer differ by hash for no visible reason. war_current says day_kind and war_day beside season_id and returns decks_today as an explicit null with a reason off a war day, so a training day stops looking like a clan that no-showed. elixir_coverage reports measured_span and measured_hours, so a perfect completeness ratio over two days no longer reads as a fully captured week. The clan named when a connection opens is now the primary player's, and any others are named too. https://elixir.poapkings.com/updates#2026-09-09-76 https://elixir.poapkings.com/updates#2026-09-09-76 Wed, 09 Sep 2026 12:00:00 GMT 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 and empties at each one), jobs queued for a collector, jobs being fetched, and what was done this hour, with a countdown to the next tick and the due count broken down by endpoint. The bar fills against what the next tick can plan, so a bar past full means a backlog is forming rather than the normal between-tick pile. https://elixir.poapkings.com/updates#2026-09-09-77 https://elixir.poapkings.com/updates#2026-09-09-77 Wed, 09 Sep 2026 12:00:00 GMT 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. That bar is now shaded the way the Dashboard shades an unfinished day (and drawn as a dashed outline while still empty), its tooltip says 'bucket in progress' with the count so far, and each panel states its total (fetches in the last hour, fetches in the last 24 hours) beside the bucket size, so a short last bar can no longer be mistaken for a service that stopped fetching. https://elixir.poapkings.com/updates#2026-09-09-78 https://elixir.poapkings.com/updates#2026-09-09-78 Wed, 09 Sep 2026 12:00:00 GMT 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 response cap, versioning and the tools/list cache-buster, cursors and argument rules); a limits page with one table of every quota and rate limit and the exact refusal each produces; a recording and coverage page that says what adding a player or clan actually fetches, how often, how one recording is shared, what collections do, how to read freshness and completeness, and what live_fetch can reach. The quickstart has per-client steps for Claude.ai, Claude Desktop, Claude Code and any MCP client, and an honest note on ChatGPT. The agents page is a builder's guide with a complete on_behalf_of exchange and event-cursor code. Events lists every topic's payload floor. Roles, integrations, responses, privacy and operators were corrected against the code, and headings now carry anchors. https://elixir.poapkings.com/updates#2026-09-09-79 https://elixir.poapkings.com/updates#2026-09-09-79 Wed, 09 Sep 2026 12:00:00 GMT 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 floor and could be a day stale exactly when you looked. Second, the recorder now measures how fast each player has recently filled the ~30-entry battlelog and polls before half that time has passed, so a grinder's evening burst can no longer push battles off the log before they are recorded; the previous rule learned activity only from what a poll harvested, which is precisely what an overflowed log hides. The burst rule is rolling out to half of recorded players first so the two halves can be compared over the same hours. Profile snapshots of active players are taken every eight hours instead of every two, since the record keeps one snapshot per day. https://elixir.poapkings.com/updates#2026-09-09-80 https://elixir.poapkings.com/updates#2026-09-09-80 Wed, 09 Sep 2026 12:00:00 GMT 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 access requests and collector events did, and feedback waited for the next review pass. Each kind of notification has its own subject line, and notifications ride the best-effort lane of the mail relay so they can never delay or dead-letter a sign-in code. https://elixir.poapkings.com/updates#2026-09-09-81 https://elixir.poapkings.com/updates#2026-09-09-81 Wed, 09 Sep 2026 12:00:00 GMT 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, which are the console's own feature). Every tool, on both doors, now checks its arguments against its published schema before running, so a misspelled argument or an out-of-range value is a clear refusal instead of a silent ignore. The usage page shows your tier's real ceilings rather than the member tier's. Malformed ids in console requests answer 400 rather than a server error. And the API origins now accept only requests that came through the site's CloudFront distribution, so the caller address recorded on every call cannot be forged. https://elixir.poapkings.com/updates#2026-09-09-82 https://elixir.poapkings.com/updates#2026-09-09-82 Wed, 09 Sep 2026 12:00:00 GMT 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 shared API budget. Each tier also has an agent count now (member 3, leader 5, family 10, partner 25, admin and owner unlimited), enforced when an agent is created and shown on the Roles page. Separately, a refused OAuth token at the MCP door answered with a server error instead of the 401 challenge a client needs to re-authorize; it answers 401 now. https://elixir.poapkings.com/updates#2026-09-09-83 https://elixir.poapkings.com/updates#2026-09-09-83 Wed, 09 Sep 2026 12:00:00 GMT 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 before' is one call instead of a five-page sweep. badges_rarity and badges_holders make badges a dimension across every recorded profile, with one-off badges told apart from tiered ones. cards_synergy answers 'what is Witch played with' with co-occurrence, distinct players per pair and lift. players_names resolves up to a hundred tags to names without spending the live lane. Every response now carries meta.quota - calls and live fetches used and remaining, and when they reset - so an agent can price a plan instead of rationing an invisible budget. The event feed needs only the read capability. Deck and card meta shrink toward the corpus, not toward a player's own record, flag samples below thirty decided battles, and itemize what they excluded; performance windows separate decided head-to-head battles from boat attacks. Duel rows say how many games they hold and the legend says their crowns sum. Collection cards decode their forms (evolution, hero) instead of leaving a bit field to be misread as progress, and the card catalog serves max level on the in-game scale like everything else. https://elixir.poapkings.com/updates#2026-09-09-84 https://elixir.poapkings.com/updates#2026-09-09-84 Wed, 09 Sep 2026 12:00:00 GMT 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 there. Credentials of yours that stopped working and are still being presented appear above the list, counted per source per day. Agents already got this; the personal door has it now too. https://elixir.poapkings.com/updates#2026-09-09-85 https://elixir.poapkings.com/updates#2026-09-09-85 Wed, 09 Sep 2026 12:00:00 GMT 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. Refused attempts are counted per credential, per source, per day, and name the key when it is one of yours. Addresses are cleared after 30 days and refusal records deleted after 30 days; see the privacy page. Local clients redirecting to an IPv6 loopback address are now accepted alongside localhost and 127.0.0.1. https://elixir.poapkings.com/updates#2026-09-09-86 https://elixir.poapkings.com/updates#2026-09-09-86 Wed, 09 Sep 2026 12:00:00 GMT 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 every check on the request applied again and each authorization code still usable only once. https://elixir.poapkings.com/updates#2026-09-09-87 https://elixir.poapkings.com/updates#2026-09-09-87 Wed, 09 Sep 2026 12:00:00 GMT 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 impossible to enter and could exhaust its attempts. When a code is refused, the page now says which reason applies - superseded, already used, expired, too many attempts, or a code from the other flow - and what to do next. https://elixir.poapkings.com/updates#2026-09-09-88 https://elixir.poapkings.com/updates#2026-09-09-88 Wed, 09 Sep 2026 12:00:00 GMT 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 refused call never reaches the log. Your usage now counts what your daily limit counts: calls your agents made on your budget are included in the daily total and broken out separately, instead of being invisible until you were throttled. https://elixir.poapkings.com/updates#2026-09-09-89 https://elixir.poapkings.com/updates#2026-09-09-89 Wed, 09 Sep 2026 12:00:00 GMT 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 when you issue a new key. https://elixir.poapkings.com/updates#2026-09-09-90 https://elixir.poapkings.com/updates#2026-09-09-90 Wed, 09 Sep 2026 12:00:00 GMT 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 connection had no recorded clan membership while the same connection reported the clan by name. Agents with several clans default to their primary. Personal connections, explicit tags and leadership-scoped analytics are unchanged. https://elixir.poapkings.com/updates#2026-09-08-91 https://elixir.poapkings.com/updates#2026-09-08-91 Tue, 08 Sep 2026 12:00:00 GMT 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. Elixir Drop is the first consumer. Personal and clan-agent MCP connections keep their existing behavior. https://elixir.poapkings.com/updates#2026-09-08-92 https://elixir.poapkings.com/updates#2026-09-08-92 Tue, 08 Sep 2026 12:00:00 GMT 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; manual copying is available if clipboard access is blocked. The overview shares the same suggestions. New players see guidance while they wait for their first capture. https://elixir.poapkings.com/updates#2026-09-08-93 https://elixir.poapkings.com/updates#2026-09-08-93 Tue, 08 Sep 2026 12:00:00 GMT 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 resumption. Existing behavior is preserved. CI now runs the same complete verification gate as local development, including dead-code checks. https://elixir.poapkings.com/updates#2026-09-08-94 https://elixir.poapkings.com/updates#2026-09-08-94 Tue, 08 Sep 2026 12:00:00 GMT 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 statistical calculations are unchanged. https://elixir.poapkings.com/updates#2026-09-08-95 https://elixir.poapkings.com/updates#2026-09-08-95 Tue, 08 Sep 2026 12:00:00 GMT 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 level inputs and qualifying population. Their responses spell out that the legacy standard-error field is an approximation, not a confidence interval for the score. The methodology documents the formulas, independent rounding of displayed rates, sample floors, dependent observations, and limits of rolling-baseline and tenure comparisons. Earlier release descriptions claiming guaranteed rankings or improvement independent of spending have been corrected. https://elixir.poapkings.com/updates#2026-09-08-96 https://elixir.poapkings.com/updates#2026-09-08-96 Tue, 08 Sep 2026 12:00:00 GMT 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 two weeks as those samples become available. Copy a question with coverage and freshness checks built in, or open the same player's recorded data to inspect it. Connection consent and successful data reads are shown separately, including recent repeat use. Copying a question never counts as a successful answer, and a small sample never promises proof of improvement. https://elixir.poapkings.com/updates#2026-09-08-97 https://elixir.poapkings.com/updates#2026-09-08-97 Tue, 08 Sep 2026 12:00:00 GMT 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 last observed. Coverage compares battles over the actual time between profile observations instead of treating several days as one, and later-arriving battles improve that estimate automatically. Results too large to deliver now fail clearly with a traceable request ID. The methodology explains the statistics currently served and distinguishes descriptive comparisons from proof of improvement. https://elixir.poapkings.com/updates#2026-09-08-98 https://elixir.poapkings.com/updates#2026-09-08-98 Tue, 08 Sep 2026 12:00:00 GMT 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 building a new one, which changes its address and loses its place in its own notification feed. You can now issue a new key in place, suspend an agent and resume it later, read every notification it has been sent, see who it answers for, and see how many of your daily calls it is spending. That last one mattered more than it sounds: an agent spends YOUR budget, and until now those calls appeared nowhere, so you could run out with a usage page reading nearly zero. A suspended agent's key simply stops working, the same as any invalid key. Separately: players you add can now be marked as your alt, a friend, or someone you are just watching. That setting has existed since the day relationships shipped and your agent has been reading it all along - but nothing could set it, so everyone came out as 'watching'. Now your agent knows which players are actually you. https://elixir.poapkings.com/updates#2026-09-08-99 https://elixir.poapkings.com/updates#2026-09-08-99 Tue, 08 Sep 2026 12:00:00 GMT 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 still ran on the documentation and home pages, which sit on the same address and the same session, so nothing was actually kept out. The application now counts visits the ordinary way, exactly like the public pages, and the roundabout route through our own servers is gone. No account is ever attached to a view, and the sign-in page still loads no analytics at all, because your sign-in link travels in that address. One change you may notice in effect rather than appearance: a page about a specific player or clan now reports as the page it is, with the tag alongside it, rather than as a page of its own. https://elixir.poapkings.com/updates#2026-09-07-100 https://elixir.poapkings.com/updates#2026-09-07-100 Mon, 07 Sep 2026 12:00:00 GMT 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 engines saw a single page wearing ten names, and an AI agent fetching a documentation URL got the home page instead of the documentation. The content pages are now genuine pages, each with its own address, title and description, readable without running any code. The tool reference is generated from the server's own registry, so it can no longer fall behind what your agent actually sees - it had drifted five tools behind. There is a new page listing everything that has shipped, and machine-readable files at /llms.txt, /llms-full.txt and /tools.json for agents that would rather read one file than crawl a site. Nothing moved: every address you had still works. https://elixir.poapkings.com/updates#2026-09-07-101 https://elixir.poapkings.com/updates#2026-09-07-101 Mon, 07 Sep 2026 12:00:00 GMT 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 access stays read-only, and write actions require their own explicit grants. Tokens are also bound to this MCP server, so one minted for another resource cannot be replayed here. Existing connections keep read access; reconnect when an agent needs to make changes. https://elixir.poapkings.com/updates#2026-09-07-102 https://elixir.poapkings.com/updates#2026-09-07-102 Mon, 07 Sep 2026 12:00:00 GMT 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 for an archive covering many: war day 3 ended up meaning a different twenty-four hours for every clan, so no two clans could be compared and a re-run of the same data could land on a different day. Elixir MCP now follows the policy hour for every clan. We still record and report when each clan's race was actually seen to open, and by how many minutes it differed, so anyone working with a single clan can correct for it. https://elixir.poapkings.com/updates#2026-09-07-103 https://elixir.poapkings.com/updates#2026-09-07-103 Mon, 07 Sep 2026 12:00:00 GMT 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 collection now stops the recordings it was the only reason for, rather than leaving them running for a list that no longer exists. And two roster edits arriving at once no longer overwrite each other, so an add can never quietly drop somebody another add just put in. https://elixir.poapkings.com/updates#2026-09-07-104 https://elixir.poapkings.com/updates#2026-09-07-104 Mon, 07 Sep 2026 12:00:00 GMT 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 the same hierarchy as role changes. Separately, the site's edge was turning API refusals into blank successes: an unauthorized API call came back looking like an empty but successful answer instead of a refusal. Refusals now arrive as refusals. https://elixir.poapkings.com/updates#2026-09-06-105 https://elixir.poapkings.com/updates#2026-09-06-105 Sun, 06 Sep 2026 12:00:00 GMT 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 deeply to record what it names: everything including battles, or just the surface - a clan's roster, war and standings, or a player's profile. Editing membership is now a single box, one tag per line, and collection descriptions have room for real writing. https://elixir.poapkings.com/updates#2026-09-06-106 https://elixir.poapkings.com/updates#2026-09-06-106 Sun, 06 Sep 2026 12:00:00 GMT 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 identity appears, never the account behind it. https://elixir.poapkings.com/updates#2026-09-06-107 https://elixir.poapkings.com/updates#2026-09-06-107 Sun, 06 Sep 2026 12:00:00 GMT 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 in hourly buckets, which is where a collector that quietly stopped pulling its weight overnight becomes obvious. Empty stretches now draw as real zeroes instead of vanishing, so the time axis no longer lies about quiet periods. https://elixir.poapkings.com/updates#2026-09-06-108 https://elixir.poapkings.com/updates#2026-09-06-108 Sun, 06 Sep 2026 12:00:00 GMT 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 to fetch is idle, not broken, and only one of those numbers could tell you so. Both surfaces now show both times, labelled, on the same clock. The status page also dropped its queue panel - the queues it listed were retired weeks ago and six of the seven rows had been reading 'unavailable' ever since. https://elixir.poapkings.com/updates#2026-09-06-109 https://elixir.poapkings.com/updates#2026-09-06-109 Sun, 06 Sep 2026 12:00:00 GMT 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 they were installed with. We can now name a release in one command, and have named the current one. https://elixir.poapkings.com/updates#2026-09-06-110 https://elixir.poapkings.com/updates#2026-09-06-110 Sun, 06 Sep 2026 12:00:00 GMT 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 a 'token staged' note until it is revealed, links straight to the reveal when you own the collector yourself, and surfaces any failure instead of swallowing it. https://elixir.poapkings.com/updates#2026-09-06-111 https://elixir.poapkings.com/updates#2026-09-06-111 Sun, 06 Sep 2026 12:00:00 GMT 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 identity on every result, caps outstanding work, and quarantines a collector that takes jobs without returning them. Enrollment is just a name now (no IP collected), provisioning is a one-time download, and self-updates only install the exact binary hash the server names. Our two home collectors already run the new model - one in Go, one in Python, deliberately different so no single bad release can silence the fleet. https://elixir.poapkings.com/updates#2026-09-06-112 https://elixir.poapkings.com/updates#2026-09-06-112 Sun, 06 Sep 2026 12:00:00 GMT 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 with activity up to 90 days instead of dying at day nine), every recorded payload is verified to be ABOUT the player or clan it was requested for, delayed data can no longer overwrite newer snapshots, and deploys now run schema migrations before new code goes live. https://elixir.poapkings.com/updates#2026-09-06-113 https://elixir.poapkings.com/updates#2026-09-06-113 Sun, 06 Sep 2026 12:00:00 GMT 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 in place - members as rows, add and remove where you can see them - instead of the old squint-and-type row controls. https://elixir.poapkings.com/updates#2026-09-06-114 https://elixir.poapkings.com/updates#2026-09-06-114 Sun, 06 Sep 2026 12:00:00 GMT 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 GitHub repos - Elixir MCP, the collector, Elixir Agent, and Elixir Drop - so you can read the code behind any of it. https://elixir.poapkings.com/updates#2026-09-06-115 https://elixir.poapkings.com/updates#2026-09-06-115 Sun, 06 Sep 2026 12:00:00 GMT 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 privacy page. https://elixir.poapkings.com/updates#2026-09-06-116 https://elixir.poapkings.com/updates#2026-09-06-116 Sun, 06 Sep 2026 12:00:00 GMT 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 analytics at all. The privacy page has the full story. https://elixir.poapkings.com/updates#2026-09-06-117 https://elixir.poapkings.com/updates#2026-09-06-117 Sun, 06 Sep 2026 12:00:00 GMT 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 event fires the moment a new war day is first observed, and war_current now returns decks_today: named untouched/partial/finished lists, the nudge list. Point a scheduled agent at elixir_events and it can genuinely help run the clan - the recipe is in Docs > Tools. https://elixir.poapkings.com/updates#2026-09-06-118 https://elixir.poapkings.com/updates#2026-09-06-118 Sun, 06 Sep 2026 12:00:00 GMT 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). And every fresh battlelog poll is now capture-audited: if the rotating log fully rolled between polls, that's flagged as a possible gap, and the 24-hour gap count is public on Data > Status - so 'no gaps' is a measurement, not a promise. https://elixir.poapkings.com/updates#2026-09-06-119 https://elixir.poapkings.com/updates#2026-09-06-119 Sun, 06 Sep 2026 12:00:00 GMT 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 corpus has nobody by that name. https://elixir.poapkings.com/updates#2026-09-06-120 https://elixir.poapkings.com/updates#2026-09-06-120 Sun, 06 Sep 2026 12:00:00 GMT 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 rejects in amber. Public by design, refreshes every minute, and built mobile-first - bookmark it on your phone. https://elixir.poapkings.com/updates#2026-09-06-121 https://elixir.poapkings.com/updates#2026-09-06-121 Sun, 06 Sep 2026 12:00:00 GMT 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 beside the real name, and no other account ever sees it. https://elixir.poapkings.com/updates#2026-09-06-122 https://elixir.poapkings.com/updates#2026-09-06-122 Sun, 06 Sep 2026 12:00:00 GMT 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 keeps its Clash Royale card identity - the card is its name; your machine label stays underneath. https://elixir.poapkings.com/updates#2026-09-06-123 https://elixir.poapkings.com/updates#2026-09-06-123 Sun, 06 Sep 2026 12:00:00 GMT 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 headline change: Explore is no longer eight tabs of charts. It's a lookup - 'Do we have it?' - that opens deep-linkable records you traverse by clicking references: player to clan to war week to battle to deck. Every record page is one tool call, the same one your agent makes, with a raw-JSON view and a copy link. Charts now live only in Data, where corpus scale is the subject. https://elixir.poapkings.com/updates#2026-09-06-124 https://elixir.poapkings.com/updates#2026-09-06-124 Sun, 06 Sep 2026 12:00:00 GMT 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 add exactly one thing yourself: your own Clash Royale API key. Pairs with the new Go collector: a single binary for Mac, Linux, and ARM NAS boxes, self-updating from signed releases. https://elixir.poapkings.com/updates#2026-09-06-125 https://elixir.poapkings.com/updates#2026-09-06-125 Sun, 06 Sep 2026 12:00:00 GMT 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 card meta plus weekly trends for any segment: the whole corpus, a clan, or a collection like the pros. And Clan & War now carries Standings (win rates vs the clan median), clan-wide Pilot Scores, and the war Scouting Report. Every view is the same registry call your agent makes. https://elixir.poapkings.com/updates#2026-09-05-126 https://elixir.poapkings.com/updates#2026-09-05-126 Sat, 05 Sep 2026 12:00:00 GMT 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 bolded; reading here never marks anything seen for them). Collector shows what your machines have actually done: a 30-day fetch chart per collector, endpoint mix, points, and the running version. https://elixir.poapkings.com/updates#2026-09-05-127 https://elixir.poapkings.com/updates#2026-09-05-127 Sat, 05 Sep 2026 12:00:00 GMT 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 pages are crawlable: real content in the HTML, not just an app shell. https://elixir.poapkings.com/updates#2026-09-05-128 https://elixir.poapkings.com/updates#2026-09-05-128 Sat, 05 Sep 2026 12:00:00 GMT 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 that moderate small-sample extremes without guaranteeing rank order, distinct-pilot counts, and evolution forms kept separate. battles_trends adds weekly series for the same segments: watch a clan's (or the pros') win rate, volume, and active players move week over week. No tier lists, no opinions - sample sizes ride every number. https://elixir.poapkings.com/updates#2026-09-05-129 https://elixir.poapkings.com/updates#2026-09-05-129 Sat, 05 Sep 2026 12:00:00 GMT 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: whether that player or clan feeds your agent's event pipe. elixir_add_player and elixir_add_clan replace the watch tools. https://elixir.poapkings.com/updates#2026-09-05-130 https://elixir.poapkings.com/updates#2026-09-05-130 Sat, 05 Sep 2026 12:00:00 GMT 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 rung: owner (the super admin) sits above admin, and admins now see the console with day-to-day powers. Docs pages are also directly linkable now (like /docs/roles). https://elixir.poapkings.com/updates#2026-09-05-131 https://elixir.poapkings.com/updates#2026-09-05-131 Sat, 05 Sep 2026 12:00:00 GMT 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: the family tier and above create their own collections right on the Collections page. PUSH LANE: agents stop polling - the new elixir_events tool is a per-account event feed (new battles recorded, war week finished, feedback answered, tier changed) with implicit subscriptions: watching something IS subscribing. https://elixir.poapkings.com/updates#2026-09-05-132 https://elixir.poapkings.com/updates#2026-09-05-132 Sat, 05 Sep 2026 12:00:00 GMT 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 by everyone under Explore, and the maintainer curates them from a new Admin page. Old links redirect. https://elixir.poapkings.com/updates#2026-09-05-133 https://elixir.poapkings.com/updates#2026-09-05-133 Sat, 05 Sep 2026 12:00:00 GMT 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 instructions that ask agents to file friction on their own judgment - your agent reports friction so you don't have to. https://elixir.poapkings.com/updates#2026-09-05-134 https://elixir.poapkings.com/updates#2026-09-05-134 Sat, 05 Sep 2026 12:00:00 GMT 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 with a pros list - browsable by everyone, curated by the maintainer for now. https://elixir.poapkings.com/updates#2026-09-05-135 https://elixir.poapkings.com/updates#2026-09-05-135 Sat, 05 Sep 2026 12:00:00 GMT 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 include_curve: false for repeated scoring. The event-mode taxonomy it also asked about had shipped hours earlier. Responses are on each item via elixir_my_feedback. https://elixir.poapkings.com/updates#2026-09-05-136 https://elixir.poapkings.com/updates#2026-09-05-136 Sat, 05 Sep 2026 12:00:00 GMT 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 deserved better than a void. https://elixir.poapkings.com/updates#2026-09-05-137 https://elixir.poapkings.com/updates#2026-09-05-137 Sat, 05 Sep 2026 12:00:00 GMT 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' finds all the Chaos drafts). https://elixir.poapkings.com/updates#2026-09-04-138 https://elixir.poapkings.com/updates#2026-09-04-138 Fri, 04 Sep 2026 12:00:00 GMT 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, with a descriptive monthly trend that does not prove improvement or spending independence. war_rivals is the Scouting Report: observed war history for every rival clan your brackets have ever contained. No tiers, no opinions - every number ships its sample size. https://elixir.poapkings.com/updates#2026-09-04-139 https://elixir.poapkings.com/updates#2026-09-04-139 Fri, 04 Sep 2026 12:00:00 GMT 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). https://elixir.poapkings.com/updates#2026-09-04-140 https://elixir.poapkings.com/updates#2026-09-04-140 Fri, 04 Sep 2026 12:00:00 GMT 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. https://elixir.poapkings.com/updates#2026-09-04-141 https://elixir.poapkings.com/updates#2026-09-04-141 Fri, 04 Sep 2026 12:00:00 GMT 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 player, request clan recording, corpus-wide data insights, and the collector ladder. Reconnect to pick up the new names. https://elixir.poapkings.com/updates#2026-09-04-142 https://elixir.poapkings.com/updates#2026-09-04-142 Fri, 04 Sep 2026 12:00:00 GMT 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 and draw counts, and the validation layer rejects forged cursors, empty tags, and out-of-range arguments loudly. https://elixir.poapkings.com/updates#2026-09-04-143 https://elixir.poapkings.com/updates#2026-09-04-143 Fri, 04 Sep 2026 12:00:00 GMT 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. https://elixir.poapkings.com/updates#2026-09-04-144 https://elixir.poapkings.com/updates#2026-09-04-144 Fri, 04 Sep 2026 12:00:00 GMT 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. https://elixir.poapkings.com/updates#2026-09-04-145 https://elixir.poapkings.com/updates#2026-09-04-145 Fri, 04 Sep 2026 12:00:00 GMT 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 recorded battles only. https://elixir.poapkings.com/updates#2026-09-04-146 https://elixir.poapkings.com/updates#2026-09-04-146 Fri, 04 Sep 2026 12:00:00 GMT Long-lived API tokens for trusted services — the first step toward elixir-bot consuming Elixir MCP instead of running its own recorder. https://elixir.poapkings.com/updates#2026-09-04-147 https://elixir.poapkings.com/updates#2026-09-04-147 Fri, 04 Sep 2026 12:00:00 GMT 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. https://elixir.poapkings.com/updates#2026-09-04-148 https://elixir.poapkings.com/updates#2026-09-04-148 Fri, 04 Sep 2026 12:00:00 GMT 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. https://elixir.poapkings.com/updates#2026-09-04-149 https://elixir.poapkings.com/updates#2026-09-04-149 Fri, 04 Sep 2026 12:00:00 GMT 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. https://elixir.poapkings.com/updates#2026-09-04-150 https://elixir.poapkings.com/updates#2026-09-04-150 Fri, 04 Sep 2026 12:00:00 GMT Send feedback from the dashboard or have your agent call send_feedback — either way it lands on the maintainer's desk attributed to you. https://elixir.poapkings.com/updates#2026-09-04-151 https://elixir.poapkings.com/updates#2026-09-04-151 Fri, 04 Sep 2026 12:00:00 GMT 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. https://elixir.poapkings.com/updates#2026-09-04-152 https://elixir.poapkings.com/updates#2026-09-04-152 Fri, 04 Sep 2026 12:00:00 GMT The elixir-bot archive was replayed into the recorder: battles back to mid-May, war seasons 133-135, and daily snapshots from July. https://elixir.poapkings.com/updates#2026-09-03-153 https://elixir.poapkings.com/updates#2026-09-03-153 Thu, 03 Sep 2026 12:00:00 GMT Recording, the MCP server, clan war data, and the gateway fleet — live from day one.