Team builder

Four slots, all 225 forms, and an honest read on what the party covers. Everything stays in your browser, and a whole team fits in a link.

The team builder needs JavaScript. The Aniimo-Dex and thetype chart both work without it.

How this reads a team

Four slots

The control scheme binds 1–4 to swapping party members, and community team guides assume four. No official source states the party size outright, so treat four as well-evidenced rather than confirmed — it is the one number here we would most like the game to correct.

Coverage counts skills, not just typing

121 of the 225 forms carry at least one skill in an element they are not. Eklue is a Wind creature with an Ice arc strike and a Water arc strike. A builder that reads only the element chips would tell you a team has an Ice hole when it does not, so the coverage table counts every element a form can actually deal damage in and marks which ones come from its own typing rather than from a skill on the bar.

Two elements are never multiplied together

87 forms carry two elements, and no source states how a pair combines when defending. A member favourable against one of its elements and not the other is reported as partly exposed, with both multipliers intact. Inventing a rule would make the numbers look tidier and be wrong.

BREAK is treated as a pillar, not a footnote

Breaking an enemy's grey gauge staggers it, opens the burst window and improves capture odds — it is the mechanic tying combat to collection. So BREAK is a first-class column in the party table and a role the summary checks for, rather than one stat among six.

Nothing here is scored

There is no tier list, no letter grade and no "best team". The effectiveness chart is not officially published — 2 community databases agree on all 81 cells and 1 publishes a different one — the game is unreleased, and no source states how party composition is rewarded. Reporting coverage and exposure is defensible; ranking a team on unverified data is not.

Two ways to share, and the first needs no account

The share link carries the whole team in the part of the URL after the#, which browsers never send to a server. Nothing is stored, nothing is uploaded, and anyone who opens it gets an editable copy of their own. That is the default, and the only option signed out.

Publishing is the other one. It puts the team on a permanent page at/b/…, which is what buys a preview when the link is pasted into Discord and a page a search engine can find. It needs an account so that you can take it down again, and it publishes only the team, its notes and the credit you choose — never your email or your collection. See what people have shared on Published teams.

What goes on that page is a snapshot. Signing in also keeps your teams in step across devices, and neither editing nor syncing changes a published page — it stays on the version you published until you update it. A team you are still tinkering with does not go public a change at a time.