Texas Hold'em Poker Bot
A Full Game Engine Inside Discord
A 4,200-member gaming community wanted a polished, visual Texas Hold'em experience running entirely inside Discord, complete with canvas-rendered cards, multiple concurrent tables, configurable rules, turn timers, and elimination. Here's the full story from request to delivery.
The request: a full PRD from day one
This client knew exactly what they wanted. They submitted a thorough product requirements document covering game format, configuration options, visual requirements, hosting needs, and edge cases. More detail upfront = faster delivery with fewer questions.
This is the opposite end of the spectrum from the Video Contest Bot's 5-sentence request. The client wrote a proper PRD with sections for game format, configuration options, visual requirements, edge cases, and hosting preferences. Both styles work. Write five sentences or five pages. We adapt to you.
What we delivered
All 7 commands
Canvas-rendered cards
All 52 cards rendered as images using server-side Canvas. Community cards shown on a felt-green table layout. Private hands displayed as ephemeral card images only the player can see.
Multi-table support
Multiple games can run concurrently in the same server. Each host creates their own table with independent game state, settings, and players.
Configurable rules
Starting chips, ante increase per round, and turn timer are all configurable per game. Defaults work out of the box, but hosts can tune for quick or marathon sessions.
Turn timer & auto-fold
Optional turn timer (up to 300 seconds) keeps games moving. Players who don't act in time are automatically folded. Critical for keeping distracted gamers honest.
Side pot handling
Correct side pot calculations when players go all-in with fewer chips than others. Multiple side pots tracked and resolved properly across complex multi-way all-in situations.
Late join support
Players who join after the game starts enter in a "folded" state and are dealt in on the next hand. No waiting for a new game to start.
Approved on the first attempt. The detailed PRD meant zero ambiguity about what the client wanted. We built exactly to spec, and they approved the delivery without requesting a single revision.
Key takeaway: complex builds are just another card
- Complex builds are our sweet spot. This bot involves a game state machine, image rendering, real-time multiplayer, and dozens of edge cases. It's the kind of project where freelancers typically under-scope and over-charge. With DiscordGenius, it's just another request card.
- Detailed requests = faster delivery. The client wrote a proper PRD with configuration options, visual requirements, and edge cases. We didn't need a single follow-up question. The build started immediately.
- Follow-ups are easy. The client mentioned wanting a leaderboard as a future request. When they're ready, it's just another card on their board. No new project, no new quote, no scope negotiation.
- You own the code. Even though we host and manage the bot, the client can request a full code handover at any time. No lock-in, full IP ownership.
How different clients write requests
There's no wrong format. Compare these three real examples:
| Video Contest Bot | World Map Bot | Poker Bot | |
|---|---|---|---|
| Request style | 5 casual sentences | Conversational paragraph | Formal PRD with sections |
| Complexity | Simple | Moderate | Moderate |
| Commands | 2 | 3 | 7 |
| Delivery time | <48 hours | 72 hours | ~96 hours |
| Follow-up requests | 0 | 3 iterations | Leaderboard (future) |
| Outcome | Approved first try | Evolved through feedback | Approved first try |
There's no wrong way to submit a request. Write it however comes naturally. We'll figure out the rest.