StackXo

At the table

Scanning the tournament clock

Typing at the table is the reason most people stop tracking. Point the camera at the board instead and the session sets itself up.

Two things you can scan

The tournament clock — the display the room puts on the wall. Scan it when you sit down and the form fills in with the event name, buy-in, game type and whether it’s a bounty. Scan it again later and the clock inside the app catches up to the level, blinds, time remaining and players left.

The structure sheet — the printed page with every level on it. Scan that and the app knows the whole schedule ahead of you: each level, each break, how long they run. From then on the clock moves itself along instead of waiting for you.

What it does not do

It reads what is written on the board and nothing more. Your location is never on a tournament clock, so that stays a manual choice. If a field isn’t there, it’s left blank rather than guessed at.

When it fills something in you get a one-line reminder to double-check the numbers, and it disappears as soon as you edit anything. That’s deliberate. A wrong number that looks exactly like a number you typed yourself is worse than no number.

Scanning more than once

Clock scans replace what was there, because the board is showing you now. Structure sheets add to what you have, because a long structure runs over several pages. Take as many photos as the sheet needs and save once at the end. If two scans disagree about a level, the newer one wins.

What it costs

Scanning is free for five sessions a month. Inside one session it’s unlimited: rescan the clock as often as the level changes, photograph as many structure sheet pages as it takes, none of it counts again. A session only uses one of the five the first time a scan works in it, and the count resets at the start of each month.

If you take a photo and cancel, or it can’t be read, nothing is used up. Pro removes the monthly limit.

What happens to the photo

The photo is sent to our server to be read, which is why scanning needs a connection. It’s read once and discarded in the same request. Nothing is written to disk, on our side or in the app, and no photo is kept after the fields come back.

Related