games: the ladder gets played, and the rack learns where to stand
Trivia had every Go test passing and had never been in a browser, which this plan's own rule says means nothing. So: play it. The game itself holds up. The clock drains honestly and does not restart on a reload, the multiple compounds, walking pays exactly what the felt quoted, the reveal marks the right answer, and the auto-submit at zero lands as a timeout rather than an illegal move. The next question's answer never crosses the wire. Two bugs only the browser could show: - The spot printed double the stake after every settled game. standing() set spot.amount and *then* poured the chips on, and pour grows the pile from what it is told is already there. The money was always right; the number under the chips was not, which is the one rule the felt is built on. - The house rack sat on top of the multiplier at 390px. Its 5.75rem inset is not a margin, it is the width of blackjack's shoe — so on a phone the rack sits in the middle of the felt. It now shrinks on small screens and pulls into the corner where the corner is empty; data-at says which rack is which, because pulling blackjack's to the edge slides it under the deck. The dev rig seeds its own question bank now (one real OpenTDB batch per difficulty), because a fresh dev database 503s every start otherwise.
This commit is contained in:
@@ -278,7 +278,10 @@
|
||||
}
|
||||
bet = amount;
|
||||
showBet();
|
||||
spot.amount = amount;
|
||||
// pour grows the pile from whatever is on the spot, and settle has just swept
|
||||
// it clean — so it must not be told the chips are already there. Setting the
|
||||
// amount first counted the standing bet twice, and the spot printed 400 under
|
||||
// a 200 stake.
|
||||
return spot.pour(purseEl, amount);
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user