PulseGTO

Solver engines

Preflop engine

The preflop engine (PulseGTO_preflop.exe) trains blueprints. A blueprint is a whole No-Limit Hold'em game for 2–6 players, solved in one run from the first preflop decision through the river. Preflop ranges and postflop play are trained together on the same tree, so each preflop decision is valued by the postflop strategy it leads to.

What it computes

The engine trains preflop and postflop decisions together for the configured game. Postflop play uses the selected abstraction level to keep the whole-game calculation practical on a desktop. Higher levels need more memory and give more detailed postflop strategies. See Hand abstraction.

Configuration and limits

  • 2–6 players, any stacks, raise sizes per seat, limping from the SB only, and rake with a cap and a minimum pot.
  • Strength: small, medium or high (the default).
  • Memory: the run saves a checkpoint and stops at 85% of physical RAM.

Its accuracy number measures convergence inside the abstraction; Accuracy & limitations explains what that covers.

Technical notes

The .pgb contains a compact strategy and recorded EVs; a checkpoint is needed to resume training. See Exploitability metrics.

Overview page: Preflop solver for your own game tree.

A three-max game and a three-way flop are different

For a three-max preflop blueprint, enable the three seats representing your game and set their stacks and action menus. The blueprint trains decisions from the blinds onward, including which hands open, call, re-raise or fold. A three-way postflop solve instead starts with three ranges already reaching one board and one pot.

In six-max, a first-in open and the same hand facing an open are different decisions. Match the seat strip, action history and averaged/current setting before comparing a chart. Record call limits, squeeze and jam-call options as well as open sizes: these downstream possibilities can change an opening range.

The payoffs are chip EV with configurable rake. Three-player support does not imply tournament ICM or payout-aware ranges. For a selected postflop board, use the ranges reaching that node in RangeCFR instead of treating the first-in range as its river range.