Discord bot: a screenshot in, a solved spot out

Drop a screenshot of your table in Discord and get the GTO solution for that exact spot. No spot builder, no manual stack typing — the bot reads the table, you confirm it, HRC solves it.

1. Post the print

Send the table screenshot in the Discord channel (or use /ocr). A vision model reads every seat: stacks in big blinds, bounties, blind level, players still in the hand, and who already folded. A second pass only counts the players, because a dropped seat shifts every position label after it — that is the one mistake that stays plausible while being wrong.

Anything that looks off comes back as a warning instead of being silently accepted:

2. Fix it in plain language

Nothing is queued before you confirm. If a number is wrong:

• Edit with AI — one sentence, English or Portuguese: "the CO has 8bb and add a player between the CO and the BTN". The bot applies the whole batch at once and shows the diff before Confirm.
• Edit Spot / Edit Seat / Add Seat — the same corrections through forms.
• Re-read — runs the screenshot through a different vision model. Reads vary; this is usually faster than fixing seats by hand.

3. Tell it about the tournament

ICM needs the field size, so the bot asks for the total entries from the lobby:

4. Pick the tournament and the stage

Then choose which structure the spot belongs to and how deep into the tournament you are — from 100–60% left down to Near bubble and After bubble. The stage decides the payout pressure the solve runs under:

5. Run it

The spot goes into the same HRC queue that produces the solutions already on the site:

The bot follows the job from calculation to publication and sends you a private link to the finished solution when it lands — the full viewer, ranges, EV and all, for the hand you played. A bot restart does not lose your spot; the tracker re-arms itself.

What it does not do (yet)

Worth knowing before you send the first print:

• Two formats. Vanilla Hyper and Speed Racer Bounty. Mystery Bounty spots cannot be queued.
• Speed Racer is solved on the canonical $54 scale. Whatever buy-in the print shows, the bounties are converted linearly to that scale. The blind level also has to exist in the Speed Racer structure — a level outside it is refused rather than silently solved at the wrong blinds.
• Preflop only. HRC solves the preflop tree (with subtrees two levels deep). There is no postflop solve and no street-by-street replay.
• The stage sets the tournament state, not the screenshot. Total entries plus the stage you pick decide how many players are left; the ranking text on the print is ignored on purpose.
• The read can be wrong — that is why you confirm. Stacks, bounties and level come from a vision model. Nothing is queued before you press Confirm, and anything implausible is flagged as a warning; a dropped seat is the failure to watch for, since it renames every position after it.
• It is a queue, not an instant answer. Your spot runs on the same Windows HRC machines that produce the solutions already published on the site, so it waits its turn behind them. The bot answers in your own thread whenever it finishes.
• One screenshot, one spot. Up to 8 MB per image, one table per read. No hand-history file import here — that is what the Replayer is for.
• The result is yours, not published. The finished solution comes back as a private share link. It does not enter the public solution catalogue.

Try it

The bot lives in the Short Stack Arena Discord. Join, drop a print of the hand you are unsure about, and let the solver settle it.

Join the Discord