The interactive dives and Community Day articles on this site use a handful of terms you won’t find on PvPoke or GamePress: “envelope position,” “threshold tier,” “flavor,” “slayer category.” They aren’t new game concepts - they’re the vocabulary we built to talk about which IV to chase in a way that stays honest across shield scenarios, opponent IV choices, and bait policies.
These guides explain each term with a worked example from a real dive. When the underlying methodology changes, every example regenerates on the next publish so the numbers and named cases stay current.
How these dives get built: PvPoke's simulator, reimplemented in Python, swept across every IV, then rendered with Plotly. The short version of what you can and can't trust.
Tier vs category vs anchor. What the stat-cutoff bullets mean and why overlapping tiers are intentional.
What 'rider' and 'band-crosser' shapes mean for a category, why mean_delta matters when you're picking an IV to chase.
What the purple IV Flavor Guide zone does, how to read a flavor, what a namesake is, why two flavors with the same stat signature merge.
Color modes, hover cards, the Shields / Opponent IVs / Bait dropdowns, and what the anchor-clear overlay shows.
How we test whether a matchup outcome survives the IVs - outcome planes, cohorts and probe spreads, W/L/? grids, robustness curves, and closed-form reach/deny cutoffs.
The Dive Analysis section that groups IVs by which marginal matchups they win, with the three stat-plane panels and the flip-threshold table.
How to read the matchup-delta table, what the PvPoke multi-battle link does when you click it, what 'flip' means here.
How the dives auto-generate: the anchor / category / tier / flavor pipeline, why certain narrative blocks are gold vs blue vs orange, and where to push back when the output gets something wrong.
Battle engine is a Python port of PvPoke; all game data from PvPoke by Empoleon_Dynamite (MIT license). This project would not exist without it.
Part of the PvP dive site. Explainers regenerate from current dive data every publish, so numbers stay in sync with the methodology. Last regenerated 2026-08-27.