Say something when the raise isn't a legal raise #56

2026-09-01T09:12:46-06:00

jheaps commented

2026-09-01 09:12:46 -06:00

Web search turned up the oversized-chip rule described as the single most common cause of floor disputes, and specifically a home-game problem. Chasing it led to checking what the bar does with an illegal raise — and the answer was nothing. Stacked on #55.

With the minimum at $18 and a player holding $200, typing 13 was accepted without a word. The engine then treated it as a short raise and correctly declined to reopen the betting — right for an all-in, wrong for someone who just misheard the bet, and either way the dealer was never told.

It says what's wrong and still lets it through

This tool records what the humans at the table actually did, and a dealer overruling the arithmetic is right more often than the arithmetic is. Confirm stays enabled in every case:

Typed	Note
$13 (min $18, deep stack)	$13 is under the $18 minimum. A legal raise is $18 or more — otherwise it's a call, or all-in.
$13 (min $18, 13 behind)	All-in for less than a full raise. Legal, but it doesn't reopen the betting — anyone who has already acted owes the difference or folds.
$500 (200 behind)	More than they have. This goes in as all-in for $200.
$10 (bet is $10)	$10 is not above the $10 already bet — that's a call, not a raise.

The second surfaces the rule fixed in #51 at the moment it decides something, rather than only in the rulings sheet.

Two minimums, which is where my first attempt went wrong

The pad already had a minimum — clamped to what the player can actually put in. Correct for the Min button, wrong for the warnings: for a short stack the clamped minimum equals their all-in, so neither warning could ever fire for exactly the player the rule exists for. They're separate now.

A regression the audit caught in the same round that introduced it

The note makes the pad taller → --actionBarHeight grows → the toast, which floats just above the bar since #45, gets pushed up over the table. Measured at 360x640:

bar  122px closed  →  178px with pad  →  217px with note
toast  y506        →  y450            →  y411  (covering seats outright)

A toast is transient news about the action just taken; the pad is the dealer deciding the next one. The older one gets out of the way when the pad opens — nothing lost, since its Undo is also the bar's own undo control. The note is tighter on short screens and the pot breakdown hides during entry (which side pots exist isn't what's being read while typing an amount). Net 210px, and no seat covered that the pad wasn't already covering at 178px.

Two rulings entries from the same search

The oversized chip — a single big chip pushed out silently is a call, not a raise, however big it is; to raise you say so before it lands. And what a full raise is, which the pad now enforces in words.

Validation

137 tests passing. Raise warnings verified across four amounts on a deep stack and three on a short one, at eight viewports: note shows, pad stays reachable, contrast clean, Confirm never disabled. Toast confirmed still normal when the pad is closed. No console errors.

One note on process: two of my checks this round tripped the unresolved-pot confirm from #49 and looked like failures until I re-seeded — my test's fault, not the code's.

Web search turned up the [oversized-chip rule](https://www.cardplayer.com/cardplayer-poker-magazines/66547-bestbet-37-17/articles/25147-contracts-and-poker-the-oversized-chip-rule) described as **the single most common cause of floor disputes**, and specifically a home-game problem. Chasing it led to checking what the bar does with an illegal raise — and the answer was **nothing**. Stacked on #55. With the minimum at $18 and a player holding $200, typing **13** was accepted without a word. The engine then treated it as a short raise and correctly declined to reopen the betting — right for an all-in, wrong for someone who just misheard the bet, and either way the dealer was never told. ## It says what's wrong and still lets it through This tool records what the humans at the table actually did, and a dealer overruling the arithmetic is right more often than the arithmetic is. **Confirm stays enabled in every case:** | Typed | Note | | --- | --- | | $13 (min $18, deep stack) | *$13 is under the $18 minimum. A legal raise is $18 or more — otherwise it's a call, or all-in.* | | $13 (min $18, 13 behind) | *All-in for less than a full raise. Legal, but it doesn't reopen the betting — anyone who has already acted owes the difference or folds.* | | $500 (200 behind) | *More than they have. This goes in as all-in for $200.* | | $10 (bet is $10) | *$10 is not above the $10 already bet — that's a call, not a raise.* | The second surfaces the rule fixed in #51 **at the moment it decides something**, rather than only in the rulings sheet. ## Two minimums, which is where my first attempt went wrong The pad already had a minimum — clamped to what the player can actually put in. Correct for the Min button, wrong for the warnings: for a short stack the clamped minimum *equals their all-in*, so neither warning could ever fire for exactly the player the rule exists for. They're separate now. ## A regression the audit caught in the same round that introduced it The note makes the pad taller → `--actionBarHeight` grows → the toast, which floats just above the bar since #45, gets pushed **up over the table**. Measured at 360x640: ``` bar 122px closed → 178px with pad → 217px with note toast y506 → y450 → y411 (covering seats outright) ``` A toast is transient news about the action just taken; the pad is the dealer deciding the next one. The older one gets out of the way when the pad opens — nothing lost, since its Undo is also the bar's own undo control. The note is tighter on short screens and the pot breakdown hides during entry (which side pots exist isn't what's being read while typing an amount). Net **210px**, and no seat covered that the pad wasn't already covering at 178px. ## Two rulings entries from the same search The oversized chip — a single big chip pushed out silently is a **call**, not a raise, however big it is; to raise you say so before it lands. And what a full raise is, which the pad now enforces in words. ## Validation 137 tests passing. Raise warnings verified across four amounts on a deep stack and three on a short one, at **eight viewports**: note shows, pad stays reachable, contrast clean, Confirm never disabled. Toast confirmed still normal when the pad is closed. No console errors. One note on process: two of my checks this round tripped the unresolved-pot confirm from #49 and looked like failures until I re-seeded — my test's fault, not the code's.

jheaps added 1 commit 2026-09-01 09:12:47 -06:00

Say something when the raise isn't a legal raise e0eb0d2079

Web search turned up the oversized-chip rule described as the single most common
cause of floor disputes, and specifically a home-game problem. Chasing that led to
checking what the bar does with an illegal raise, and the answer was: nothing.

With the minimum at $18 and a player holding $200, typing 13 was accepted without
a word. The engine then treated it as a short raise and correctly declined to
reopen the betting -- right for an all-in, wrong for somebody who just misheard
the bet, and either way the dealer was never told.

The raise entry now says what's wrong and still lets it through. This tool records
what the humans at the table actually did, and a dealer overruling the arithmetic
is right more often than the arithmetic is, so Confirm stays enabled in every case:

  $13 is under the $18 minimum. A legal raise is $18 or more -- otherwise
    it's a call, or all-in.
  All-in for less than a full raise. Legal, but it doesn't reopen the
    betting -- anyone who has already acted owes the difference or folds.
  More than they have. This goes in as all-in for $200.
  $10 is not above the $10 already bet -- that's a call, not a raise.

The second one surfaces the rule fixed two rounds ago at the moment it decides
something, rather than only in the rulings sheet.

Two minimums, which is where the first attempt went wrong

The pad already had a minimum, clamped to what the player can actually put in --
correct for the Min button, wrong for the warnings. For a short stack the clamped
minimum equals their all-in, so neither warning could ever fire for exactly the
player the rule exists for. Kept separate now: one for the button, the rules one
for the warnings.

A regression the audit caught, in the same round that introduced it

The note makes the raise pad taller, --actionBarHeight grows, and the toast --
which floats just above the bar since the occlusion round -- got pushed up over
the table. Measured at 360x640: bar 122px closed, 178px with the pad, 217px with a
note, and the toast climbing from y506 to y411, covering seats outright.

A toast is transient news about the action just taken; the pad is the dealer
deciding the next one. The older one gets out of the way when the pad opens --
nothing is lost, its Undo is also the bar's own undo control. The note is tighter
on short screens, and the pot breakdown hides during entry, since which side pots
exist isn't what's being read while typing an amount. Net: 210px rather than 217px,
and no seat covered that the pad wasn't already covering at 178px.

Two rulings entries, from the same search

The oversized chip -- a single big chip pushed out silently is a call, not a raise,
however big it is; to raise you say so before it lands. And what a full raise is,
which the pad now enforces in words.

137 tests passing. Raise warnings verified across four amounts on a deep stack and
three on a short one, at eight viewports: note shows, pad stays reachable, contrast
clean, Confirm never disabled. Toast still behaves normally when the pad is closed.

Sources: cardplayer.com/.../contracts-and-poker-the-oversized-chip-rule,
pokernews.com/strategy/be-careful-when-betting-essential-wsop-rules-to-remember

Co-Authored-By: Claude Opus 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_015bnp7xKUPFFSpwkYNFaPgb

jheaps referenced this pull request

2026-09-01 09:21:13 -06:00

Light up the seat that's holding the game up #57

jheaps closed this pull request

2026-09-01 09:32:20 -06:00

Pull request closed

Please reopen this pull request to perform a merge.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: jheaps/JoshHeaps.Net#56