Correct payouts on tied hands, chips that can't get stranded in a cancelled game, and a chat toggle that does what it says — plus the automated testing that found it all.
A big batch of fixes just went live. Most of it is invisible plumbing, but three changes affect your chat directly: tied hands now pay out correctly, chips can no longer get stranded in a game that goes wrong, and turning chat integration off now actually turns it off.
This is the one I'm least proud of, so I'll start here. In All-In Hold'em, if the final two hands tied, the pot was supposed to split evenly between them. It didn't — the split was calculated against the wrong pot size, and half the prize money quietly disappeared instead of going to the players.
Tied final hands are uncommon, which is exactly why this survived so long. It's fixed, and there are now automated tests covering every payout mode so it can't come back.
A few paths could previously end a game without returning everyone's stake — a settlement that failed partway, or a game whose internal timer gave up after repeated errors. In both cases the pot could vanish instead of going back to players.
Now every one of those paths refunds every stake. Cancel a blackjack game after someone doubled down, and they get both bets back, not just the first.
If you turned Twitch chat integration off in your dashboard, the bot kept posting anyway. The only thing that really stopped it was disconnecting your account entirely.
Two bugs were behind that: the send path never checked whether you'd disabled it, and logging back in silently switched it back on. Both fixed. Off means off, and it stays off across logins.
Game connections now sleep while nothing is happening instead of holding resources open for an entire session, and the end-of-game database writes were collapsed from several round-trips into one. You shouldn't notice anything except overlays keeping up a bit better during busy rounds.
I also tightened permissions on the game management endpoints, so creator controls can only ever affect your own channel.
The honest note in my first post still stands: this is a one-person project and my wife has clicked through more edge cases than anyone should have to. What's changed is that she's no longer the only safety net.
There's now an automated suite that plays the games for real every single night — spawning tournaments, placing bets, cancelling them, checking that every chip lands where it should, and loading the overlays in a real browser to confirm they render. It runs against a test copy of the platform, never your channel.
That suite is how the tied-hand payout bug was found. Not a player report — a nightly run that noticed a balance ending in 950 when the only valid answers were 900 or 1100. That's the whole point of it.
Not set up yet? Getting Started takes about two minutes.