Poker HUD Overlays Obscure 1 in 6 Time-Bank Reminders at Table 2

Poker HUD overlays cover the time-bank reminder widget in roughly one in six hands at Table 2, according to a screen-capture audit of 1,140 hands played across six client builds between 3 February and 19 March 2025. The obstruction is not random: it clusters in the 2.5-second window before the reminder fires, precisely when a player needs to see the countdown. Because the reminder is the only visual cue that a decision clock is running, its occlusion converts a timing aid into a timing hazard.

What the audit measured, and where the number comes from

The study logged hands at a six-max no-limit hold'em table on a mid-stakes rupee table (blinds ₹10/₹20), with a commercial HUD running its default profile: a three-panel overlay showing VPIP/PFR, a 3-bet grid, and a session graph anchored to the top-right of the table window. Capture ran at 30 frames per second, with each frame timestamped against the client's own action-clock API.

The reminder widget occupies a 96×28 pixel band at the lower-right of the table felt on the build tested. The HUD's session-graph panel, at default scale, covers 71% of that band. At 125% scaling — a common setting on 1440p laptops sold in India — coverage rises to 89%.

Across 1,140 hands, a reminder fired 402 times. In 68 of those firings, the HUD panel overlapped the widget for the entire visible duration of the reminder, a rate of 16.9%. That is the one-in-six figure. A further 41 firings were partially obscured, leaving the countdown digits visible but the "time bank" label hidden.

Two caveats matter for interpretation. First, the sample is one table, one client build per session, and one HUD configuration; the rate will move with panel layout and screen scaling. Second, obstruction was measured geometrically, not by asking players whether they noticed. The audit establishes that the cue was hidden, not that it was missed.

Why the reminder sits where the HUD sits

The collision is a design consequence, not an accident. Poker clients place timing widgets in the lower-right because that region stays clear of cards, chip stacks, and the action buttons that occupy the centre and lower-left. HUD developers, working from the same ergonomic logic, anchor session stats and graphs to the same corner: it is peripheral to the felt, persistent, and rarely overlaps community cards.

Both parties optimised against the same constraint and produced a conflict. The client assumes the corner is free; the HUD assumes the corner is unimportant. Neither assumption survives contact with the other.

There is a regulatory dimension. Under the All India Gaming Federation's voluntary code for skill-gaming platforms, operators commit to displaying "clear and timely" information about decision clocks where time banks are offered. A widget that is present in the client but covered by third-party software in a majority of reminder events is, on a plain reading, not clearly displayed. Whether the obligation extends to a player's own overlay choices is untested; no Indian regulator has issued guidance on HUD occlusion specifically, and the code's language addresses operator-side display rather than client-side customisation.

The time-bank mechanic the overlay is hiding

Time banks are not decorative. On the client tested, each player receives a 30-second bank per tournament or per session, replenished only between hands at a rate of one second per ten seconds of idle time. The reminder widget appears 2.5 seconds before the standard 15-second action clock expires, signalling that the next decision will draw on the bank.

A player who cannot see the reminder has two failure modes. The first is a forced fold: the clock expires, the hand is mucked, and the bank is untouched. The second is worse — the player believes the bank has engaged when it has not, or vice versa, and mis-times a decision that the bank was meant to protect.

The audit found 11 hands in which the acting player folded with more than 8 seconds remaining on the clock while the reminder was fully occluded. That pattern is consistent with a player reading the HUD graph as a substitute for the clock, or with the reminder's disappearance being interpreted as the clock having reset. Eleven hands in 1,140 is not proof of causation, but it is the kind of anomaly that a larger instrumented study could resolve.

The scaling problem

At 100% display scaling, the HUD's default layout clears the reminder band by 4 pixels. At 125%, it overlaps by 19 pixels. At 150% — common on the 15.6-inch panels that dominate the Indian laptop market — the overlap reaches 34 pixels, enough to hide the countdown digits entirely rather than merely the label.

This matters because scaling is not a niche setting. Windows sets 125% as the default recommendation on many 1080p panels at 15.6 inches, and players rarely adjust it. A HUD that behaves acceptably on the developer's 27-inch monitor can occlude the reminder on the hardware most Indian players actually use.

What operators and HUD vendors could do, and why they haven't

The technical fixes are unglamorous and cheap. Clients could render the reminder widget in a layer above third-party overlays, or reserve a protected 120×40 pixel band that overlay software is contractually and technically discouraged from covering. HUD vendors could ship a "table-safe" profile that repositions session panels to the upper-left and shrinks the graph to a sparkline.

Neither has happened at scale, for reasons that are commercial rather than technical. Clients have little incentive to accommodate third-party software they did not author and cannot audit. HUD vendors compete on information density, and a smaller graph is a worse sales pitch than a larger one. The cost of the conflict falls on the player, who experiences it as a lost hand rather than a design failure.

There is a precedent worth noting. Several international clients now expose an action-clock API that HUD software can read, allowing overlays to display a synced countdown rather than relying on the client's own widget. Where that API exists, occlusion becomes irrelevant because the information is duplicated. On the build tested, no such API was available, and the HUD had no way to know the reminder had fired.

The open question: whose clock is it?

The audit's one-in-six figure is a starting point, not a verdict. The larger question is jurisdictional. If a player installs software that hides a timing cue the operator is obliged to display, has the operator discharged its duty by rendering the cue, or must it render the cue in a way that survives the player's own tooling?

Indian skill-gaming regulation has so far treated the client as a closed system and the player's machine as private. HUD overlays blur that boundary: they are player-side software that changes what the operator's interface communicates. A regulator inclined to read "clear and timely" strictly might require protected rendering zones; one inclined to defer to player autonomy might treat occlusion as a self-inflicted harm, like turning down the volume.

What the data does not yet show is whether occlusion changes outcomes at a rate players would notice without instrumentation. The 11 anomalous folds are suggestive, not conclusive. A study that instruments the player's decision latency, rather than the widget's pixel coverage, would answer that — and would tell operators whether the fix is a rendering change or a disclosure requirement. Until then, the reminder is firing into a covered window roughly once every six hands at Table 2, and nobody in the chain has a clear incentive to move the panel.