Wicket Blast

{
  "game": {
    "name": "Wicket Blast",
    "provider": "Turbo Games",
    "game_kind": "crash",
    "category_note": "Mines-style tile-reveal game with a cash-out ladder (grid reveal + Cash Out), NOT a reel slot. The provider's own catalogue widget calls the type 'Instant', but the build has a cash-out button and a multiplier ladder, so it is documented as crash/instant-win per the project's device-based classification (playbook turbo.md §6).",
    "series": "Part of Turbo Games' 'Cricket Arena' thematic line (per provider catalogue clustering, P-T17): Cricket Boom, Wicket Blast, Spin Strike (declared opener), Fast Fielder, Vortex Powerplay. This page/build of Wicket Blast does not itself name the line in its own rules text; membership is established from the provider's catalogue cluster markup, not from in-game text. order_in_series is not established (catalogue rank is a display-sort field, not chronology, per P-T17) and is left unset.",
    "theme": "Night-time cricket stadium. A circular green cricket pitch/field sits in the middle of the screen, ringed by a thin glowing light-green outline, lit by two tall floodlight towers (white diamond-pattern lamp clusters) in the upper-left and upper-right corners against a dark navy night sky. The reveal tiles are cricket-themed: a safely-opened tile shows an illustrated batsman playing a shot; a mine tile shows a set of broken cricket stumps (wicket) with a red cricket ball lodged between them.",
    "art_style": "Flat-to-semi-realistic illustrated 2D style: UI chrome (buttons, panels, ladder pills, icons) is clean flat vector design with rounded rectangles and soft drop shadows, while the two reveal-tile illustrations (batsman, broken stumps+ball) are more detailed painterly/airbrushed renders with visible shading and highlights, not flat-cel cartoon. Overall palette is a dark navy/near-black stadium-at-night backdrop with a saturated green pitch, cyan-to-gold accent gradient on numeric labels, and a bold red/orange sports-broadcast wordmark. No 3D rendering, no photographic elements. Mood is a slick modern sports-betting/instant-game aesthetic (night match under floodlights), not cartoonish or childlike.",
    "documentation_purpose": "Exhaustive accessibility documentation (blind/low-vision screen-reader users, deaf/hard-of-hearing, color-blind of all types, motor-impaired) built from 15 desktop screenshots (1280x800) + the dословный DOM dump of the in-game rules panel (which the provider serves as an accessible text document, per playbook turbo.md §3) + zoomed crops of the reveal tiles and UI icons.",
    "method_notes": "All numbers (RTP, limits, ladder values) are taken verbatim from either the rules panel text or from the live balance/ladder readouts on captured frames, cross-checked against the provider's product page (turbogames.io/games/wicketblast) and against two structurally related titles in the same engine family (Turbo Mines, Book Of Mines, per P-T15). One frame in the manifest (gameplay_round.png) carries a capture note that does not match its actual pixel content (see 'capture_note_discrepancy' below); the documentation below describes what is actually visible on that frame, not the note.",
    "language": "English"
  },

  "capture_note_discrepancy": {
    "frame": "gameplay_round.png",
    "manifest_note_claimed": "\"Round started (Cancel button instead of Start Game, first ladder rung x1.08 highlighted), balance still $1000\" - offered as visual proof of P-T10 (stake is deducted on the first tile, not on Start Game).",
    "actual_pixel_content": "Balance reads $999 (not $1000), the action button reads 'Start Game' in its idle gold styling (no Cancel button visible), and no ladder rung is highlighted. The 5x5 grid is fully unrevealed/idle. This is consistent with an IDLE screen shown AFTER a prior round was already lost (balance already reduced from the $1000 seen on base_game.png), not a 'round in progress' screen.",
    "conclusion": "This frame does NOT visually demonstrate P-T10's Cancel-button / delayed-deduction moment. The Cancel-before-first-tile behaviour described in P-T10 and echoed by this game's own rules text (\"You can cancel the bet only if you haven't opened any tiles yet\") is documented here from the RULES TEXT only; our captured frame set does not contain a direct screenshot of the pending/Cancel state, and that gap is listed in unreadable_or_uncertain.",
    "recommendation_for_TL": "Treat gameplay_round.png in the archive as an 'idle state, balance already reduced by one prior lost round' frame, not as the 'round started / Cancel visible' frame its note describes."
  },

  "color_palette": {
    "background": "Deep navy/near-black night sky filling the corners; a saturated mid-green circular cricket field fills the centre of the screen with a thin glowing pale-green ring outline.",
    "floodlights": "Two tall grey lamp-post towers (upper-left and upper-right) topped with white diamond-grid lamp clusters, each emitting a soft white radial glow over the dark background.",
    "wordmark": "'WICKET' in bold white letters, a small round orange/red cricket-ball icon (with visible red stitching seam) between the words acting as a bullet, then 'BLAST' in bold orange-to-red letters.",
    "tiles_unrevealed": "Dark navy-blue rounded-square tiles with a faint grey crosshair/target glyph centred on each, arranged in the selected grid on top of the green field.",
    "tile_safe_reveal": "Painterly illustration of a batsman: royal-blue helmet and shirt, white gloves, tan/wood cricket bat, red ball frozen mid-air near the bat, on a green-grass tile background with a light-green rounded border glow.",
    "tile_mine_reveal": "Painterly illustration of broken cricket stumps/wicket: three tan wooden stumps with the bails knocked off and scattered, a red cricket ball resting between them, on a green-grass tile background with an orange/amber rounded border glow (visually distinct from the safe tile's green-glow border).",
    "ladder_pills": "Horizontal row of multiplier values above the grid; low-value rungs are shown in cyan/light-blue, mid-value rungs in green, and high-value rungs in orange/gold - a colour gradient from cyan to gold as the multiplier grows. The currently-reached rung is shown as a solid filled blue oval/pill (white text on blue), all other rungs are plain text on the dark background.",
    "buttons": "Primary action button (Start Game / Place bet) is a large circular gold/yellow button with a subtle dotted-halo glow and black bold text. The Cash Out button (available after at least one safe tile is revealed) is a large circular light-blue/sky-blue button with white bold 'Cash Out' text and the cash amount in a smaller darker-blue capsule beneath it.",
    "turbo_toggle": "Small pill-shaped switch labelled 'TURBO' above it; OFF state is a dark grey track with a plain grey circular knob; ON state is a green track with a glowing green-outlined knob (green dot centre) - state is also conveyed by knob position (left=off, right=on), not colour alone.",
    "left_panel": "Dark semi-transparent rounded panel holding the Wickets stepper and the Bet Amount dial; both use white text on the dark panel with circular grey '−'/'+' buttons.",
    "accent_ui": "Red used sparingly for the ball icon in the logo and for a small notification dot on the 'TURBO UNIVERSE' icon top-right; white used for all icon glyphs (speaker, sliders/settings) on the dark header bar."
  },

  "ui_layout": {
    "top_left": "'Balance:' label in small white text, followed by the current balance in large bold white text with a '$' prefix, e.g. 'Balance: $1000'.",
    "top_left_below": "Game wordmark 'WICKET🏏 BLAST' (see color_palette.wordmark) sitting just under the balance line.",
    "top_right": "Three icons in a row: (1) 'TURBO UNIVERSE' - a white swirl/orbit glyph with two small stars and the words 'TURBO UNIVERSE' underneath in tiny bold white text, with a small red notification dot at its top-right corner (this is the provider's cross-game platform/loyalty layer, not a feature of this specific game - per playbook turbo.md §9 it belongs in 'modes', not 'features'); (2) a white speaker/sound icon with sound-wave arcs (toggles audio); (3) a white 'sliders' icon (three horizontal bars each with a round toggle knob, like an equalizer) that opens the Settings/Rules menu.",
    "right_edge_vertical_ribbon": "A dark vertical pill-shaped ribbon running down the right edge of the screen reading 'DEMO MODE' in white capital letters (top-to-bottom), with a small circular icon containing a stylised X/cross below the text. This is present on every captured frame and is the demo-mode indicator, not part of the themed game art.",
    "top_centre": "Horizontal multiplier ladder: a row of rung labels (e.g. 'x1.08 · x1.23 · x1.42 · x1.64 · x1.92 · x2.25 · x2.68 · x3.21 · x3.9' for the 5x5/3-wicket default) directly above the play grid. The number of rungs shown equals the number of safe tiles for the current grid size and wicket count (grid cells minus wickets).",
    "centre": "The play grid: a square of rounded tiles (3x3, 5x5, 7x7 or 9x9 depending on the selected 'Grid' option) laid out inside the glowing green circular pitch.",
    "below_grid": "Four pill-shaped toggle buttons labelled '3x3', '5x5', '7x7', '9x9' under a small 'Grid' caption - the active grid size is shown with a solid white outline, the inactive ones are dimmed/greyed.",
    "left_panel_top": "'Wickets' label above a stepper: a round grey '−' button, the current wicket count in large bold white digits, and a round grey '+' button.",
    "left_panel_bottom": "'Bet Amount' label with a small circular 'i' info glyph, above a circular dial control: 'max' caption with a '+' button at the top, 'min' caption with a '−' button at the bottom, and the current bet value ($ figure) in a bold white circle at the centre of the dial.",
    "right_panel_top": "'TURBO' label above the Turbo Mode toggle switch (see color_palette.turbo_toggle).",
    "right_panel_bottom": "Large circular primary action button: reads 'Start Game' (idle/normal mode) or 'Place bet' (when Turbo Mode is active and tiles have been pre-selected); after a safe tile has been opened in normal mode it is replaced by the 'Cash Out $<amount>' button.",
    "footer_left": "Small grey text 'Turbo Games · Wicket Blast' in the bottom-left corner of every game screen (provider + game name footer, per playbook turbo.md §2).",
    "footer_right": "A timestamp (e.g. '22 Aug, 2026 | 18:01:59') appears in the bottom-right corner on several - but not all - captured frames. This looks like a debug/capture-tooling overlay rather than in-game content (it is absent from the very first idle frames such as base_game.png and appears only later); it is NOT described as part of the game's own UI in this documentation."
  },

  "reveal_tiles": {
    "note": "The game has no traditional paying symbols/paytable - the payout is entirely a function of the multiplier ladder position reached, not of any tile artwork. The two tile illustrations below are documented for their VISUAL identity only (needed for accessibility and for icon generation), not as paytable entries.",
    "safe_tile": {
      "name": "Batsman (safe reveal)",
      "appearance": "A cricket batsman mid-shot: royal-blue helmet with a dark visor/grille, royal-blue short-sleeve shirt, white batting gloves, gripping a light tan/wood cricket bat that has just struck a red cricket ball (shown frozen in the air near the bat head). Illustrated in a semi-realistic painterly style over a green-grass tile background with a soft light-green rounded border glow.",
      "meaning": "Opening this tile is a safe reveal: it advances the player one rung up the multiplier ladder and keeps the round alive."
    },
    "mine_tile": {
      "name": "Wicket / broken stumps (mine)",
      "appearance": "Three tan wooden cricket stumps with the two wooden bails knocked off and scattered above them, and a red cricket ball with visible seam stitching resting in the gap between the stumps. Illustrated in the same semi-realistic painterly style over a green-grass tile background with an orange/amber rounded border glow (visually distinct from the green glow of the safe tile).",
      "meaning": "Opening this tile ends the round as a loss: the staked amount is forfeited and (per the captured bust_loss.png frame) the game reveals the positions of ALL the wickets placed on the board for that round, not just the one that was clicked."
    }
  },

  "mechanics": {
    "grid_selection": "Player picks a square grid size before starting: 3x3 (9 tiles), 5x5 (25 tiles, default), 7x7 (49 tiles) or 9x9 (81 tiles).",
    "wickets_stepper": "Number of 'wickets' (mines) hidden on the grid is chosen with a +/− stepper. Default on 5x5 is 3 wickets (22 safe tiles); default on 3x3 is 2 wickets (7 safe tiles); default on 7x7 is 5 wickets (44 safe tiles). Maximum observed on the 9x9 grid was pushed to 80 wickets (only 1 safe tile remaining out of 81), which collapsed the ladder to a single rung of x76.95 - consistent with a fair-multiplier formula of (total tiles × RTP) / safe tiles at the extreme (81 × 0.95 ≈ 76.95).",
    "ladder": "A horizontal row of multiplier rungs is shown above the grid, one rung per safe tile in the current configuration (grid cells minus wickets). Each successful safe-tile reveal advances the current position to the next rung; the reached rung is shown filled/highlighted. Rung values grow geometrically and the growth rate steepens as fewer safe tiles remain relative to wickets (e.g. 3x3/2-wickets: x1.22 … x34.2 over 7 rungs; 5x5/3-wickets: x1.08 … x3.9 shown, continuing further; 7x7/5-wickets: x1.06 … x2.75 over the first 8 of 44 rungs; 9x9/40-wickets: x1.88 … x707.43 visible within the captured frame, with the ladder continuing beyond the edge of that frame - see max_win_and_ceiling below).",
    "betting": "Bet Amount is set via the circular dial control (min/max buttons, +/− increments). Min bet $0.1, max bet $100 (from the Limits panel).",
    "start_and_stake_timing": "Per this game's own rules text (Cancel section: \"You can cancel the bet only if you haven't opened any tiles yet\") a pending/cancellable state exists after pressing Start Game and before the first tile is opened - matching the provider-wide pattern P-T10 (stake is deducted on the FIRST TILE OPEN, not on the Start Game click). Our captured frame set does not contain a clean screenshot of this pending Cancel-button moment (see capture_note_discrepancy above); the behaviour is documented here from rules text only.",
    "cash_out_normal_mode": "In the default (non-Turbo) mode, after at least one safe tile is revealed a 'Cash Out $<amount>' button appears showing the payout at the CURRENTLY REACHED rung. Pressing it ends the round and credits the payout. Cash-out is SILENT: on our captured example the field simply reset to the idle 5x5 grid with 'Start Game' showing again, and the win was visible only as a change in the balance figure ($997.00 before the round → $998.08 after cashing out at the x1.08 rung on a $1 bet) - there is no on-screen 'you won' message or overlay in this mode.",
    "cash_out_turbo_mode": "Turbo Mode changes the flow entirely: the player pre-selects (clicks) a pattern of tiles on the grid BEFORE placing the bet (selected tiles show a '?' glyph inside an amber/gold-outlined tile), the action button becomes 'Place bet', and pressing it reveals all the selected tiles at once. If the pattern is entirely safe, the round ends with a VISIBLE win overlay: a rounded dark panel reading 'YOU WIN', the dollar amount, and 'x<multiplier> Multiplier' beneath it, drawn over the grid with the winning tiles shown around it. On our captured example: 3 tiles pre-selected on 5x5/3-wickets, all 3 landed safe, overlay read 'YOU WIN $1.42 / x1.42 Multiplier', and the balance moved from $998.08 (before placing the $1 bet) to $998.50 after the win was credited.",
    "loss": "If a wicket tile is opened (normal mode) or is included in the pre-selected pattern (Turbo Mode), the round ends immediately as a loss, the stake is forfeited, and (observed on the normal-mode example) the positions of ALL wickets on that round's board are revealed on the grid at once, not just the clicked one.",
    "grid_size_vs_wicket_defaults": "Changing the grid size resets the wicket count to a new grid-specific default and regenerates the ladder length (3x3 defaults to 2 wickets, 5x5 to 3, 7x7 to 5); the 9x9 default was not separately captured, but 40 and 80 wicket configurations were exercised manually on it."
  },

  "max_win_and_ceiling": {
    "rulebook_text_is_inherited_boilerplate": "The rules panel's 'Min & Max Multiplier' section states verbatim: 'The minimum win multiplier is x0.99. The maximum win multiplier is x4940285 (it could be achieved for setting with 13 mines & 12 successively opened tiles). However, the maximum win is limited by the operator and can be accessed from the \"Limits\" section in the settings menu.' This is IDENTICAL wording (and identical numbers, x0.99 / x4940285 / '13 mines & 12 tiles') to the base 'Mines' title's rulebook (playbook turbo.md §10-bis). Wicket Blast's own grid is selectable (3x3/5x5/7x7/9x9), unlike the fixed 5x5 grid that 'x4940285/13 mines' actually describes, so this printed figure is a copy-pasted template value that does NOT describe this build's real ceiling - it is recorded here as a direct quote, not as this game's max_win.",
    "actual_ceiling_x805001": "The real ceiling for this build is x805001, corroborated by: (1) the provider's own product page (turbogames.io/games/wicketblast) stating 'a maximum win of x805001'; (2) the same cap figure (x805001) already confirmed on two structurally related Turbo Games titles that share this configurable-grid mines engine, Turbo Mines and Book Of Mines (P-T15 - shared ceiling and shared 3x3/5x5/7x7/9x9 grid-selection structure are the reliable kinship signals for this engine family, NOT the ladder values themselves, which are generated by one shared formula and will coincide across any two titles at the same grid/wicket setting). (3) Partial visual support: pushing the 9x9 grid to 40 wickets produced a ladder that reached x707.43 within the first 9 of a theoretical 41 rungs visible inside the captured 1280x800 frame, geometrically consistent with continuing to grow past x805k a few rungs later before the operator cap would truncate it (the same truncation behaviour already documented for the sibling title Turbo Mines, P-T14) - however, our archived screenshot of that 9x9/40-wicket ladder shows only the visible on-screen portion (up to x707.43); it does not itself show a printed 'x805001' rung, so this third channel is corroborating/consistent rather than a direct screenshot proof.",
    "operator_cap_max_profit": "Separately, the Limits panel shows 'Max Profit: $10000' - an absolute OPERATOR MONEY CAP (not a multiplier). At the $0.1 minimum bet this connects at a x100000 multiplier; at the $100 maximum bet it connects at only x100. This is a different quantity from both the ladder multiplier and the x805001 ceiling and must not be confused with either.",
    "conclusion_for_max_win_field": "max_win = 805001 (multiplier). The x4940285 figure from the rules text is recorded as an inherited-boilerplate anomaly, not used as max_win."
  },

  "rtp": {
    "value_percent": 95.0,
    "form": "Single number (no range), unlike the base 'Mines' title which prints a range (94.71%-95.30%).",
    "verbatim_quote": "\"Game relies on a coefficient called \\\"RTP\\\" (Return to Player) which is the statistical average of payouts over billions of rounds. Wicket Blast has RTP 95.0%\" (Rules panel, RTP section).",
    "showcase_agreement": "The provider's product page also states RTP 95% for this title - agrees with the in-game figure (unlike several sibling titles at this provider where the showcase RTP diverges from the build, P-T01/P-T01-bis)."
  },

  "limits": {
    "min_bet": "$0.1",
    "max_bet": "$100",
    "max_profit_operator_cap": "$10000 (absolute dollar cap set by the operator, see max_win_and_ceiling.operator_cap_max_profit)",
    "source": "info_limits.png - 'Limits' panel reached via the settings/sliders icon."
  },

  "payout_basis": {
    "rule": "Payout = ladder multiplier at the reached rung × the total stake of the round.",
    "measured_evidence": "Balance went from $997.00 to $998.08 after cashing out at the x1.08 rung with a $1 stake in normal mode (997 + 1×1.08 = 998.08, exact match). In Turbo Mode, balance went from an effective $997.08 (after a $1 stake was deducted from $998.08) to $998.50 after a 3-tile pre-selected pattern all landed safe at x1.42 (997.08 + 1×1.42 = 998.50, exact match).",
    "currency_note": "The demo balance is shown in US dollars ('$'). Per project convention this is the demo-balance display unit only and is not asserted as the game's real-money currency field."
  },

  "turbo_mode": {
    "what_it_is": "An alternate play mode toggled by the 'TURBO' switch on the right panel. Instead of revealing tiles one at a time and choosing when to cash out, the player pre-selects a pattern of tiles on the idle grid (selected tiles show a '?' inside an amber-outlined tile) and presses 'Place bet' to reveal the whole pattern at once.",
    "rules_text_quote": "\"Click on \\\"Turbo\\\" toggle to switch game mode. Choose the playing field size and select a pattern. Press 'Place bet' to reveal all selected tiles at once. Find the hidden batsmen while avoiding the wickets to win big\" (Rules panel, Turbo Mode section).",
    "win_presentation_differs_from_normal_mode": "This is the ONLY mode in which the game shows an explicit win overlay ('YOU WIN $<amount> / x<multiplier> Multiplier'); the normal (non-Turbo) mode's cash-out is silent and only visible via the balance change (see mechanics.cash_out_normal_mode / cash_out_turbo_mode). For accessibility purposes this is an important distinction: in normal mode, a screen-reader or low-vision user has NO on-screen confirmation of a win beyond the numeric balance readout changing; in Turbo Mode the win is announced with large on-screen text."
  },

  "rules_panel": {
    "navigation": "Reached via the sliders/settings icon top-right. A left-hand vertical menu lists six sections: 'How to Play?', 'Game Details', 'RTP', 'Turbo Mode', 'Settings', 'Version'. It is a single continuously scrollable document (not an accordion) - all 6 sections were captured across 7 screenshot pages.",
    "how_to_play": "Opens with an emoji-decorated tagline: \"Play Wicket Blast! Avoid the wickets and smash your way to victory! 🏏💥\" followed by 3 bullets: \"Choose the number of wickets, field size and press 'Start Game' to begin\"; \"Click on tiles to reveal batsmen\"; \"Cash out before you hit a wicket to win your reward\".",
    "game_details_place_bet": "\"Choose the playing field size. Choose the number of wickets. The more wickets are on the playing field, the higher the winning multiplier will be, as well as hitting wicket chance. Enter a valid amount in the field \\\"Amount\\\". Press \\\"Start Game\\\"\".",
    "game_details_gameplay": "\"With each opened batsman, the winning amount increases. But if you hit a wicket, you lose your bet. So choose wisely!\"",
    "game_details_cash_out": "\"When you've found one or more batsmen, you can press 'Cash out' to collect your reward. If you've found all the batsmen, cash out will be triggered automatically.\"",
    "game_details_cancel": "\"You can cancel the bet only if you haven't opened any tiles yet\"",
    "min_max_multiplier": "\"The minimum win multiplier is x0.99. The maximum win multiplier is x4940285 (it could be achieved for setting with 13 mines & 12 successively opened tiles). However, the maximum win is limited by the operator and can be accessed from the \\\"Limits\\\" section in the settings menu.\" - see max_win_and_ceiling for why this figure is inherited boilerplate, not this build's real ceiling.",
    "rtp_section": "\"Game relies on a coefficient called \\\"RTP\\\" (Return to Player) which is the statistical average of payouts over billions of rounds. Wicket Blast has RTP 95.0%\"",
    "turbo_mode_section": "\"Click on \\\"Turbo\\\" toggle to switch game mode. Choose the playing field size and select a pattern. Press 'Place bet' to reveal all selected tiles at once. Find the hidden batsmen while avoiding the wickets to win big\"",
    "settings_section": "\"Click the gear icon in the top right corner of the screen to open the settings menu. In Settings you can:\" followed by 4 bullets: \"change the nickname\"; \"view the minimum bet, maximum bet, and maximum profit limits\"; \"turn on/off sounds\"; \"view your betting history\". Autoplay is NOT mentioned anywhere in this list or elsewhere in the rules text.",
    "version_section": "\"Game version: \\\"1.0.2\\\" / RNG version: \\\"2.0.0\\\"\" - build/RNG version numbers, not a release date."
  },

  "screens": {
    "preview": {
      "type": "preview",
      "content": "Provider loading splash, not a game-specific promo screen: solid black background, centred red circle containing a black plus/cross emblem, and the bold white wordmark 'TURBO GAMES' (with a small red accent dot after 'TURBO'). No Wicket Blast branding, no numbers, no volatility indicator. Captured via burst at ~1.76s into load, per playbook turbo.md §1/§13 (this provider's demos have no separate game-specific promo splash - loading goes straight into the idle field).",
      "color_blind_notes": "High-contrast white-on-black text; the only colour cue (red circle) carries no unique information (it's decorative branding)."
    },
    "base_game": {
      "type": "base_game",
      "content": "Idle/ready state: 5x5 grid selected (default), Wickets stepper shows 3, Bet Amount $1, Balance $1000, full 9-rung ladder for this configuration partially visible (x1.08 through x3.9, 8 of the notionally-22 rungs fit in the header row and are shown, the rest are implied by 'grid cells minus wickets'), TURBO toggle off, 'Start Game' button in idle gold styling. See ui_layout for the full persistent chrome (balance, wordmark, top-right icons, DEMO MODE ribbon, footer).",
      "color_blind_notes": "Grid-size buttons (3x3/5x5/7x7/9x9) distinguish the active one by a white outline/highlight, not colour alone; Wickets stepper and Bet dial use +/− glyphs, not colour."
    },
    "gameplay_round_idle_after_loss": {
      "type": "base_game",
      "content": "SEE capture_note_discrepancy. Actual content: idle 5x5 grid (unrevealed), Balance $999 (already reduced from the $1000 base-game default, i.e. a prior round has already been lost), Wickets still 3, ladder unlit, 'Start Game' button idle. No Cancel button and no highlighted rung are visible on this frame.",
      "color_blind_notes": "Same as base_game."
    },
    "gameplay_reveal": {
      "type": "base_game",
      "content": "One safe tile has been opened (batsman illustration, top-right tile of the 5x5 grid). Balance $997 (a stake of $1 was already deducted for this round, following two earlier lost rounds that took the balance from $1000 to $998). The ladder's first rung (x1.08) corresponds to the value shown on the 'Cash Out $1.08' button now replacing 'Start Game'; the SECOND rung (x1.23) is shown as the highlighted/filled pill, indicating the reward for opening one more safe tile.",
      "color_blind_notes": "Cash Out button is identified by its distinct shape/position (bottom-right, replacing Start Game) and explicit text/amount, not by colour alone, though it is coloured light-blue versus the gold Start Game button."
    },
    "bust_loss": {
      "type": "base_game",
      "content": "A lost round: the player's clicked tile (top-left) shows the broken-stumps/wicket illustration, and the game has also revealed the OTHER two wicket positions on this board (middle row, bottom-left) even though they were never clicked. Balance $998 (down from $999, i.e. this round's $1 stake was forfeited). Ladder's first rung (x1.08) is shown filled/highlighted even though this round ended in a loss - likely indicating '0 safe reveals reached' rather than a payout. 'Start Game' button has returned (round over).",
      "color_blind_notes": "Wicket tiles have a distinct orange/amber glow border versus the green glow border of a safe batsman tile - redundant with the very different artwork (stumps+ball vs batsman), so identifiable by shape alone as well."
    },
    "grid_3x3": {
      "type": "other",
      "content": "3x3 grid selected, Wickets defaulted to 2 (7 safe tiles). Full ladder of exactly 7 rungs fits on screen: x1.22, x1.63, x2.28, x3.42, x5.7, x11.4, x34.2. This is the only captured grid size whose complete ladder fits within the 1280px frame width.",
      "color_blind_notes": "Same ladder colour gradient (cyan→green→gold) as other grids; all values are printed as text."
    },
    "grid_7x7": {
      "type": "other",
      "content": "7x7 grid selected, Wickets set to 5 (44 safe tiles). Balance shown as $998.5 (state carried over from a prior round). Only the first 8 of the theoretical 44 ladder rungs fit on screen: x1.06, x1.18, x1.32, x1.48, x1.67, x1.88, x2.13, x2.42, x2.75 (9 values visible).",
      "color_blind_notes": "Same as other grids."
    },
    "grid_9x9_maxladder": {
      "type": "other",
      "content": "9x9 grid selected, Wickets manually raised to 40 (41 safe tiles). Balance $1000 (fresh idle state, no round played on this configuration). Only 9 of the theoretical 41 ladder rungs fit within the visible 1280px-wide frame: x1.88, x3.75, x7.6, x15.61, x32.48, x68.57, x146.93, x319.8, x707.43. See max_win_and_ceiling for how this frame contributes to (without alone proving) the x805001 ceiling.",
      "color_blind_notes": "Same as other grids; the 9x9 grid packs 81 small tiles tightly, still using the same crosshair-on-navy-tile styling as the other sizes."
    },
    "turbo_mode_pattern": {
      "type": "other",
      "content": "TURBO toggle is ON (green). Three tiles in the top-left of the 5x5 grid are pre-selected, shown as amber/gold-outlined tiles each containing a white '?' glyph. Action button reads 'Place bet' (gold). The ladder's x1.42 rung (3rd position) is shown highlighted, indicating the potential payout if all 3 selected tiles are safe. Balance $998.08 (carried over, bet not yet placed).",
      "color_blind_notes": "Pre-selected tiles are marked by both a distinct amber outline AND a '?' glyph (redundant shape+symbol cue, not colour-only)."
    },
    "win_screen_turbo": {
      "type": "win_screen",
      "content": "Result of the Turbo Mode round above: all 3 pre-selected tiles were safe. A rounded dark win panel is drawn over the centre of the grid reading 'YOU WIN' in large bold white/cyan-glow letters, '$1.42' beneath it, and 'x1.42' with the caption 'Multiplier' below that. The 3 winning tiles are shown around/behind the panel: the top row shows the 3 opened batsman tiles plus one wicket tile revealed at the far right of that row, and a wicket tile is also revealed in the bottom row - i.e. even on a win, the OTHER wicket positions on the board are shown once the round resolves. A small '+1.42' floating credit indicator appears above the balance figure, which reads '$998.5' (997.08 after the $1 stake was deducted from 998.08, plus the 1.42 payout = 998.50).",
      "color_blind_notes": "The win text is large, high-contrast, and paired with explicit numerals ('$1.42', 'x1.42') - not colour-coded information."
    },
    "win_screen_regular_is_silent": {
      "type": "base_game",
      "note": "See mechanics.cash_out_normal_mode. The frame filed in the manifest as 'win_screen.png' for the NON-Turbo cash-out is visually indistinguishable from the plain idle base_game screen (5x5 grid, Start Game button, no overlay) apart from its balance figure ($998.08, up from $997.00 before that round). It is documented here as evidence that normal-mode cash-out produces NO visual win confirmation, which is itself an important accessibility finding (screen-reader/low-vision users get no non-numeric win signal in this mode)."
    },
    "info_limits": {
      "type": "info",
      "content": "A separate full-screen black panel (not overlaid on the game field) titled 'Limits' with a 'Back' arrow (top-left) and an 'X' close button (top-right). Three stacked rows, each a dark bordered card with a small red icon on the left: 'Min bet: $0.1' (icon: a circular arrow/gauge), 'Max bet: $100' (icon: a banknote), 'Max Profit: $10000' (icon: an upward arrow in a circle). Faint grey diamond/sparkle watermark pattern tiles the background.",
      "color_blind_notes": "Each limit row is labelled with explicit text, and the icons differ by shape (gauge / banknote / up-arrow), not colour alone (all three icons are the same red)."
    }
  },

  "not_captured": [
    {
      "claim": "Autoplay is absent from this game (confirmed by the Settings section of the rules text, which lists nickname/limits/sound/betting-history but never mentions autoplay or auto-cashout, and by the absence of any autoplay control on any captured screen).",
      "methods": ["rules_text", "screen_survey"]
    },
    {
      "claim": "The pending 'Cancel' state (round started, stake not yet deducted, per P-T10 and the rules text's Cancel section) was not captured as a clean screenshot - see capture_note_discrepancy.",
      "methods": ["rules_text_only"]
    },
    {
      "claim": "The full extent of the 9x9/40-wicket ladder beyond x707.43 (up to the theorised ~x805001 cap) was not captured as printed on-screen text; it is corroborated instead via the provider's product page and sibling-title comparison (P-T15).",
      "methods": ["provider_page_url", "sibling_title_comparison"]
    }
  ],

  "accessibility_summary": {
    "screen_reader": "Every numeric readout that matters for play (balance, bet amount, wickets count, ladder rung values, limits, RTP) is rendered as on-screen TEXT rather than colour/shape-only encoding, which is favourable for screen-reader/OCR-based accessibility tooling, PROVIDED the tool can read canvas-rendered text (this is a canvas game per the manifest device notes - no native DOM buttons for the play controls themselves, though the rules panel IS DOM text, per playbook turbo.md §3). The one significant gap is the silent normal-mode cash-out (see win_screen_regular_is_silent): a user relying only on a 'did something happen' audio/visual cue would miss a completed win in this mode; the Turbo Mode win overlay does not have this problem.",
    "color_blind": "The ladder's cyan→green→gold colour progression and the tile glow-colour difference (green for safe, amber/orange for wicket) are both REDUNDANT with shape/text: rung values are always printed as numerals, and the two tile types have completely different artwork (batsman vs. broken stumps), so colour-blind users are not dependent on colour to distinguish them.",
    "motor": "All controls (Wickets stepper, Bet dial, grid-size buttons, Turbo toggle, Start Game/Place bet/Cash Out) are large, well-separated circular or pill-shaped click targets; no drag, hold, or precision-timing input is required in normal mode. Turbo Mode requires selecting multiple individual tiles before placing the bet (multiple discrete clicks), which is not a fine-motor-intensive action beyond ordinary clicking.",
    "deaf_hard_of_hearing": "All information used to play (multiplier values, win/loss outcome, balance) is presented visually; sound is a togglable enhancement (speaker icon, top-right) with no unique game-critical audio cues identified in the rules text or on captured screens."
  },

  "unreadable_or_uncertain": [
    "Volatility is not stated anywhere in this game's UI or rules text, and is not present in the provider's catalogue listing beyond a template constant that applies identically to all 45 of the provider's games (P-T16) - left as an honest omission, consistent with the rest of this provider's catalogue.",
    "provably_fair status is not confirmed: the rules panel's Version section prints an 'RNG version' number but no provably-fair verification/seed-checking mechanism is described or shown anywhere in this build.",
    "The exact 9x9-grid default wicket count was not captured (only the manually-set 40 and 80 configurations were exercised); the 3x3 default is 2 wickets and the 5x5 default is 3, but the 9x9 default pattern was not separately observed.",
    "The full 41-rung 9x9/40-wicket ladder is not visible on any single captured frame - only the first 9 rungs (up to x707.43) fit inside the 1280px-wide viewport; the tail of that ladder and its exact final capped rung were not read as printed text (see max_win_and_ceiling).",
    "The pending/Cancel state described in the rules text (bet placed, no tile opened yet) was not captured as a clean screenshot - see capture_note_discrepancy.",
    "Exact release date is not present on any captured screen or in the rules text; not established in this documentation pass (out of scope for tech_doc.json - handled separately by the dating workflow)."
  ]
}