Sizing configs

A full solution offers four or five bet sizes at every decision. Nobody plays that way, and the doctrine megamaster's rules are built on says you shouldn't try: one size on the flop, usually one on the turn, block plus pot on the river captures nearly all the EV. A sizing config is where you write that down — which simplified menu you practice at each decision — and the library tells you what it costs.

General defaults and Spot rules

Train › Play › Sizing menus (marked beta). General sets the starting menu per scope: pot type (SRP or 3-bet), position (IP or OOP), role (aggressor or caller), and the decision slot — flop, turn after a bet, turn after a check-through, river after a bet, river after a check-through. Broad rows ("Everything") apply wherever a more specific row doesn't. "After a bet" means the previous street contained a bet or raise — a fact about the line, not a judgment; the flop has no previous street.

Spots are the exceptions: an ordered list of rules keyed to your texture buckets, checked top to bottom, first match wins. "Monotone flops keep all sizes; paired flops use B70; everything else uses the General default." A rule whose menu equals the default it shadows is tagged keeps default — it stops later rules without changing the answer, which is sometimes exactly what you want and sometimes a mistake, so the editor points it out. Test a spot at the bottom tells you which rule fires for any flop, decision and scope.

Built-in configs are read-only; Customize makes an editable copy. "Doctrine starter" is the doctrine as a starting point (B30 flop, B70 after a bet on the turn, B70 + overbet after a bet on the river) — which single size is right is a per-board question, and that is what the next section answers.

Size rules: one size by board texture

General and Spots choose a whole menu. A size rule decides one size at a time from the board's texture: "B30 only on monotone or paired flops", "B70 never on low monotone flops". Each rule row has a street, a scope (pot type, position, role), a size, only on or never on, and a condition picked as chips. The row reads back in words what it does.

• Only on — the size is offered on boards that match, even where General or Spots leave it out, and hidden on every other board in the rule's scope.
• Never on — the size is hidden on boards that match; elsewhere General and Spots decide.

The condition. Three rows of chips. Flop: Monotone, Two-tone, Rainbow, Paired, Paired high/mid/low, plus your own saved texture buckets. Height: Triple, Double and Single Broadway, Low. The card (turn and river rules only): what the card that opened this street did — pairing, flush-completing, flushdraw-bringing, straight-completing, overcard, undercard, blank. Chips in one row are alternatives (monotone or paired); rows must all hold (monotone or paired, and low). These are the same textures as the bucket presets and the drills' texture filter. There is no new taxonomy; for a combination the chips can't spell, save a texture bucket and pick it as a chip.

Flop or current board. The flop chips read the flop and keep applying on the turn and river: the flop's texture is the board's texture for this purpose. The card row is the one reading of the current board. It looks at the turn card on the turn and the river card on the river, by the runout classes (first match wins, so a card that pairs the board and completes a flush reads "pairing"). A rule with a card condition has no effect on the flop.

Precedence. Size rules run last, over whatever menu General or Spots chose, so for its size a texture rule always beats a formation-only rule. When two size rules name the same size, the first one in the list that has a say on the board wins, the same top-to-bottom reading as Spots.

Example. General: flop B70. Size rule: Flop · Everything · B30 · only on · Monotone, Paired, which reads "B30: only on monotone or paired flops". On A♥K♥2♥ and on 9♠9♦4♣ you get B30 + B70. On K♠7♦2♣ you get B70 alone. With no General rule (all sizes), the rainbow board shows "All sizes except B30". Sizes are the app's buckets: a 25% bet is B30 (anything from 20% to 40% of the pot). Only the sizes the solver's tree actually has are ever offered, and nothing is interpolated.

Grading is unchanged: the full solve renormalized over the sizes offered on that board. A size hidden on a rainbow flop has its frequency spread over what was offered there. Size rules ride along in Export and Import (Export also has a Size rules only part). A config with size rules needs Megamaster 0.4.67 or newer to import. Older versions refuse it with a message naming that version rather than quietly dropping the rules.

EV loss by sizing

Solve › Library, under a spot's rules: the priced cost of each simplified menu against the full menu, as a percentage of the pot, over your saved texture buckets. Each number is a real re-solve — the library rebuilds the tree with fewer flop sizes and solves it to the same accuracy, both players re-equilibrated — not a solution with buttons hidden. Bands follow the doctrine: under 0.5% of pot is fine for almost everyone, 0.5–1% is borderline, above 1% is unacceptable, and a cost inside the solves' own noise reads "≈ free (within noise)". A "+" marks an option whose solve was killed early once its cost was provably above the kill threshold: the number is a lower bound. Drag across cells to average them; "Individual boards" shows one board per row instead of board groups, and costs can read in % of pot or bb.

A config's page also prices the config itself on any solved spot (Price it): its resolved flop menu per board joined to that board's priced options — mean cost, worst board, and how many boards are unpriced. Unpriced is counted, never assumed free. Only the flop menu is priced; the library does not price turn and river menus yet.

Using a config in training

Pick a Sizing menu when you create a drill or start free play. Your bet buttons are restricted to the menu (check, call and fold always stay; a menu with no matching size in the tree keeps the nearest one rather than silently turning the spot check-only), and every decision shows the menu in force and — when the library has priced this exact simplification on this board — what it costs.

How it is graded, honestly. The full solution is the reference, renormalized over the sizes you were allowed: "buttons hidden". That is not the same as a strategy solved for the restricted menu, and the trainer labels it so on every decision rather than pretending otherwise. Solving restricted trees per config is library work; the priced cost shown beside each decision is what that would change.

Nothing is ever applied by default. A drill or session names a config; no other surface reads one.