Evidence and updates
Source pins, refresh triggers, audit commands, and the claims that need relabeling when the tier moves.
| Claim | Primary source | Current pin |
|---|---|---|
| named-format rules and banlist | local Pokémon Showdown config/formats.ts | guide source hash |
| species tiers and Manectric RUBL status | local Gen 3 formats-data.ts | guide source hash |
| Manectric vote | ADV RU council post | June 3, 2026 |
| published rank bands | ADV RU VR update | December 22, 2025 |
| public samples | sample update and Poképastes | January 8, 2026 |
| pre-ban high-level usage | ADVPL VI cumulative table | May 24, 2026 |
| post-source observations with no revealed current conflict | public replay protocol | July 4–26, 2026 |
| post-ban building recommendations | dated samples, July replay ledger, and matchup analysis in this guide | July 26, 2026 |
| exact stats and damage | validator plus repository calculator | per receipt |
The research memo behind this revision lives at docs/research/adv-ru-metagame-2026-07-26.md.
Rebuild the evidence
From the repository root:
node tier-guides/adv-ru-guide/tools/snapshot-format.mjs
node tier-guides/adv-ru-guide/tools/snapshot-benchmarks.mjs
node tier-guides/adv-ru-guide/tools/snapshot-replays.mjs
node tier-guides/adv-ru-guide/tools/audit-guide.mjs
Then check the site:
cd tier-guides/adv-ru-guide/site
npm ci
npm run check
npm run build
The snapshot scripts pin source hashes and explicit replay IDs. A changed source should stop the refresh until the difference is read and the guide claims are audited.
Update triggers
Run a new revision after any of these events:
- an ADV RU council vote or tier shift;
- a new community viability ranking;
- a new sample-team slate;
- a change to the
gen3rurules or Gen 3 tier data; - enough ADV RU Cup games to support a separate tournament table;
- a public set resource that changes a benchmark used here;
- repeated post-ban tournament evidence that confirms or rejects these recommendations.
Do not pool battles across a ban. Keep the Manectric ADVPL table as its own historical stratum and start a separate exact-format ledger after the source-change boundary. Label hidden legality unproven unless a complete validated paste is public.
Labels that must move with the source
If the council publishes a new VR, replace the carried-forward December table and move Hypno out of New only if the source does.
If the sample slate changes, revalidate every full paste and update the lead order, sample denominator, species appearances, and team-page copy together.
If source tier data changes, regenerate the entire legal manifest. Editing one banned-species label by hand can leave roster pages, counts, and filters in disagreement.
If a replay reveals only four Pokémon, keep the remaining two unknown. More games do not make hidden information public.
The ADV RU Cup was scheduled to open on July 27, one day after this guide’s cutoff. Its first completed round is the next useful evidence checkpoint.