Show and side show: read the comparison rule

Start with the purpose of the comparison

A show commonly compares eligible remaining hands to decide the round. A side show is a private comparison request between eligible players under the table’s rules. Similar wording does not make the controls interchangeable. Before selecting either, identify whose cards are involved and what the comparison will decide.

Eligibility comes before the button

A visible control does not explain every condition behind it. Look for the number of active players, the required player state and whose turn it is. A disabled control might reflect a rule rather than a connection fault. Record its label and the table state before treating it as a technical problem.

A request is not yet a result

For a comparison that needs another player’s response, separate “requested”, “accepted” and “resolved” in your notes. Do not infer acceptance from the press alone. The table documentation should explain any refusal, timeout or equal-hand outcome. This article does not assign one universal rule to those cases.

Use a three-line observation log

Write the action label, the response message and the final recorded state on separate lines. For a practice exercise, invent neutral messages such as “request sent” and “waiting”. Ask a second reader which line actually establishes a result. This is a way to learn interface reading without simulating a paid round.

When the displayed result is unclear

Keep the time, app version and exact text visible on screen. Read the table’s comparison and connection rules together; a screenshot without the preceding state may omit the important part. For an account-specific answer, use a verified in-app contact. The website cannot inspect a hand history or reverse an action.

Common questions