What changed, newest first. Open one for the whole entry.
Privacy now says what Elixir keeps when you connect Discord or sign in with it: your Discord user id and username, used to sign you in and to tell your clan's Discord agent who you are. Discord's sign-in also gives Elixir your email address when Discord has v…
Read it ›Your profile has Connect Discord: Discord asks you to let Elixir know who you are, and your Discord account is connected to your Elixir account. After that, Continue with Discord on the sign-in page signs you in, and your clan's Discord agent knows it is you …
Read it ›A person can link their Discord account to Elixir from their profile (Discord's own sign-in proves it), so an agent's on_behalf_of: "discord:<user id>" now resolves without elixir_identify.
Read it ›A request to a path the JSON API does not have, such as GET /api/v1/models, now gets a 404 that links the JSON API docs and the OpenAPI document, whatever key it carries, where it used to get a 401 that suggested a key would help. Every real operation still n…
Read it ›Your MCP hourly limit now counts calls only: tool calls, and reading a docs page or a prompt. Connecting does not count. When a client starts up it says hello, lists the tools, resources and prompts, and sends a notification; none of that spends your 300 an h…
Read it ›Connecting no longer spends the hour. The MCP hourly bucket counts calls only: tools/call, resources/read, prompts/get and any method the door does not serve. A notification (answered HTTP 202), initialize, ping, tools/list, resources/list, resources/template…
Read it ›Path of Legends leagues carry the names the game uses: Master I, Master II and Master III, where Elixir said Master 1, Master 2 and Master 3. Champion to Ultimate Champion are unchanged.
Read it ›Elixir now writes Path of Legends leagues the way the game does: Master I, Master II and Master III, where the timeline and the milestone mail said Master 1, Master 2 and Master 3. Champion, Grand Champion, Royal Champion and Ultimate Champion are unchanged.
Read it ›When an Elder moves back to Member, the Leader Message Elixir Clan offers names the member and now reads "… moves from Elder back to Member for now, and Elder can come back." The old "Keep playing and it can come back" could read as a reason, and a demotion n…
Read it ›In Elixir Clan, How our messages sound is a new row in Manage ▸ Settings, beside the clan's model. The leader and co-leaders write, in their own words, how the clan's messages should sound, in up to 400 characters. The clan's model reads it both when it draft…
Read it ›The top of Elixir Clan's rail is now the clan you are in: its name, its tag, your role there and, while your player there is not verified, "unverified". If your players are in more than one clan, it opens to each of them, with the player you are there and you…
Read it ›When a leader drafts a promotion, demotion, welcome, removal or farewell line for one member, the clan's model is now told much more of that member's record: every war week they played in the clan over the last year, their donations here week by week and in t…
Read it ›Ladder's season home has a third panel beside "This week vs your last 4" and "Before and since your main deck": the season you are reading beside the one before it, in the mode you chose. Each side shows won–lost, win rate, net trophies where trophies move, a…
Read it ›When the leader or a co-leader comes to their clan with Actions waiting for them, Elixir Clan now opens on Actions rather than the roster: from the clan's address, from Clans, from the clan switcher and when coming back from sign-in. With nothing waiting, the…
Read it ›In Elixir Clan, Draft in our voice now starts from Elixir's own words for the Action and goes further: it says at least what the card would send, then two to four facts that belong to the member, each said for what it means. A draft that says less of the reco…
Read it ›The Timeline dot in the Console now clears when you open your Timeline, whether or not an agent is connected. The page marks what the record learned since your last visit New and draws a line under the last of them. Opening it changes nothing your agents have…
Read it ›On a wide screen the rail down the side of the Console, Ladder and Elixir Clan stays in view as a long page scrolls, with Send feedback at its foot. On a phone, the folded rail carries one mark when something waits on another page: an unread timeline, or Clan…
Read it ›The sign-in check that started deciding earlier today is back to only recording. Another service built the same way found real people whose browsers sent no check at all, and Elixir's few sign-ins so far cannot show that will not happen here. Every sign-in em…
Read it ›The Cloudflare Turnstile check on the sign-in forms, which until today was only recorded, now decides. A sign-in email no longer goes out when the page's check is missing or failed, so a script cannot fill someone else's inbox with sign-in mail.
Read it ›From the first war day on Thursday, every timeline that reached a tracked clan's war line failed instead of answering, including the Discord agents' event polls. It answers again, with the decks tally for the war day in progress.
Read it ›elixir_timeline answers again on a war day. From 11.8.0, a clan's war line on the war day in progress (its decks tally) threw before the timeline was built, so every read that reached a tracked clan's war day failed from war day 1 on 2026-10-15. The tally's a…
Read it ›The sign-in forms, on this site and on the page an app sends you to when it connects to Elixir, now carry Cloudflare Turnstile. It tells a person from a script that types someone else's address to fill their inbox with sign-in mail. It is usually invisible; C…
Read it ›Elixir's emails use a quieter frame, readable headings and fewer boxes. Reports keep their figures and coverage notes, and narrow screens have more room for names, records and card art. Actions waiting are rows with new ones marked. Feedback emails lead with …
Read it ›Clan Discord shows the channel, what it posts and its voice as three rows. Manage opens the controls you need; closing discards unsaved text. Posting problems remain visible, and deliveries are still available on the page.
Read it ›Closing Manage sharing discards an unfinished webhook URL and clears its messages and errors. Opening it again shows the saved sharing state. Saving or turning sharing off still requires its own button.
Read it ›Elixir gives the record and your next action more room. Product tabs and the left rail stay familiar, with quieter colours, clearer page titles and fewer framed panels.
Read it ›Verify’s decks and collector images load from Elixir’s own card-art mirror. The images are exact copies of Supercell’s originals, and these views no longer send your browser to Supercell for card art.
Read it ›Collectors need version 3.0.6 or later to fetch work and submit results. An older collector can still read its update instructions and update itself to the release Elixir names.
Read it ›When a sign-in or signup enrolls you in Elixir product news, Elixir sends Buttondown your browser's IP address along with your email address. This helps Buttondown check each subscriber individually when filtering spam. The privacy page describes this informa…
Read it ›Elixir's Console, Ladder and Clan now begin with a page rendered by the server, including your sign-in state. The sign-in form is ready as the page arrives, and a returning visit no longer waits for a separate session check before the account bar can appear. …
Read it ›When Elixir's maintainer answers feedback you filed, your timeline now carries that answer as an item of its own, with its words: what you wrote (its first 600 characters), the answer, its status and the version it shipped in. Two answers to two things you fi…
Read it ›battles_query explains how a river race duel row collapses its games (rounds_played, rounds, crowns summed across rounds) in a note, and until now every answer carried that note, even when no duel was on the page. It now comes only with a page that holds a du…
Read it ›What you connect to Elixir as yourself, Claude or another assistant signed in as you, can now read your own view of your clan in Elixir Clan with clans_my_view: the clan's policy summary, your own standing line, and the Actions waiting for you, each with a li…
Read it ›An answer to feedback is a timeline item of its own, with its words, and the answer email is now written from that item.
Read it ›battles_query carries its duel note (how riverRaceDuel rows collapse their games, rounds_played and rounds) only when the page holds a duel. Before, every page carried it and named fields no row on the page had. No field changes. JSON API 3.2.0 is unchanged.
Read it ›A person's own connection can read their own view of their clan in Elixir Clan.
Read it ›A verified player is its owner's alone: no other account may claim it as itself. A primary or alt on a tag another account has verified is refused, and when a tag is verified, every other account's primary or alt claim on it ends, with an account item on that…
Read it ›Sunday's collector activity email now covers Saturday 00:00 UTC to the next Saturday 00:00 UTC, the week that closed the night before it arrives (Friday evening in US time zones), instead of Sunday afternoon to Sunday afternoon. It still comes on Sunday at 14…
Read it ›Verifying a player now protects it: once you have verified a player, no other account can add it as its primary player or an alt, on the console, through an agent or through the JSON API. They are told what the Verify page says: if that player is theirs, sign…
Read it ›The page an app sends you to when it signs you in with Elixir, as Elixir Drop does, now lets someone new create an account there: enter your email and the code, and your free Elixir account opens once the code is proved, exactly as signing up on the website d…
Read it ›The worked example for the collector fleet, and a collector's own page in the console, now say what running a collector earns: the Family tier while it is active, and nothing else. The example no longer mentions points, call credits or bonus slots, and the co…
Read it ›Leader and Family are no longer asked for or granted: Elixir reads them every time you use it. You are a Leader while one of your verified players leads or co-leads a clan you track, and Family while a collector you run is active. The higher one wins, and a t…
Read it ›Raising your hand at Console ▸ Collectors ▸ Run a collector now approves it on the spot: you land on your collector's page with its token ready to reveal once, and nobody has to sign off first. What keeps the record honest is what every collector's results mu…
Read it ›Elixir checked every address it answers for what opens without signing in, and wrote the rule down. A battle's own page, with its link and share picture, is the one part of the record anyone can open. The status pages, The corpus and Recording now and their J…
Read it ›Reading your own record on the Console and on Ladder no longer counts against your daily tool-call quota, so an agent that has spent the day's calls never leaves your own pages refusing. Those reads still share the hourly limit of 300 calls with your own conn…
Read it ›A Remove from the clan Action now has a Rests on row: the member's last recorded battle with its time and mode (or that none is recorded), when they joined, and what the battle count on their profile did across Elixir's reads. Under it, every removal says tha…
Read it ›When you ask for your account to be removed, the account goes: your address, the players and clans you track, your nicknames, your agents, your connections, the mail sent to you, and your usage. A few pieces were left behind before and now go too: a timeline …
Read it ›Elixir records a player or clan because someone tracks it, and now for no other reason. The maintainer used to have a reason of their own that kept a recording going after everyone had stopped tracking it; that reason is retired, and the maintainer tracks fro…
Read it ›The documentation now says three things plainly. Elixir's own words, in every email, on the timeline, on Ladder and on this site, are written from the record by code, and Elixir pays for no language model; a model writes only where someone brings their own, a…
Read it ›A member's standout sitting is skipped once anything from an earlier sitting that day was posted about them: a move, a new best, a league or the sitting itself, not only a sitting post. A post that told several members counts for each only what it said about …
Read it ›A member's arena move, new best and standout sitting from one session of play are one post in the clan's activity channel. When part of it arrives after the post went up, the post is edited to tell it too while it is under two hours old and one of the channel…
Read it ›For your first 28 days of recording, Ladder's season home says how old your record is and offers one next step: Verify your player if it is not verified, Open Clan if it is and its clan is recorded, otherwise Follow a friend. It is a link, not advice about pl…
Read it ›Account → Overview now lists Player verified (needed to act in Clan) after Battles on record, with a link to Verify, so the step Elixir Clan needs before you can act in your game role is no longer something you find later. It is shown for your own players (yo…
Read it ›The signup form has an optional Your player tag field. A tag that is not a Clash Royale tag is refused on the form before any email is sent, and an empty field is fine. Once you verify your email, the new account tracks that player as your primary and opens o…
Read it ›Inactivity is the days since a member's last recorded battle, and a member past the policy's removal day becomes a Remove from the clan Action for the leader and co-leaders again. Removal action at is now the day itself: with at risk at 7 and the removal acti…
Read it ›A leader or co-leader kicked or demoted in the game no longer keeps their powers in Elixir Clan until the clan's next roster read. Before the leader or a co-leader changes anything, Clan checks that the roster was read from the game within the hour; if not, E…
Read it ›Elixir cannot yet prove that a quiet member played no battle in any mode, so Elixir Clan no longer raises removal Actions it could never let you complete. The policy's Inactivity tab is labelled Not yet enforceable and says why; its numbers stay editable, and…
Read it ›Collector points and credits are retired, and tiers are earned in the game: running an active collector earns its operator the Family tier and nothing else, and a verified player leading or co-leading a clan the account tracks earns Leader. There is no reques…
Read it ›Elixir cannot see the channels it posts to, so the people who can now tell it how a post read there. On a timeline's Discord panel, and on Elixir Clan's Actions ▸ Discord and Social ▸ Discord pages for leaders and co-leaders, each delivered post has 👍 and 👎…
Read it ›About a day after Elixir posts a message to a Discord channel (a timeline's cross-post, a clan's Actions or its activity channel), it now reads that message back once, the next time it delivers to the same channel: whether it is still there, how many of each …
Read it ›Elixir now keeps a record of every message it posts, edits or decides not to post in a Discord channel, for a timeline's cross-post, a clan's Actions and a clan's activity channel, so its operators can judge the posts' quality and fix what is wrong without be…
Read it ›When the clan's model edits Elixir Clan's Discord activity channel, its post for a departure may now add only a thank-you or a farewell in English ("Thanks for everything!", "Good luck out there!") around Elixir's sentence for it. Anything else beside that se…
Read it ›On Elixir Clan's Social ▸ Discord page, Preview the last 5 in this voice now shows what the clan's model would do as the channel's editor with the five newest stories from the last week, in the voice in the box: each post with the stories it tells and Elixir'…
Read it ›With the clan's own model key and the leaders' voice set, a clan's activity channel (Elixir Clan's Social ▸ Discord) is now edited by the clan's model rather than rewritten line by line. A few minutes after the activity lands, the model is handed the stories …
Read it ›A clan's activity channel (Elixir Clan's Social ▸ Discord) no longer copies the timeline line by line. It now works as an editor. What one battle did (an arena reached, a new best, a promotion) is one post. The same milestone reached by several members at onc…
Read it ›A new-best moment could read as a contradiction: "set a new best of 12,032 trophies, crossing 12,000, ... +26 to 12,005". The best was reached later than the battle that crossed 12,000. The moment now tells the crossing, then the peak after it: "passed 12,000…
Read it ›A timeline cross-posted to Discord, and a clan's activity channel, used to open every line with the time the item happened. Discord already shows when each message was posted, so the line now starts with what happened. Only an item that is more than three hou…
Read it ›Privacy now says what happens when a clan's leaders add their own Anthropic key: Elixir Clan sends Anthropic what it needs to draft the clan's messages, member names included, on the clan's key. It also says what the clan's two Discord channels, one for Actio…
Read it ›When the clan's own model rewrites the activity channel's posts, each member it writes about now comes with the clan's awards they hold, as the leaders announced them this season and last, and, while the channel posts Milestones, their last three moments from…
Read it ›Settings and the Clan docs now say exactly which notes the clan's model is sent. What you type in What should it say? when you draft is sent as you wrote it, beside what Elixir keeps about the clan in its leaders' own words, such as its recruiting words, its …
Read it ›"Draft in our voice" used to tell the model almost nothing, so its drafts came back generic. Now it is told what Elixir records: the clan (its name, recruiting words, goals, member count and last war weeks), the Action's own evidence, the member it is about b…
Read it ›When your timeline is cross-posted to Discord, a sitting posted while it was still being played used to stay "still going" if nothing else happened afterward. Elixir now notices when such a sitting has gone quiet and edits the line to its final count, within …
Read it ›Your timeline's cross-post panel now lists the last 20 lines it delivered over the past 30 days, along with how many were not delivered. Each line shows what happened to it, in Discord's words when Discord refused it. If a clan you are in also posts its activ…
Read it ›A sitting only partly played with a 2v2 partner now says how much of it was with them ("20 battles in one sitting, 1 of them with Bea in 2v2"), instead of reading as if the whole sitting was. A long window's sitting details are also faster to read. MCP 11.11.…
Read it ›Elixir Clan now posts a clan's Actions to Discord in Action number order, up to ten at a time and spaced under Discord's limit, and looks again a minute later, so an Action completed or declined is edited in the channel within minutes instead of at the next v…
Read it ›When Discord refuses one line of a timeline cross-post or a clan's activity channel, only that line is skipped now, and the page shows what Discord said; before, the lines after it were dropped too. Lines go to a channel at most about 25 a minute, under Disco…
Read it ›A standout sitting on your timeline now says how it went: the best win in it (the battle, the opponent and their trophies, the crowns), and the battle that crossed each milestone. A 2v2 sitting names the teammate, so two clanmates who played together read as …
Read it ›The clan's Anthropic key and its monthly cap are the leaders' to set; which model does each job is now Elixir Clan's choice, shown read-only in Manage ▸ Settings. Claude Opus 5.5 drafts the recruiting pitch and the messages on Actions, and Claude Sonnet 5.5 r…
Read it ›GET /api/v1/feedback now honours feedback_id and verbosity=compact, as the 3.2.0 reference says; on 11.10.0 they were ignored, so a compact read returned full bodies and marked them read. A maintainer's needs_info answer always carries a new question. MCP 11.…
Read it ›Your feedback list can now come back compact: each item's title, status and whether it has an answer, without the bodies, so a long history fits on one page. Read one item whole by its number, with the replies that follow it and the items that name it as rela…
Read it ›A sitting's battles_performance follow-up now covers the sitting's last battle as well, so its totals match the item. A player's own move to or from a clan now leads only to that player's summary, since the clan may be one nobody records; a clan's own member …
Read it ›The timeline says that something happened. Each item on a full read now also says where to read more: the reads that tell the rest of that story, each a tool and the arguments to call it with. A sitting leads to its own games and to the performance over its s…
Read it ›A window that starts partway through a sitting now shows the whole sitting, every battle of it, rather than just the battles after the window's start. Reading an item's evidence back works with only its original window, even for an item a poller learned late.…
Read it ›A timeline item's sentence no longer starts with a time, so it reads right wherever it is posted. Its time comes as fields instead (at_unix for a renderer's own stamp, local in your time zone), and the feed is ordered by when each story finished. One story is…
Read it ›Timeline moments carry more of how they happened, and a moment proved late comes back as the same story.
Read it ›Feedback you can work through: a compact listing, one item read whole, related items, and a question status.
Read it ›elixir_timeline items say where they lead. On a full read, each item carries follow: the reads that expand it into its story, each a tool and the arguments to call it with, built from the item itself.
Read it ›Corrections to 11.8.0's elixir_timeline. An occurred read builds a sitting begun before from whole. An evidence read with no basis finds an item from either kind of window. A member_away's date is in the reader's time zone. Two notes 11.8.0 dropped are back.
Read it ›elixir_timeline is publication-grade: an item's text is a time-free sentence safe to post as it stands, its time comes as fields, one story is one item, and every item says whether it may be published. Feedback #373-#376.
Read it ›When a player's recorded battles fill the last page exactly, Explore no longer offers Older battles onto an empty page, and an agent paging battles_query gets a null cursor on that page instead of one more empty read. MCP 11.7.3 and JSON API 3.1.0 unchanged.
Read it ›Adding a player still asks the game for its profile at once, so a wrong tag or the player's clan shows within minutes. You and your agents now get one of these first reads a day for each player slot you have; a player added past that is still recorded, and it…
Read it ›A player's battle list in Explore shows Older battles again whenever there are more recorded battles than fit on the page, so you can read their history past the first page; the link was missing for everyone. MCP 11.7.2 and JSON API 3.1.0 unchanged.
Read it ›The players and clans a suspended agent tracks no longer count against your recording slots. Because they no longer take a slot, they are no longer recorded either, unless you or someone else still tracks them, so the record has a gap for those until the agen…
Read it ›A suspended agent can now be removed from view, from its console's Settings. It leaves the console's agent switcher and the Agents table for a folded Removed agents list at the foot of the Agents page, so the agents you run are the ones you see. Nothing is de…
Read it ›The privacy page now says what happens when you cross-post your timeline, or an agent's, to a Discord channel: each new item is posted there, where Discord keeps it under its own terms and everyone in the channel can read it. Elixir keeps the webhook sealed a…
Read it ›A clan's leaders can now post its activity to a Discord channel of its own, from Discord, a page of its own in Elixir Clan's Social section. Connect a webhook (not the one Actions go to) and the clan's timeline is posted there as it happens, as members read i…
Read it ›The clan's model list in Settings was meant to refresh itself about once a day, and it never did: each refresh stopped before it asked Anthropic. It now works, so a key added before Claude Haiku 5.5 and Claude Sonnet 5.5 offers them the next time a leader ope…
Read it ›The game's roster sees only that a member went, not whether they left or were removed, yet the timeline said "left" for both. A departure now says the member departed the clan. When a leader tells Elixir Clan which it was, the timeline says the member was rem…
Read it ›Your timeline can now be posted to a Discord channel as it happens. On Console ▸ Timeline, paste a channel's webhook under Cross-post to Discord and turn it on; for an agent, its owner does the same on the agent's timeline, and the channel gets the agent's cl…
Read it ›The leader or a co-leader can now connect a Discord webhook in Elixir Clan's Settings. Each open Action that leaders or elders can take is then posted to that channel as one short line, naming the member, with a link to the Action that draws no preview. When …
Read it ›The skip_empty check that lets an empty timeline poll answer at once was slow when the reader asked for quiet_crossed, the moment a member goes quiet: it looked at every recorded battle to find one. It now looks only at the battles of the players the reader f…
Read it ›Agents that poll your timeline every few minutes, like the clan's Discord agents, mostly find nothing new, and each poll still read every subject's summary. elixir_timeline now takes skip_empty: true. When nothing in the window could be news for that reader, …
Read it ›battles_query's next_cursor is null on the last page even when that page is exactly full, as its schema promised; a full final page used to carry a cursor that opened an empty page.
Read it ›A departure's sentence no longer says a member left when they may have been removed (Jamie: a kick is "was removed", never "left", wherever the timeline is told).
Read it ›A timeline poll that finds nothing can now cost almost nothing. Most polls of elixir_timeline find no new item, and each one still read every subject's summary.
Read it ›The Monday clan report now shows how the week compares. War decks: the race's war decks used out of those possible (four a war day up to the finish, every day in Colosseum, for each member on the roster when the race closed), beside each of the four races bef…
Read it ›Ladder's season home now sets the game week so far beside the four game weeks before it, in the mode you are looking at: your win rate, three-crown rate and (on Trophy Road and Path of Legends) net trophies, each with the battles it is over. Game weeks run Mo…
Read it ›For a minute or two after a season roll, the game has created each clan's new river race but has not drawn its bracket, so the race has no clans yet. A live read of the race in that window used to fail with an error about a rejected payload. It now says plain…
Read it ›On Ladder's Cards page, the cards across the table from you and the opponents you met again can now be read most losses first: choose Most losses beside them. It is your choice, not the page's: the page still opens most battles first. A card is listed only fr…
Read it ›Earning a legendary badge now sends a milestone email when it happens, like a new arena or a new league, and it leads the note beside a new best. It is no longer counted in Tuesday's Arena email, which still counts your cards unlocked and badge levels. Each l…
Read it ›A milestone email now comes only for a big first: a new arena, a new league in Path of Legends, a new best trophy band, an Evolution or Hero form unlocked, or a career milestone (every 1,000 career wins, and each Collection Level step). Cards unlocked and bad…
Read it ›Ladder now has a Season switch beside the page's freshness: the current season, the last one, and every season your player has battles in since Elixir started recording them, named Season 136 as everywhere else. The season is part of the address (/ladder?seas…
Read it ›The hourly limit on MCP calls, 300 an hour, now belongs to whoever made the call. Each of your agents has its own 300, so one busy agent can no longer use up the hour for you and your other agents. Your agents still spend your daily tool calls and your live f…
Read it ›live_fetch, the raw read of the game an agent can make, now only fetches: the answer comes back to the agent and nothing of it is kept, so asking about a player nobody tracks no longer puts them on the record. To keep someone's history, track them. A live rea…
Read it ›The privacy page drops a sentence saying AI models write some of Elixir's mail and help with the feedback you send. Elixir's reports about your play are built from your record, not written by a model. Nothing else on the page changed. MCP 11.5.0 and JSON API …
Read it ›Elixir's card answers now carry each card's art, one image per form the game lists (the card, its Evolution and its Hero), served from Elixir itself. Ladder, battle pages, the Console, card pages and share images draw the art the answer names: a card played a…
Read it ›A new account now starts on the time zone of the browser you sign up from, so the Console, Ladder and your emails tell time on your clock from the first visit instead of UTC. If you open the sign-in link on another device, the account still takes the zone of …
Read it ›A tag Clash Royale does not know now shows Tag not found within seconds of adding it, as an error on your player's page with the fix right there: type the right tag and Elixir tracks it instead (as your primary, if the wrong one was), or stop tracking it. The…
Read it ›Ladder's nights and season dates now name their zone ("6:28 – 7:14 pm CDT"), and a battle's page reads on the same clock as the Console and Ladder when you are signed in, so one battle never shows two times. An account starts at UTC; until you choose a zone, …
Read it ›Console ▸ Overview and Ladder's season page now offer Bring your clanmates once your primary player's clan is on record: a line for clan chat that fits the game's 200 characters and steers around its chat filter, a longer note for Discord or a message, and yo…
Read it ›Once your primary player's profile shows their clan, Elixir now follows that clan for you at activity scope, so your clan's week comes in Monday's email. Only your primary, only a player in a clan, never past your clan slots and never in place of a clan you c…
Read it ›An address that leads nowhere now answers with an Elixir page and a true 404, with the way back to the home page, the docs and the Console, instead of a bare storage error. Ladder, signed out, says what it reads back and offers Create your account, which brin…
Read it ›The models offered in Manage ▸ Settings now stay current without adding the clan's key again: when a leader opens Settings and the list is a day old, Elixir Clan asks Anthropic which models the key can use, the same free check as adding a key. A key added bef…
Read it ›When a leader adds the clan's Anthropic key and it cannot reach Claude Sonnet 5 or Opus 5.5, Elixir Clan now starts it on Claude Haiku 5.5 instead of Haiku 4.5. A clan that already chose a model keeps it, Haiku 4.5 included. If the model declines to write a d…
Read it ›Send feedback now sits at the foot of Ladder's and Elixir Clan's rail as well as the Console's, and Elixir Clan adds Report this beside an action, Standing and the award races, carrying the thing on screen with your note. Clan's separate feedback pages are go…
Read it ›Feedback is now one record wherever you file it: over MCP, the JSON API, the Console, the docs or an email's footer, with Ladder and Elixir Clan joining next. Every item lands in one queue and is answered there, and elixir_my_feedback lists all of yours. Agen…
Read it ›The documentation now describes only what Elixir does today: open signup, Clan inside your Elixir account, Ladder beside the Console, six kinds of email and the card catalog's facts. Retired pages and sections are gone, including War decks, Leaderboards, Card…
Read it ›On the smallest phones, the top bar keeps its logo, full product label and account control within the screen. Long account names wrap in the menu. On narrow phones, battle decks stack while keeping their two rows of four cards, and player names have room besi…
Read it ›Back now leaves a feedback form opened from an email, including after sign-in; Forward returns with the email attached. If your clans cannot be read, Overview and Tracking keep earlier data and offer a read-only retry instead of an empty list or endless loadi…
Read it ›Player records and public battles keep their place through sign-in. An emailed feedback link opens its form with the email attached, and a login link in another tab keeps the requesting screen's destination available too. Code and approved cross-device sign-i…
Read it ›A river race still matchmaking is no race yet, never an error. For a minute or two after a season roll the game has created a clan's new race but not drawn its bracket, so the race has no clans. A live read that landed then failed with live_unavailable ("a pa…
Read it ›The cards and players you lost to most can be read first, as a choice: battles_cards and battles_opponents take sort: "losses", and every opponent row carries its level gap. The default order is unchanged.
Read it ›Card art is Supercell's, hosted unaltered: each art URL now names a byte-identical copy of the image the catalog's iconUrls name, one file per card and form (for example /assets/cards/26000042_hero.png), never resized, re-encoded or otherwise changed. Show it…
Read it ›live_fetch only fetches: the payload comes back to the caller and never enters the record. Before, its read was admitted like a scheduled poll, so a raw read of a player nobody tracks left their profile, collection and badges in the record.
Read it ›Card responses carry each card's art: one image per form the Clash Royale catalog lists (base, evolution, hero), served from Elixir's own origin, so an agent or page can show the card without building a file name or calling Supercell's CDN.
Read it ›The first time Elixir reads a clan's roster is a baseline, not a wave of joins: elixir_timeline and players_timeline no longer say a player joined a clan they were already in when Elixir first saw them there.
Read it ›Adding a player now reads its profile once straight away, from the live lane within the one rate budget and at no cost to the caller, and Elixir follows the primary player's clan for the account at activity scope as soon as a profile shows one (accounts made …
Read it ›Feedback is one system for all of Elixir: what you file over MCP, the JSON API, the Console, Ladder, Elixir Clan, the docs or an email's footer is the same record, answered in one queue, and elixir_my_feedback returns all of it wherever you filed it.
Read it ›elixir_examples describes the ten worked examples it serves, and no longer names one that is not among them. Wording only: no arguments, response fields or JSON API 3.0.0 operations change.
Read it ›Send me Elixir product news is checked by default on the sign-in/create-account form. Uncheck it before asking for your email to open a new account without newsletter enrollment. Your code or link keeps that choice, while existing newsletter choices and unsub…
Read it ›A tracked player's own clan is still read for their membership and role, but when nobody tracks that clan Elixir no longer keeps its other members or its daily numbers; track the clan to keep them. A one-time correction also removes what the retired leaderboa…
Read it ›The last two weeks beneath your year of battles now wrap capture labels within the phone's width, keeping UTC dates, recorded counts and win/loss results together. Unknown capture stays explicit. MCP 11.2.3 and JSON API 3.0.0 unchanged.
Read it ›Your year of battles now uses comparable profile intervals to distinguish covered quiet days from missing capture. A successful poll cannot turn an empty day into zero. Recorded battles remain visible with incomplete capture, the year reaches today's UTC date…
Read it ›Adding a player opens their saved-tag confirmation and capture progress. Read a dated profile or browse captured battles directly, including older history; pending capture has no guaranteed arrival time, and failed attempts leave saved information available. …
Read it ›The public guides now describe verified member signup instead of an approval-gated beta, factual mode reads instead of retired meta tools, the completed retired-table cleanup, and explicit integration resources without recording enrollment. No account, quota,…
Read it ›Days played keeps captured battles visible and only calls a day quiet when complete observation intervals cover it. Missing, partial and stale coverage no longer becomes a break from play. Clan waits for your membership record instead of telling you to join a…
Read it ›Your week in the Arena features the most-used deck in your busiest non-war mode. Its battle count, wins, losses and level gap now describe that mode alone, even when you played the same cards in Events and Trophy Road. Previously sent emails stay archived as …
Read it ›Season, beside The week in Clan, shows recorded war decks, period points and contributors across each race. Current and former member readings count once, with open races and partial capture clearly marked. Every clan member can read it. MCP 11.2.3; JSON API …
Read it ›Console now points to your next step in Tracking or Ladder instead of scoring optional setup as unfinished work. Clan war history and AI clients are clearly optional. The record distinguishes pending capture, a profile, recent or older battles, and recording …
Read it ›Tracking shows where to find your player tag and distinguishes starting recording from proving ownership. Accounts with no comprehensive clan slots use activity recording, and AI setup is explicitly optional. Clan signup takes you straight to email verificati…
Read it ›Choose a captured battle from Ladder’s Days played, inspect its record, and add your own context about why it mattered. Preview before copying the message or using your device’s Share sheet. Your words travel alongside the existing public battle link; the lin…
Read it ›The public history chart now says what it counts: battles still in Elixir, grouped by when they were played. It separates the displayed window from the full retained total and shows when its published snapshot was fetched. Removed records are excluded; protec…
Read it ›Anyone can open a free member account by verifying an emailed link or code. Start in Console by adding your player, read your record in Ladder, and open Clan with the same account. An agent or collector is optional. Collector approval and recording limits sti…
Read it ›Weekly reports label the completed week they cover, even when a new season has begun by send time. A clan report names a closed race's season and river race week together. Previously sent emails stay archived as sent. MCP 11.2.3 and JSON API 3.0.0 unchanged.
Read it ›When a season rolls, the Clash Royale API has no river race for a few minutes to over an hour. Elixir took that gap for a clan with no race and stopped reading every race for a day, so the first training day of Season 137 went unread for the morning. A race t…
Read it ›New routine Actions start with clan chat. Award updates, final awards and important rule announcements also offer a durable Inbox message. Switching channels keeps your edits, and sent receipts preserve the channel and reviewed words. Review later leaves the …
Read it ›For a minute or two after a season rolls, the Clash Royale API answers for a new river race that has no clans yet. Elixir still sets that answer aside and reads the race again soon, but it no longer counts it as a rejected fetch on the collector's page, the s…
Read it ›Elixir checks the final log once after an unfinished recorded colosseum season's scheduled end, even when the next race is not available yet. This gives final standings and Clan award inputs a chance to arrive during standby. Only recorded API results can est…
Read it ›Once Elixir records a newer river race, it schedules one catch-up for the preceding race log if final closure is still missing. Final standings and Clan award inputs can then arrive without waiting for the next daily poll. The calendar alone never finalizes a…
Read it ›An observed unfinished colosseum owes one budgeted river-log check after its canonical season's nominal end, even while the current-race endpoint is in 404 standby. The existing current-race 404 hold, rate budget, live reserve and bounded retries remain intac…
Read it ›When the recorder observes a newer river race while its immediate predecessor has no recorded closure, the preceding race log becomes due for one catch-up instead of waiting for the daily poll. The normal rate budget, live reserve and bounded retries still ap…
Read it ›Weekly participation can read ordinary battles from the existing covering index and inspect participant sides only when checking boat defenses. Awards, Standing and The week keep the same recorded battle and ranked counts, with fewer broad database reads. MCP…
Read it ›Opening a searched roster member in another tab keeps the search out of analytics referrers as well as page addresses. Same-origin referrers use the existing normalized page routes; external referrers are unchanged. MCP 11.2.0; JSON API 3.0.0 unchanged.
Read it ›Members and Elders opening Settings directly can read the clan's Social status without a leader-only switch. The recording summary explains its existing leader access instead of leaving an empty section. Leaders and co-leaders keep their controls; server perm…
Read it ›A Member opening Scout’s address sees that it is for Elders and leaders, with no scouting form or live read. Elders and leaders keep their existing access, and the form has a persistent Player tag label. Server permissions are unchanged. MCP 11.2.0; JSON API …
Read it ›Closed Actions and roster search survive detail pages, browser history and refresh. Current members’ names in Award races, Standing and The week open their existing recorded activity, whose battle-mode names now match battle detail. Denied reads explain acces…
Read it ›Award races now display the place after season donations break equal-point ties. A shared-place marker appears only when both values tie, including a tie at the last displayed row. Viewing an older season keeps the current update button clearly labeled with i…
Read it ›The Discord agent’s scheduled war-deck check now follows saved participation intent. Participating permits it only in the right war phase after a fresh policy read; not participating skips it, and unspecified or unavailable context makes it wait. The agent re…
Read it ›The policy draft summary shows explicit Clan War participation intent, and its question now comes first in About. Clan Wars scoring links back to it without changing the draft. Small-clan leaders can open Prepare policy from the roster while operational manag…
Read it ›An assigned agent may read its clan’s explicit war intent, policy revision and timestamps only through a separately approved grant. Every read checks its actual owner, current assignment and verified membership; other private policy details remain unavailable…
Read it ›Leaders can specify whether their clan intends to participate in Clan Wars on Policy → About. This remains separate from counting war decks toward minimums and Elder. Existing policies start as Not specified, and starting points preserve the intent you choose…
Read it ›Removal recommendations, words, drafting, completion and reopening stay held while absence of battle activity across every mode is unproved—even at the exact profile observation time. Captured play and positive counter intervals still protect members; role pr…
Read it ›Successful admitted profile reads update their observation time even when the recorded values stay the same. They earn no new facts or collector points, preserve newer roster values and cannot regress on older deliveries. This does not prove absence of battle…
Read it ›Promotion and demotion evidence counts are separate from removal triage. Jump to a Board group, read wrapped member labels and scroll narrow tables within the page. Policy help describes excluded Elders as Protected. Removal checks and freshness rules are unc…
Read it ›Board distinguishes protected members, members who are not currently removal candidates, held evidence and eligible recommendations. Roster-only rows are not profile observations; missing days remain gaps. Closed Action warnings preserve the audit without sug…
Read it ›Positive profile-counter intervals protect members even when battle details are missing. Removal Actions check current evidence separately from saved evaluations; unknown capture and unmeasured time hold the recommendation and withhold removal words, drafting…
Read it ›Verified leaders can prepare Policy before a clan reaches ten members; operational management stays paused until then. The editor explains minimums, preset effects and save timing, clears stale previews and protects newer versions. Roster names and member Act…
Read it ›Welcome drafts use the Action's saved return or career detail. After a leader confirms Kicked or Left, departure drafts use that confirmation and recorded tenure when known. Changed context clears older drafts; names, private notes and removal reasons stay lo…
Read it ›A sitting summary can include games played after its standout milestone. The evidence panel now explains both counts and time spans. Timeline sentences wrap to keep game controls visible on desktop, and Close returns you to the original row after a long evide…
Read it ›Open recorded games from a Timeline sitting or a proved crossing. Evidence stays tied to its original moment as late proof arrives; missing games and unknown capture completeness are said plainly. Game pages open from a read-only panel, with ordered pages for…
Read it ›Extra weekly and season-reset snapshots preserve recorded counters without announcing another donation reset from an older baseline. Weekly high-water marks and Clan award inputs are unchanged. Contracts unchanged.
Read it ›Message copying and action decisions wait while a voice draft loads. Text over the game's field limits stays editable with a reminder to shorten before copying. Review and send the finished words, then record delivery. Contracts unchanged.
Read it ›Weekly clan participation reads resolve participant side only inside the bounded boat-defense lookup, allowing the existing player/time covering index to serve ordinary battle rows without a broad heap scan. Current and former-member battle and ranked counts …
Read it ›clans_context exposes only eight policy-context fields to an agent with an explicit credential-bound grant for its actual owner and assigned clan. Current verified owner membership, ownership, assignment and revocation are checked on every read. Missing or un…
Read it ›Successful admitted profile reads advance the daily profile observation time even when the projected values are unchanged. Timestamp-only updates earn no new facts or collector points, preserve newer roster values and cannot regress on older deliveries. No re…
Read it ›Timeline sessions and crossings carry an evidence version and observation time. elixir_timeline accepts evidence_item_id with bounded evidence_offset/evidence_limit and expected_evidence_version to read exact ordered canonical game references for a visible it…
Read it ›Weekly participation reads check boat defenses against the requested battles without scanning unrelated history. The Week and You Here keep the same member and former-member counts. MCP 11.0.2; JSON API unchanged.
Read it ›Verified clan leadership can return a declined Action to Open while keeping its decline in the log and preserving sent message parts. New standings updates use short game messages with scores and places, while timestamps and coverage stay in the app. Complete…
Read it ›The Week and You Here can load while a clan decision is being processed. Member-count observations preserve the newest read, and private diagnostics now time direct recorded reads. Contracts unchanged.
Read it ›Clan request diagnostics now include private-state operation counts and timing, plus time waiting for the clan lock. This helps explain slow Actions without recording SQL, state keys or message content. Contracts unchanged.
Read it ›Rookie ranks the season's first joins by the same points and donation tiebreaks as the points podium. Joining in an earlier season without playing war does not extend Rookie eligibility, and a returning stint does not reset the first join. Existing closed awa…
Read it ›The draft worker confirms missing replies and claims inside their own storage paths while retaining failures for genuinely denied objects. Existing replies and one-time claims still prevent duplicate model calls. Contracts unchanged.
Read it ›Awards is now under Clan for every member, with one season selected at a time. Leaders can prepare a current standings update; every message stays together in one Action with its own explicit sent receipt. Weekly updates use only the latest timely close, and …
Read it ›The weekly collector email now carries each collector’s full version and the dashboard’s signed, dev build, unverified or mismatch status. A separate email arrives for each collector Elixir observes upgrade, with the old and new versions and available release…
Read it ›The model worker can now distinguish a reply that has not arrived from denied access, allowing a first draft to reach its one-time request claim. Uncertain attempts remain visible and are never automatically repeated. A counted attempt does not by itself conf…
Read it ›Leaders receive editable, numbered Actions with provisional award standings after a war week is recorded as closed. Updates stop at that completed week, withhold places when evidence is incomplete, and stay separate from final awards. Retried runs fill missin…
Read it ›Clan holds awards when required evidence is unknown, keeps final podiums from saved grants, and resumes interrupted awards without changing the winners. Manual picks require a closed season and a reason, with the saved rule and previous holder in view. Comple…
Read it ›Welcome and removal actions now have editable chat lines with character counts and copy controls. Leaders can ask the clan’s existing model to draft them in its saved recruiting voice, then edit or restore their previous words. Drafting never completes an act…
Read it ›The final cleanup removes empty leaderboard, game-wide statistics, named-group and featured-card tables after their runtime readers have retired. Personal and clan records, notifications, sent mail and agent access remain. Contracts unchanged.
Read it ›The reviewed cleanup removed old global leaderboards, named recording groups and games recorded solely for retired captures from the database and replay archive. Personal, friend and clan overlap was preserved, along with history whose recording provenance wa…
Read it ›The retirement cleanup removes obsolete leaderboard projectors, global population processing, named-group machinery and editorial composers. Your record, clan features, factual event calendar, notifications, sent mail and agent access remain available. Contra…
Read it ›clans_participation checks boat defenses by battle identity instead of scanning unrelated battle history. Current and former member counts, ranked battles, weekly donations, war counters and role history retain the same meaning. No response fields or JSON API…
Read it ›Card history now uses the existing player index and checks boat sides only where needed. Earliest recorded forms, own boat attacks and duel rounds stay the same; boat defenses remain excluded. Contracts unchanged.
Read it ›The reviewed history cleanup distinguishes unchanged re-fetches from new contents. Personal and clan overlap and later recordings stay protected. No game history has been purged. Contracts unchanged.
Read it ›Card reads now start from your selected players' games and look up repeated deck identities once for earliest play. Clan lists retain each played game, duel round, level and form. This fixes excessive reads during the history cleanup. Contracts unchanged.
Read it ›Retired automatic groups no longer generate nightly activity records. Following a player still works when they appeared in an old group. The history cleanup now has checks for personal overlap and late-arriving data; no game history has been purged. Contracts…
Read it ›Clan now uses Elixir’s account, application, storage and deployment. Its old service and storage have retired after all transferred private records matched. Personal and clan history stays protected while the cleanup of retired global captures is prepared. Co…
Read it ›The retired global recording features stay off. Cleanup now gathers historical recording evidence privately so personal, friend and clan history survives overlapping elite-player captures. No game history has been purged.
Read it ›Your Elixir sign-in now opens your record and clan tools in one application. Clan policies, actions, awards, preferences and private records were transferred and checked in full. The separate Clan sign-in and service key are retired; Drop keeps Elixir authent…
Read it ›The old board updater credential has a separate retirement check that preserves the account and its other connections. Live-read documentation now describes only the personal and clan recorder. Global game history still awaits the reviewed purge. Contracts un…
Read it ›Clan’s separate sign-in can now retire after its records are transferred and its shared Elixir runtime is active. The transition checks prevent an in-flight sign-in from issuing a usable grant after retirement. Drop keeps Elixir sign-in and authorized account…
Read it ›Clan consolidation is moving into Elixir’s shared application. The same account will open your personal record and clan tools; your clan’s policies, action history and private records are being preserved for the transfer.
Read it ›Clan consolidation now has a checked import path for its private records and preparation for its morning work inside Elixir. The cutover remains underway; existing policies, action numbers and mail history will be preserved. No recorded history has been remov…
Read it ›Clan's account consolidation now has preservation and permission checks for your existing clan records. The transition is still underway; your current Clan sign-in and app remain available. No clan records or game history have been removed. Contracts unchange…
Read it ›The Clan consolidation is underway. Its management engine and ledger are now shared within Elixir, with preservation checks for policies, actions, awards, preferences and mail history. Clan's current sign-in and stored records still serve the app while the ac…
Read it ›A card's earliest recorded play reads the deck identities already kept with your games, including each recorded duel round and card form. This avoids a timeout seen on a clan-sized history while preserving what the answer means. Contract 11.0.1; JSON API rema…
Read it ›Elixir is a recorder for the players and clans you follow. Global leaderboard tools, game-wide card and deck statistics, recommendations and the editorial model worker have retired. Explore your own games, card inventory and clan activity, receive the notific…
Read it ›Named recording Collections have retired from tracking, Explore, administration, agents and platform integrations. A Collection no longer keeps its members recording. Follow players directly and organize them with primary, alt, friend and watching relationshi…
Read it ›Elixir is focusing on the players and clans you choose to record. Global, regional, clan and mode leaderboards no longer fetch, and leaderboard presence and the former board Collections no longer keep a player recording. The recording cutover preserves remain…
Read it ›About Elixir now starts with what it is for: recording your own play, your friends and your clan, sending notifications, making the record available to agents, and a dashboard where you can explore what happened. Clan and Ladder are features inside Elixir. Th…
Read it ›Overview links the setup steps still waiting for you and offers a first question matched to the history already recorded. A connected client and a successful data read are separate checks; a profile is enough to start, and a clan is optional. The quickstart f…
Read it ›Clan on the bar used to stop at its own Sign in with Elixir button even when you were signed in to the Console. Now Clan sees you are signed in to Elixir and signs you in itself, and a Clan link you opened while signed out, such as an email's link to Actions,…
Read it ›Ladder's Days played could show "Elixir could not read the season's battles" in place of the calendar: it asked for the season in pages of fifty, and fifty battles now run past the size one answer may have. It asks for forty at a time, and when a page is stil…
Read it ›Emails from Elixir, in the account menu and in Account settings, now opens the page with your week of emails and a switch for each, rather than the list of what was sent. That list is one click on, under All sent. No change to the tools.
Read it ›Some of the site printed an escape code where a quotation mark or an apostrophe belonged: the tool reference's descriptions, the On this page list beside a doc, and the description a link preview shows for an update, an example or a family page. The text was …
Read it ›When a milestone email names the battle that took you to a new arena or league, See the battle now opens that battle's own page, the same link an agent gets from battles_query. Its button, and the button on Your week in the Arena, now open your season on Ladd…
Read it ›Profile → Email is now Emails from Elixir. The six weekly emails sit on a week from Monday to Sunday, each on the day it arrives in your own time zone, with what it holds and its switch; the milestone note and Elixir Clan's actions note, which come when somet…
Read it ›battles_query's boat block now has role, the player's own part in a boat battle: attacker or defender. The side it already carried is what the recorded battle log said for its own player, who can be the other side, so a boat attack recorded from the defender'…
Read it ›Elixir's front page is redrawn. It says what Elixir is for a player: every battle, clan week and river race you play, kept and read back on your Ladder, inside your clan, in a short weekly email or to your own AI. Six tiles show what each part does and lead i…
Read it ›In the Console's Explore, a battle in a player's list or a deck's list now opens that battle's own page: both decks, the towers and how it ended, at the same link you can hand anyone. A battle's record in Explore links its page too. A battle recorded before t…
Read it ›Cards has its own page at /cards, linked from the row under the bar. It lists every Clash Royale card and how each is played in the battles Elixir recorded this season, one mode at a time: Path of Legends, Trophy Road, War and the rest each rank the cards on …
Read it ›The menu down the side of the Console is shorter and grouped: Overview, Timeline and Explore, then Your record (Tracking, Collections, Verify), Access (Connections, Usage) and Service (Status), with Send feedback at the foot. The box at the top switches betwe…
Read it ›Ladder has a Cards page, at /ladder/cards: one mode's season card by card, with the same mode tabs as the season home. Your cards show the battles where your deck held each one, your record in them and the share you won; across the table, each card your oppon…
Read it ›Ladder has a Decks page, at /ladder/decks: every deck you played this season, each judged in the mode it was played in. Trophy Road and Path of Legends show each deck with its eight cards, its evolutions, the days you played it, its average elixir, and its re…
Read it ›Ladder has a second page, Days played, at /ladder/days: every day of the season on your calendar in your own timezone, each mode with its own mark and record, the two modes you played most as tiles, the longest break, and your nights (runs of battles with no …
Read it ›A battle's page is public and reads the same signed out, so the bar at the top no longer marks the Console as the place you are in there: Console, Ladder and Clan are plain links, and on a phone the bar's button says Menu. The Console's sign-in card now says …
Read it ›Elixir's emails now draw cards the way the game does. Your week in the Arena and Your friends this week show each deck as its eight cards in a row, with the tower troop named under it; a milestone for a card you unlocked shows the card, and opens its page; a …
Read it ›You here, your own page in a clan on Elixir Clan, has the new design. Any actions waiting for you sit in a link at the top. This week so far is a row of tiles: war decks out of those asked, ranked battles, donations, battles and trophies, each marked when the…
Read it ›Actions in Elixir Clan have the new design. What is waiting for you and what closed in the last 30 days sit in two panels, each action marked by its kind with its number, who it is about and its comments. An action's own page opens with what it asks and who i…
Read it ›Standing in Elixir Clan has the new design. How it works here now opens with what Elder weighs in your clan, drawn as bars from the policy, and your own line sits under it with your war decks race by race. Where the clan shares it, each group has its own pane…
Read it ›A clan's page in Elixir Clan has the new design. It opens with what the game says the clan asks of a joiner and the clan's own figures as tiles: members by role, clan war trophies with the latest race result, and donations a week. The roster sits in a panel y…
Read it ›Every battle page has a picture: add .png to the battle's link. It is the page in one image, with the player's name on the left and the opponent's on the right, both decks as the game lays them out with each card's level, average elixir and elixir leaked, the…
Read it ›cards_card reads earliest selected-history play from shared deck identities instead of joining every played-card occurrence. Base, Evolution, Hero and duel-round history retain the same factual meaning. No response fields or JSON API operations change.
Read it ›Elixir records the histories you ask it to keep: your games, friends and clans. Global leaderboard tools, game-wide meta statistics, synergy and gameplay/upgrade recommendations have retired. Card catalog facts and art, owned inventory, personal profile ranks…
Read it ›Named recording Collections have retired. Elixir records players and clans followed directly by accounts. Primary, alt, friend and watching relationships, owned card collections, notifications and personal OAuth tracking remain. Drop no longer automatically e…
Read it ›Elixir stops autonomous leaderboard capture and elite-player enrollment. Personal profile ranks and requested player/clan recordings remain. Ultimate Champions and Card of the Week have ended; sent-email history remains available. Existing global history awai…
Read it ›Corpus trends select covered player/time keys before fetching battle identifiers and trophies, retaining distinct games at the same timestamp. Season card partners read anchor-bearing cached participants and duel parents once, then expand rounds; recent and o…
Read it ›Season card partners narrow deck identities to decks containing the requested card and bound uncached observations by the recording cursor before expanding duel rounds. Card profiles filter their season deck rows in the database. Corpus weekly trends bound pa…
Read it ›Historical clan presence is bounded by membership in the requested window. A later departure or a future join no longer changes the closed window's quiet crossings, returns or never-recorded count. Quiet and never-recorded summary values read membership at th…
Read it ›A boat battle's boat carries role: this row's player's part, attacker or defender. side is the API's boatBattleSide as the log that recorded the battle said it, for that log's own player, so on a row for the other player it named their opponent's part. A swee…
Read it ›A battle's url with .png on the end is its picture: the battle page drawn as one 1200 by 630 image, with both names, both decks, the elixir numbers, the towers and the link. The page's link unfurls with it. url's description says so; no field changed.
Read it ›The bar at the top of every Elixir page is new. The logo takes you home; Console, Ladder and Clan sit on the left, and the one you are in is green; Docs and a Play Drop button, which opens the elixir-cost game in a new window, sit on the right. At the end is …
Read it ›Ladder opens at /ladder, beside the console and signed in like it: the current season of one of your players, as Elixir recorded it, one mode at a time. Trophy Road, Path of Legends, war and events each have their own tab and nothing pools across them. The se…
Read it ›Each recorded battle now has its own page at elixir.poapkings.com/battle/ followed by a short id, and anyone with the link can open it, no account needed. The player is on the left and the opponent on the right, with the score, both decks as the game lays the…
Read it ›Six new pages in the docs' Clan group: bringing your clan (signing in, your role, the ten-member threshold), the weekly report, standing and the Elder band, actions and the inactivity clock, awards and trophies, and writing the clan's policy with the leaders'…
Read it ›Every email Elixir sends now wears the same frame: Elixir's logo and name at the top, a label saying which part of Elixir it comes from and when (Clan on Monday, Friends on Wednesday), and a footer that says why you got it and when the next one comes, in your…
Read it ›The week in Elixir Clan has the new design. The top says where you are, and the week's numbers sit in a row of tiles: how many members took part in the war, how many played some of their decks and how many played every deck asked. The war lists everyone in tw…
Read it ›Eight new pages in the docs, each about one thing you came to do: your account (signing in, your players, your time zone, removal), following a friend and watching any player, milestone emails, turning an email off, why modes are kept apart, signing in to Eli…
Read it ›The docs are reorganized around what you came to do: getting started, your friends and the emails, your own AI agent, what every number in the record means, building on Elixir, and the policies. The docs home starts from those tasks, the rail on the left is t…
Read it ›Every battles_query row carries url, the battle's public page at https://elixir.poapkings.com/battle/<short id>: both decks, the towers and how it ended, readable without signing in. It is the link to hand a person for one battle. The short id is the first 12…
Read it ›