The Fatigue Strategy
An original game theory strategy for the WhatIfSports baseball simulation: exploiting an undocumented mechanical gap in how the engine handled appearance thresholds, replicated widely enough across the community that it forced the platform to change its own game engine and ruleset.
The discovery
WhatIfSports is a baseball simulation platform where users build historical rosters and simulate full seasons. I developed the fatigue strategy in the late 2000s: deliberately drafting high-quality, low-IP/PA player seasons that fell below the threshold needed to cover a full 162-game schedule, then using league-minimum replacement players to absorb low-priority games — primarily interleague matchups, where the platform’s competitive stakes were lowest — while preserving rested, high-quality players for the games that actually mattered: critical intra-division matchups and the playoff push.
The strategy exploited a real mechanical gap in the simulation engine: pitcher and position-player fatigue accumulated based on usage relative to a player’s real-life workload, but the platform had no mechanism preventing a manager from strategically resting elite, low-IP players during low-stakes games specifically to keep them fresh for high-stakes ones. A team could field a meaningfully weaker roster in games that mattered less, banking the rest for games that mattered more — producing a net competitive advantage no rules document anticipated.
Why it worked
The core insight was that not all 162 games in a WIS season carry equal competitive weight. Interleague games, in particular, have no bearing on division standings. A team willing to accept worse outcomes in those specific games, in exchange for fresher elite talent during division and playoff games, could systematically outperform a team that distributed playing time evenly across the full schedule — even with an identical total roster of talent.
Spread and platform response
The strategy proved effective enough that it was widely replicated across the competitive WIS community within a relatively short window. That replication is what forced WhatIfSports to respond directly. The platform implemented several rule and engine changes specifically in response: IP/PA minimum thresholds for rostered players, roster management restrictions limiting how aggressively a team could bench elite low-IP players, a 10% team salary cap limit applied specifically to AAA rosters (closing a related loophole the strategy had also exposed), and modifications to the underlying fatigue mechanics in open leagues.
This is one of the few documented cases of a user-developed strategy directly causing a major simulation platform to alter its own game engine and ruleset in response — not a balance patch reacting to general feedback, but a structural fix targeting one specific, identifiable strategy.
Attribution
The original strategy post was lost in a later site migration, but the attribution has been preserved within the community. Other long-tenured WIS users continue to credit me as the strategy’s originator when the topic comes up in league discussions — a level of attribution that persisted decades after the original post itself was gone, which says something about how distinctive and consequential the strategy actually was within the platform’s competitive history.
Philosophical Application
This strategy begged the question as it became popular, “Is it cheating?” There were some who felt so because it flies in the face of accepted normal roster creation and management. It also ignored the otherwise implied constraints on roster construction with player and salary requirements. The argument against it being cheating was twofold: 1. The strategy operated within the full scope of the rules and what is permitted, there was no changing source codes, or using URL tricks to draft a team one otherwise couldn’t. Anyone could draft such a team. 2. This strategy is the same categorically as resting a player once a team has clinched a playoff spot or to make sure the player is fresh for a key matchup, just taken to its extreme; resting all key players in all key matchups, to ensure the team makes the playoffs. Which brought up a key philosophical point of why people play games. Some were playing to win a game and use all the resources available to them to do so, and others were playing to simulate managing a baseball team with as life-like an application of what that looks like as possible. When these two players meet, it creates tension as their goals are at odds with each other. One is playing a computer game, the other is reliving a baseball game, and those mean very different things to those players.