Preflop Charts and GTO Solvers

A lookup does not solve your spot

BluffKing’s preflop ranges once used the name gto_chart. The current method field is cfr_equity_realization, and the interface says “preflop baseline range.” Requests read pregenerated data rather than solving the entered spot again.

How the preflop data is generated

A discounted-regret CFR variant runs over a simplified six-player, 100bb preflop tree, using all-in equity and an equity-realization model at terminals. Range data contains mixed continue frequencies. Its provenance label is “CFR approx. equilibrium · equity-realization,” not an optimal strategy for full Hold’em.

Inputs include fixed bet sizes, opponent reaction frequencies and equity-realization factors, plus rules including premiums and excluding weak hands. Each equity-matrix cell uses 8,000 Monte Carlo trials and representative suit combinations. Changing the model can change the ranges; generation parameters are recorded in engine/data/preflop_v2.json under _source.

Ordinary postflop advice is different from a solve

The ordinary spot analyzer uses equity_heuristic postflop: equity and rule-based advice rather than CFR. A separate postflop solver runs Discounted-CFR for specified player ranges and bet sizes, returning cfr_equilibrium, iterations and measured exploitability.

It retains card combinations within the specified tree, but betting options remain limited by the inputs, and finite iterations do not guarantee exact equilibrium. The interface therefore says “Postflop CFR approximation.” Results apply only to the specified ranges, sizes and precision. The endpoint also needs server enablement and a source-offer configuration; code availability does not establish availability on every deployment.

What to inspect in an analysis result

• Method: pregenerated baseline, equity heuristic or a CFR solve of the current spot?
• Model: which ranges, stack depth and bet sizes were used?
• Error: what sampling budget, iteration cap and measured exploitability are reported?

Implementation entry points are engine/src/solver/, server/src/handlers/solver.rs and gto-solver/src/lib.rs. Analysis helps review decisions; it cannot guarantee wins.