Draw density decides the call
A button opening range picks up a straight draw on J-T-4 about three and a half times as often as it does on Q-7-3. That gap is what sets how wide you keep calling against a c-bet. These queries count the draws on both flops, then check the mental arithmetic the strategy material uses to estimate them.
6 runnable queries. The stated numbers are what we measured, not a promise. Monte-Carlo runs wobble, and the solver-referenced ranges move when we re-solve. Run the cells for today's figures.
The strategy material puts your continue against a c-bet near three quarters of a button range on J-T-4, and well under half on Q-7-3. PQL cannot check a solver frequency, but it can count what produces one: how many combinations of your range just picked up a draw. Every cell below uses the 6-max button opening range from this site's solves (`#6m/rfi/btn`), frequency-weighted.
1. Made hands on J-T-4 rainbow
select count(exactFlopHandCategory(hero, set)) as sets,
count(exactFlopHandCategory(hero, twopair)) as two_pair,
count(exactFlopHandCategory(hero, overpair)) as overpairs,
count(exactFlopHandCategory(hero, toppair)) as top_pair
from game='omahahi',
hero='#6m/rfi/btn',
villain='****',
board='JsTd4h'These categories are board-relative. A set is a pocket pair matching a board rank, an overpair is a pocket pair above every board card.
Sets around 6%, two pair 10%, overpairs 17%, top pair 10%. The material quotes about 5% sets and 11% two pair for a raising range on this flop, so the counts land where it says they should.
Run in the PQL engine →2. Straight draws: J-T-4 against Q-7-3
select count(hasStraightDraw(hero, flop)) as any_straight_draw,
count(hasOpenEnder(hero, flop)) as open_enders
from game='omahahi',
hero='#6m/rfi/btn',
villain='****',
board='JsTd4h'Run it, then change the board to Qs7d3h and run it again. Same range, same functions, different flop.
J-T-4 gives about 56% any straight draw with 23% open-enders. Qs7d3h gives about 16% and 1%. The material counts roughly 45% against 20% for the defending side, a narrower gap on a different range, pointing the same way.
Run in the PQL engine →3. Add the flush dimension: two-tone J-T-4
select count(hasFlushDraw(hero, flop)) as flush_draws
from game='omahahi',
hero='#6m/rfi/btn',
villain='****',
board='JsTs4h'The same board with two spades instead of a rainbow.
About 23%, against the material's 22% for a raising range on a two-tone flop. Its rule of thumb is that any range gets dealt a flush draw about 20% of the time on two-tone boards, and that holds up here.
Run in the PQL engine →Those straight-draw counts come out of one number worth memorizing. Any specific two-card combination you were dealt turns up about 7 to 7.5% of the time, so on a flop like 9-8-7 you add roughly 7% for each straight-completing combo (J-T, T-6, 6-5) and land near 20%. The next two cells check both halves of that.
4. One specific two-card combo, about 7%
select count(inRange(hero, 'JT')) from game='omahahi', hero='****', villain='****', board='9s8d7h'inRange(hero, 'JT') asks whether the four dealt cards contain a jack and a ten.
About 7%.
Run in the PQL engine →5. All three straight combos together, about 19%
select count(inRange(hero, 'JT,T6,65')) from game='omahahi', hero='****', villain='****', board='9s8d7h'About 19%. The union comes in a little under 3 x 7% because some hands hold two of the combos at once, and that overlap is what the add-7-percent shortcut quietly absorbs.
Run in the PQL engine →6. The same idea in Hold'em: K-7-2 rainbow has no draws at all
select count(hasStraightDraw(hero, flop) or hasFlushDraw(hero, flop)) as any_draw
from game='holdem',
hero='15%',
villain='**',
board='Kh7d2c''15%' is the top 15% of Hold'em hands by all-in equity. Change the board to Th9h4c and run it again.
Exactly 0% on K-7-2 rainbow, about 23% on T-9-4 two-tone. Not one gutshot, open-ender or flush draw is possible on the first flop, so a continuing standard built for wet boards will have you folding far too much on the dry ones.
Run in the PQL engine →Draw density belongs to the range and the board together. Neither one alone tells you anything, and it swings by a factor of three and a half between flops that look similar at a glance. The 7%-per-combo shortcut survives contact with the engine: the single-combo figure and the summed one both come out where the arithmetic says they should. So when your range is mostly draws, folding bottom pair because it is only bottom pair throws away the equity the texture just gave you. The material works that exact hand, bottom pair with a gutshot, and it folds on the dry flop and continues on the wet one.
PQL computes entirely in your browser, no install or account. New to it? See the PQL syntax reference, open the PQL engine, or browse all recipes.