Pitcher / Hitter Randomness
Randomness is the optimizer's diversity dial: each lineup is solved against projections with a controlled amount of noise added, so 100 lineups explore the slate instead of repeating one optimal answer.
The global slider
In Advanced Options → GENERAL, the Randomness slider runs 0–100%.
- 0% — pure optimization; only the uniques constraint separates lineups.
- Higher values — proportionally larger noise, more varied lineups, lower average projected total.
At 0% the setting is a no-op: builds are deterministic.
MLB pitcher / hitter overrides
Below the slider, MLB adds two optional overrides. Check Pitcher or Hitter and set its own percentage — that position class then uses the override instead of the global value. Unchecked = inherit the global slider.
This decouples the two roles: e.g. keep pitchers near-deterministic while hitters vary, or the reverse.
How it interacts with everything else
Noise is applied to whichever projection source is active (system or user, after Adj boosts). Locks, exposure bounds, stacks, and groups all still bind — randomness only varies the objective, never the rules.
Uniques and randomness solve different problems. Uniques force a minimum difference between lineups; randomness varies which players the solver prefers. Large builds typically use both.