VYASA
PostsDemoPokemonREADMELoop

The Game Theory of Competitive Pokémon

←→

The Iterative LoopURL copied

Team building and battling form a feedback loop that never fully closes.

stateDiagram-v2
    [*]          --> Hypothesis : Have an idea
    Hypothesis   --> Build      : Finalize 6 Pokémon
    Build        --> Ladder     : Test on ranked
    Ladder       --> Win        : Strong matchup
    Ladder       --> Loss       : Weak matchup
    Win          --> Analyze    : What worked and why?
    Loss         --> Analyze    : What failed and why?
    Analyze      --> Hypothesis : Revise theory
    Analyze      --> Build      : Adjust team
    Build        --> Tournament : Submit team
    Tournament   --> [*]        : Outcome recorded
The attribution problem

If you win 10 ladder games, how much is your skill and how much is your team? If you lose, was the team wrong, or were you outplayed?

Feedback in this loop is noisy, opponent-dependent, and influenced by luck. Systematic improvement is structurally difficult in a way that most games don't have to contend with.

What makes this worse: practice games are usually against known opponents. Tournament opponents make decisions in entirely different ways. And if you happen to freeze several opponents in a row with Blizzard in testing, your six Ice-type team looks like a genius idea - right up until the tournament, where you play against Fire and Rock teams and your Pokémon are stationary boulders.