Tinkaton vs Lickilicky: how much do IVs actually matter?

Human-guided, AI-generated (Claude). Methodology, honesty notes and disclosures.

4,096 x 4,096 IV spreads x 9 shield scenarios x 2 distinct moveset/bait grids = 301,989,888 simulated matchups (69,969,420 deduplicated engine calls -- IV-identical cells share one sim).

Controls

Your IVs: which one should you build?

Runs entirely in your browser; nothing is uploaded. Paste your Poke Genie CSV (or pick the file) and your mons are ranked below. Only Lickilicky, Lickitung, Tinkatink, Tinkaton, Tinkatuff rows are read.

The short version

Every matchup at once: 4096 Tinkaton x 4096 Lickilicky

Hover a cell to outline it across the view. At the default zoom a cell covers a BAND of ranks, not one spread -- the caption under the plot states the current band size, which narrows to a single spread as you zoom in.

Coverage vs attack: is there a cliff?

Off the frontier: attack vs stat-product rank

Coverage: which Tinkaton spreads beat the most Lickilicky

Pareto: Lickilicky coverage vs the rest of the meta

Drill-down: one Lickilicky spread at a time

Mechanism: breakpoints, bulk, and the community claims

Recommendations

The other side: anti-Tinkaton Lickilicky tech

Methodology, honesty notes and disclosures

generated 2026-08-24 19:05 UTC | engine 5839391a7596 | gamemaster 8f1d6cca5c0f | mechanics legacy | 69,969,420 deduplicated engine calls covering 301,989,888 matchup cells | grids embedded: bulgh_bait, bulgh_nobait

All declared inputs are present in this build.