Avia Fly

{
  "game": {
    "name": "Avia Fly",
    "catalog_name": "Avia Fly",
    "in_game_wordmark": "AVIA FLY",
    "wordmark_matches_catalog_name": true,
    "provider": "InOut Games",
    "game_kind": "crash (multiplayer/shared live rounds), with a second range-betting mode called 'Trenball'",
    "theme": "Minimalist aviation / flight-departure theme: a small red toy-like biplane climbs over a dark navy 'radar map' background. No narrative characters, no reel symbols - the whole game is one continuously-running growing multiplier represented by the climbing plane.",
    "art_style": "Flat 2D vector illustration, cartoon-simple biplane with rounded shapes and thick flat color fills (no gradients on the plane itself); dark navy/charcoal background overlaid with a faint thin white square grid and faint darker geometric silhouette shapes (evoking a night-time radar/world-map dashboard); UI chrome is flat, sharp-cornered, dark slate-grey panels with solid (non-gradient) accent colors - red, royal blue, forest green, gold/amber, bright green for buttons and status badges; the only non-flat effect observed is a soft round blurred orange/red 'explosion' puff replacing the plane at the moment of crash. Overall mood is a moody, nighttime, casual-competitive multiplayer betting dashboard - not childish, not photorealistic, not neon-cyberpunk. Camera is a fixed, straight-on/orthographic front view of the aircraft (no isometric or side-scrolling perspective); the plane only moves vertically (up) and does not bank, turn or fly off-screen.",
    "documentation_purpose": "Exhaustive accessibility documentation (blind/low-vision screen-reader users, deaf/hard-of-hearing, color-blind of all types, motor-impaired) built from 12 primary desktop screenshots (1280x800) plus additional verification frames, read directly with vision (pytesseract OCR repeatedly timed out under host CPU load from concurrent capture sessions - text below was transcribed manually and verbatim from the images, not invented).",
    "method_notes": "This is a LIVE/SHARED crash game: rounds run continuously with other (real or simulated) players visible in real time, in their own currencies. Screenshots are single moments of a constantly changing stream (multiplier value, round ID, player list, history ribbon all change second to second even without our input) - numbers quoted below are illustrative examples of a given frame, not fixed game constants, and are always anchored to their source frame.",
    "language": "English"
  },

  "color_palette": {
    "background": "Dark navy/charcoal (near-black with a blue tint) full-screen background, overlaid with a faint, thin white square grid (like graph paper) and faint darker geometric polygon silhouettes (diamond/map-like shapes) visible mainly in the lower-left and right thirds of the screen - decorative, not interactive.",
    "top_bar": "Same dark charcoal as background, no separate panel color; logo at far left, pill-shaped balance readout and icon buttons at far right.",
    "logo_avia_fly": "Wordmark 'AVIA FLY': a red angular chevron/arrow shape (like two stacked flattened triangles, suggesting wings or a paper-plane nose) to the left of 'AVIA' in bold white letters, a matching smaller red chevron between 'AVIA' and 'FLY', and 'FLY' in bold white letters - red and white only, no gradient.",
    "aircraft": "Small biplane, front-on view: red upper wing pair with a round tan/gold circular emblem containing a small yellow lightning-bolt icon on each wingtip; red fuselage/nose cone; a round tan/beige cockpit window in the center of the nose; a light-grey two-blade propeller at the very top with a thin horizontal light-blue bar/line floating just above it (a subtle motion/altitude cue); thin grey tripod landing-gear struts extending down from the fuselage. At the moment of crash the plane graphic is replaced by a soft, blurred, rounded orange-to-dark-red explosion/smoke puff at the same screen position.",
    "multiplier_readout": "Large bold white text (e.g. 'x4.25') centered above the plane during a live round. At the crash moment the number and the word 'CRASH' beneath it recolor to match the range/history-chip color system: dark red/maroon for a crash between 1x and 2x (exclusive), medium blue for 2x and above (below 10x), bright green for 10x and above. Example evidence: win_screen_trenball.png shows 'X 1.61' and 'CRASH' in dark red/maroon (Red range); _trenball_bet_placed.png shows 'X 29.63' and 'CRASH' in bright green (Green range).",
    "history_ribbon_chips": "Rounded rectangle chips along the top edge, each printing a past round's crash multiplier (e.g. 'x3.74'). Chip fill color follows the SAME three-way scheme as the multiplier readout and the Trenball range buttons: dark red/maroon = crashed between 1x and 2x (exclusive), medium/royal blue = crashed at 2x or higher (up to just under 10x in observed chips), forest/bright green = crashed at 10x or higher. This color coding is a direct visual echo of the Trenball Red/Blue/Green ranges described in rules_p2.png.",
    "team_red_blue_panels": "In Trenball mode the left column is headed 'Team RED' (white text) and the right column 'Team BLUE' (white text), each showing a running pooled-stake total in a currency-prefixed number. Player rows use a small circular red-outlined person-silhouette avatar icon. A row for a player whose bet has just won is outlined in bright green with the amount in bright green prefixed with '+'; a still-open or losing bet row stays on the default dark slate background with the amount in plain white.",
    "buttons_bet_flow": "BET button: solid bright/lime green fill, white bold 'BET' text - shown while no bet is placed for the upcoming/current window. CASHOUT button (Classic, bet in flight): solid amber/orange fill, white bold 'CASHOUT' text plus the live dollar amount beneath it (e.g. 'CASHOUT $2.84'). BETTING/Cancel button (bet queued for the next round while the current one is still flying): solid medium blue fill, white bold 'BETTING' on top and 'Cancel' in a lighter weight beneath. CANCEL button (Trenball equivalent, or post-crash pending state): solid red/crimson fill, white bold 'CANCEL' text.",
    "trenball_range_buttons": "Three fixed side-by-side buttons, each two-toned per range: 'Payout: 1.81x / BET' on a dark-red/crimson fill (Red range), 'Payout: 2x / BET' on a medium blue fill (Blue range), 'Payout: 10x / BET' on a forest-green fill (Green range).",
    "toggle_switches": "Auto Cashout / Sound / Music toggles: a small pill-shaped track with a round knob. Off = dark grey track, white knob on the LEFT. On = bright green track, white knob on the RIGHT. Both a color change AND a knob-position change occur together (position is the redundant non-color cue).",
    "load_more_button_bet_history": "Solid amber/gold-brown fill, bold dark text 'LOAD MORE', beneath the bet-history table.",
    "latency_badge": "Small rounded badge bottom-right showing a millisecond value (e.g. '471ms') in reddish/salmon text on a dark reddish-tinted translucent background, next to a small wifi-signal icon; color did not change across any captured frame (always the same reddish tint), so it could not be confirmed to encode connection quality - see unreadable_or_uncertain."
  },

  "layout_and_screens": {
    "base_game_classic": {
      "source_frames": ["base_game.png", "_bet_ready.png", "_after_bet.png (mid-flight, bet active)", "_after_cashout.png (post-crash)"],
      "top_bar": "Left: 'AVIA FLY' logo/wordmark. Right-aligned group: a rounded rectangle 'How to play?' button with a small circled-'i' icon and white text, a dark pill showing the account balance with a small white circular dollar-sign icon (e.g. '1 000 000  $'), a square fullscreen-toggle icon button (four corner-arrows), and a hamburger-menu icon button (three horizontal white lines in a circle).",
      "history_ribbon": "A horizontal strip directly under the top bar: a left-pointing chevron-in-circle 'scroll back' button, roughly 12 visible colored multiplier chips (see color_palette), and a right-pointing chevron-in-circle 'scroll forward' button - lets the player browse further back through past-round results.",
      "left_panel_bets_table": "Header row 'Bets' (label) and the pooled total stake for the room in dollars (e.g. '$ 14.12'), then column headers 'Players' / 'Bets'. Below, a scrollable list of up to ~5 visible rows: red circular avatar icon, truncated player name/handle (e.g. 'Bekmurod', 'BouncyBream3...', a long alphanumeric guest id, or literal '?????' for anonymous), and their stake shown in THEIR OWN currency with the matching symbol/code (examples observed: '$' USD, '€' Euro, '₹'/'NPR' Nepalese Rupee, 'SAR' Saudi Riyal, '₱'-style 'P$', 'Rs'/local Indian formats like '2.93k'). A row whose bet has just cashed out in profit is outlined bright green with the amount in green prefixed '+'.",
      "center_stage": "Large bold multiplier readout centered above the aircraft; the aircraft itself centered in the lower-middle of the stage, rising very slightly as the multiplier increases; on crash the aircraft is replaced by the explosion graphic and the word 'CRASH' appears under the final multiplier value. Between rounds a centered message 'STARTS IN N.NN SECONDS' counts down instead of showing an active multiplier (info.png, _min_bet.png, _max_bet.png, bet_history_two_ranges.png all capture this waiting phase).",
      "mode_switch": "Centered pill-shaped two-option toggle directly above the bet panel: 'Classic' | 'Trenball'. The active mode has a lighter/raised dark-grey background and bold white text; the inactive mode is flat and its text is dimmed grey. Clicking switches the entire bottom bet panel's contents (see below) without reloading the page.",
      "bet_panel_classic": {
        "stake_field": "A dark rounded rectangle containing, left to right: a 'MIN' text button, a centered numeric stake VALUE (read-only display, e.g. '3', '0.12', '200'), and a 'MAX' text button. There is NO separate manual numeric-entry/keyboard field anywhere in the interface for this value - clicking the number itself (verified in _bet_field_click.png) does not open an editable input; the stake can only be changed via MIN, MAX, or the four quick-amount buttons below.",
        "quick_amount_buttons": "Four fixed preset buttons directly under the stake field, each showing a coin/dollar icon and a value: '2 $', '3 $', '8 $', '20 $'. Clicking one sets the stake field to that exact amount.",
        "auto_cashout_control": "Label 'Auto Cashout' with an on/off toggle switch to its right (off by default on fresh load per base_game.png; observed turned on in win_screen_classic.png and _min_bet.png/_max_bet.png). When on, a secondary row appears: a round '−' (decrease) button, the current auto-cashout multiplier (e.g. '2 x', decremented to '1.9 x' in _autocashout_minus.png after one click of '−'), and a round '+' (increase) button. Default value observed on every capture where the toggle was on: 2x. Step size measured directly: exactly 0.1x per click (2.0x -> 1.9x for one '−' press).",
        "primary_action_button": "Right side of the panel, large: 'BET' (green, no bet placed) / 'CASHOUT $X.XX' (amber, our bet is live and in-flight, amount updates continuously with the multiplier - _after_bet.png shows 'CASHOUT $2.84' at x1.25) / 'BETTING' + 'Cancel' (blue, our bet is queued for the NEXT round because it was placed while the current round was still flying) / 'CANCEL' (red, queued/pending bet can be withdrawn before the round it is queued for starts)."
      },
      "bottom_left_round_id": "Plain white small text, bottom-left corner: 'Round ID: <number>' (e.g. 'Round ID: 126680') - changes every round, purely informational/audit value."
    },

    "base_game_trenball": {
      "source_frames": ["base_game_trenball.png", "win_screen_trenball.png", "_trenball_bet_placed.png"],
      "layout_change_from_classic": "The single 'Bets' table is replaced by TWO side-by-side tables: 'Team RED' (left) and 'Team BLUE' (right), each with its own pooled-stake total and its own Players/Bets column pair. A third color (Green) exists as a betting option but was NOT observed with its own dedicated table column in any captured frame - it is possible a 'Team GREEN' column only appears once it has at least one bet, or it may render in the same space depending on which ranges have active bets; this could not be confirmed further and is listed in unreadable_or_uncertain.",
      "bet_panel_trenball": "Replaces the single BET button with three side-by-side, fixed-odds range buttons sharing the same stake field described above (MIN/MAX/quick-amounts/no manual entry): red 'Payout: 1.81x / BET', blue 'Payout: 2x / BET', green 'Payout: 10x / BET'. Any one of the three can be clicked to place a stake on that range; per rules_p2.png ('You may select multiple ranges'), more than one can be selected/placed in the same round. A selected/queued range shows the same BETTING/Cancel blue treatment described above on that specific button (_trenball_bet_placed.png: Blue button shows 'BETTING' / 'Cancel' while Red and Green still show their normal 'Payout:Nx / BET' state)."
    },

    "how_to_play_dialog": {
      "type": "rules",
      "page": 2,
      "frame": "rules_p2.png",
      "title": "How to play?",
      "verbatim_text": [
        "1. Classic mode: Make a withdrawal after the bet, but before the plane crashes. The win depends on the coefficient which you made a withdrawal on.",
        "2. Trenball mode: It is a bet range where the plane would reach the destination. The withdrawal will occur automatically in the reached range, defining your winnings. You may select multiple ranges. Commands with different ranges:",
        "   a. Red: 1-2 (not inclusive).",
        "   b. Blue: 2 and higher.",
        "   c. Green: 10 and higher.",
        "3. You can play in two modes at the same time.",
        "4. Malfunction voids all pays and plays"
      ],
      "notes": "Rule 2.a-c literally defines Blue ('2 and higher') and Green ('10 and higher') as OVERLAPPING ranges from 10x upward - a crash at, say, 15x would by this text pay BOTH Blue and Green if both were bet. This overlap is stated in the printed rules; it was not itself reproduced by a captured crash (no observed round crashed at >=10x while both Blue and Green were bet simultaneously by our test account) - see payout_basis below for the caveat."
    },

    "game_rules_dialog": {
      "type": "rules",
      "page": 1,
      "frame": "rules_p1.png",
      "title": "Game rules",
      "subtitle": "Bet limits are presented below",
      "verbatim_text": [
        "Min bet: 0.12 USD",
        "Max bet: 200 USD",
        "Max win: 20 000 USD",
        "Malfunction voids all pays and plays"
      ]
    },

    "hamburger_menu": {
      "type": "settings",
      "frame": "settings.png",
      "trigger": "Click the three-line hamburger icon, top-right of the top bar.",
      "content": [
        "Header row: circular avatar placeholder icon, our session display name (e.g. 'Cyan Occu...', truncated), and grey text 'Change avatar' to the right.",
        "Toggle row: speaker icon + 'Sound' + on/off switch (observed OFF by default).",
        "Toggle row: musical-note icon + 'Music' + on/off switch (observed OFF by default).",
        "Divider line.",
        "Menu item: shield icon + 'Provably fair settings' (opens the provably-fair dialog).",
        "Menu item: document icon + 'Game rules' (opens the Game rules / bet-limits dialog, rules_p1.png).",
        "Menu item: clock icon + 'My bet history' (opens the personal bet-history dialog).",
        "Divider line.",
        "Footer: grey 'Powered by' followed by the 'iNOUT' brand wordmark (red circular icon + bold white/red 'iNOUT' text) - this is the STUDIO/PROVIDER credit, confirming InOut Games as the maker; no separate sub-studio branding was found."
      ]
    },

    "provably_fair_dialog": {
      "type": "info",
      "page": 1,
      "frame": "info.png",
      "title": "Provably fair settings",
      "subtitle": "This game uses Provably Fair technology to determine game result",
      "content": [
        "'Next client (Your) seed:' with explanatory text 'Round result is determined form combination of server seed and first 3 bets of the round.' (verbatim, includes the source typo 'form').",
        "'Random on every game:' field labelled 'Current:' with a copyable hash value (e.g. '34c1353d8ad7efd2') and a copy-to-clipboard icon.",
        "'Next server seed SHA256:' field with a long hex hash (e.g. '3276ce64a0b3934583ef5e53783080ad31160a87fe7dce1a') and its own copy icon.",
        "Footer note: 'You can check fairness of each bet from bets history.'"
      ]
    },

    "my_bet_history_dialog": {
      "type": "info",
      "page": "2 (Classic context) / 3 (Trenball context, same dialog reused)",
      "frames": ["info_p2.png", "bet_history_two_ranges.png"],
      "title": "My bet history",
      "table_columns": ["Date", "Bet", "Mult.", "Win"],
      "row_format": "Each row: timestamp 'HH:MM DD-MM-YY', stake with a small dollar-icon prefix (e.g. '$ 2'), the settled multiplier in a small colored pill matching the history-ribbon color scheme (blue pill 'x2' for a win, dark-red/maroon or green pill 'x0' for a loss depending on which range/mode lost), the win amount with dollar-icon prefix or an em-dash '-' if nothing was won, and a small green shield-check icon on the far right (appears to indicate the bet/result was cryptographically verifiable via provably-fair).",
      "key_evidence_frame": "bet_history_two_ranges.png shows two Trenball bets placed in the SAME second (08:59 17-08-26), each $2: one settled 'x2 -> $4' (blue pill, Blue range won) and the other settled 'x0 -> -' (green pill, Green range lost) in the SAME round. This is the direct numeric proof that each range selection is its own independent stake+result, not a shared/split stake - see payout_basis.",
      "load_more_button": "'LOAD MORE' button beneath the visible rows to fetch older history (amber/gold in info_p2.png, more orange/yellow in bet_history_two_ranges.png - both are the same control, minor rendering/hover difference)."
    }
  },

  "round_cycle": {
    "classic_mode": [
      "1. WAITING phase: center of stage shows 'STARTS IN N.NN SECONDS' counting down; BET button is available (green); player can set stake via MIN/MAX/quick-amounts and optionally arm Auto Cashout.",
      "2. Clicking BET while waiting places an immediate bet for the upcoming round; the BET button becomes an amber CASHOUT button showing the live potential win once the round starts flying.",
      "3. FLIGHT phase: the plane rises, the multiplier readout counts up from x1.00 in real time; the history ribbon, Bets/Team tables and other players' win amounts update live.",
      "4. If Auto Cashout is armed, the game withdraws automatically the instant the multiplier reaches the set value; otherwise the player must click CASHOUT before the crash to lock in a win (win = stake x multiplier at the moment of cashout, e.g. win_screen_classic.png: stake $2, manual cashout at x2 -> Win $4).",
      "5. CRASH: the plane graphic is replaced by the explosion puff, the multiplier readout and the word 'CRASH' recolor per the range-color scheme, and the round's final chip is added to the history ribbon. Any bet not cashed out before this moment loses the full stake.",
      "6. Clicking BET DURING an in-flight round (i.e. while another round is already flying) queues the bet for the NEXT round instead of the current one; the button shows blue 'BETTING' / 'Cancel', and can be cancelled before the next round starts (observed directly: _trenball_bet_placed.png shows this exact treatment on the Trenball Blue button; the same blue BETTING/Cancel mechanic for Classic was verified by the TL through live interaction, matching the printed 'How to play?' text)."
    ],
    "trenball_mode": [
      "1. WAITING phase: same 'STARTS IN N.NN SECONDS' countdown; player picks one or more of the three fixed-odds range buttons (Red 1.81x / Blue 2x / Green 10x) and, per rules_p2.png item 2, may select multiple ranges in the same round, each using the shared stake field's current value as its own independent stake.",
      "2. Clicking a range button places that specific bet; a bet placed while another round is already flying is queued for the next round the same way as Classic, shown by that button switching to blue 'BETTING' / 'Cancel'.",
      "3. FLIGHT phase: identical visual flight/multiplier behavior to Classic, but payout is fully automatic - 'the withdrawal will occur automatically in the reached range' (rules_p2.png). The player does not click anything to cash out in Trenball.",
      "4. CRASH: the final multiplier determines which range(s) win. If the crash value falls in a range the player staked on, that stake is paid at the range's fixed odds (Red 1.81x / Blue 2x / Green 10x); ranges not reached, or not bet on, pay nothing. Example: win_screen_trenball.png - crash at x1.61 (Red zone) paid the Red-range bettor (+1.81x their stake, shown in the Team RED table) while a Team BLUE bettor (needs >=2x) got nothing.",
      "5. Because Blue ('2 and higher') and Green ('10 and higher') overlap per the printed rules, a crash at 10x or above should in principle pay BOTH a Blue stake and a Green stake placed in the same round - this was not directly observed in a captured round (no crash >=10x coincided with simultaneous Blue+Green stakes in testing) and is flagged as an inference from rules text, not a measured outcome."
    ]
  },

  "payout_basis": {
    "classic_mode": "Win = stake x the multiplier value at the exact moment of cashout (manual click or Auto Cashout trigger). This is a continuous, player-chosen value with no fixed tiers - proven directly by win_screen_classic.png (stake $2, cashed out at x2, Win $4) and by every row in the 'My bet history' table (all $2 stakes at 'x2' pill settle at exactly $4).",
    "trenball_mode": "PER-SELECTION basis, not a shared/combined stake. Each of the three range buttons (Red/Blue/Green) is its own independent bet at its own fixed printed odds (1.81x / 2x / 10x respectively), even though all three draw from the same visible stake-amount field. Proof: bet_history_two_ranges.png shows two DIFFERENT range bets placed by the same account in the same second, logged as two SEPARATE history rows, each with its own $2 stake and its own independent outcome (one 'x2 -> $4' win, one 'x0 -> -' loss) within the very same live round. If the stake were shared/split across ranges, both rows could not carry a full, independent $2 stake with independent multiplier pills. A round's total risked amount in Trenball is therefore the SUM of every range selected, each one settling on its own printed odds against the same final crash value.",
    "caveat": "The stated overlap between the Blue (>=2x) and Green (>=10x) ranges (see how_to_play_dialog notes) was not itself exercised by a captured crash >=10x with both ranges staked simultaneously - the per-selection independence is measured directly from bet_history_two_ranges.png, but the specific double-payout-on-overlap behavior at >=10x is taken on faith from the printed rules text alone and is not independently confirmed."
  },

  "bet_limits": {
    "min_bet": {"value": 0.12, "unit": "USD", "source": "rules_p1.png printed text AND independently confirmed by pressing the MIN button to its floor (_min_bet.png shows the stake field reading exactly '0.12')."},
    "max_bet": {"value": 200, "unit": "USD", "source": "rules_p1.png printed text AND independently confirmed by pressing the MAX button to its ceiling (_max_bet.png shows the stake field reading exactly '200')."},
    "method_caveat": "There is no manual numeric-entry field in this UI to test exceeding the limit by typing a value and getting a server rejection (confirmed absent in _bet_field_click.png) - the limits are therefore confirmed by the MIN/MAX buttons reaching a hard floor/ceiling that matches the printed rule, not by a rejected out-of-range submission.",
    "max_win": {"value": 20000, "unit": "USD", "kind": "money cap, NOT a multiplier", "source": "rules_p1.png printed text 'Max win: 20 000 USD'. No second independent confirmation was attempted (reaching this cap is not practically reproducible in a short test session)."}
  },

  "rtp": {
    "printed_in_game": false,
    "value": null,
    "evidence": "No RTP figure appears on any captured screen or dialog (top bar, hamburger menu, Game rules, How to play, Provably fair settings, My bet history all reviewed directly - none mention RTP).",
    "external_note": "An RTP figure of 95% is published on the provider's external marketing/catalog pages for this title, per the task brief - this is an EXTERNAL/catalog claim, not something the game itself displays, and is recorded here only as a provenance note, not as an in-game fact."
  },

  "special_fields": {
    "provably_fair": {"present": true, "frame": "info.png", "detail": "Client seed + next-server-seed SHA256 exchange, described in provably_fair_dialog above."},
    "autoplay": {"present": false, "note": "No auto-spin / auto-bet-series control exists anywhere in the interface (hamburger menu has no such item). The only 'auto' control is Auto Cashout, which automates the CASHOUT moment of a single already-placed Classic bet - a different mechanic, not a series of automated bets."},
    "auto_cashout": {"present": true, "default_multiplier": "2x", "step": 0.1, "control": "round '-' / value / round '+' stepper next to the Auto Cashout on/off toggle", "frame": "_autocashout_minus.png (2.0x decremented one step to 1.9x)"},
    "shared_live_rounds": {"present": true, "detail": "This is a multiplayer/shared demo - other (real or simulated) accounts' bets, stakes (in their own currencies: USD $, Euro €, Indian Rupee-style '₹'/'Rs', Nepalese Rupee 'NPR', Saudi Riyal 'SAR', and a 'P$'-prefixed currency), and win/loss outcomes are all visible in real time in the Bets / Team RED / Team BLUE tables. Round IDs and balances of our own account changed between some captures purely from continuously running rounds, independent of our own clicks."},
    "fullscreen_toggle": {"present": true, "icon": "square icon with four corner-arrows, top-right of the top bar"},
    "latency_indicator": {"present": true, "detail": "Millisecond ping value + wifi icon, bottom-right corner (e.g. '471ms', '810ms', '313ms' across different frames) - always rendered with the same reddish/salmon tint in every captured frame, so no color-coded good/bad threshold could be confirmed."}
  },

  "studio_evidence": {
    "text": "Powered by iNOUT",
    "frame": "settings.png",
    "note": "Matches the provider (InOut Games) exactly; no distinct sub-studio branding was found anywhere in the captured screens."
  },

  "accessibility_observations": {
    "screen_reader": "Control layout is stable across both modes: logo far-left; How to play / balance / fullscreen / menu far-right, in that fixed order; mode switch always centered directly above the bet panel; the bet-action button(s) are always the right-most, largest element of the bottom bar. The history ribbon, Bets/Team tables and multiplier readout are all live-updating regions that a screen reader would need to treat as polite live-regions rather than reading continuously.",
    "motor": "Primary actions (BET/CASHOUT/BETTING-Cancel/CANCEL, mode switch, range buttons) are all large rectangular targets. Stake can only be set via discrete button presses (MIN, MAX, 4 quick-amounts, auto-cashout +/- stepper) - there is no fine-motor-demanding text field to type into, which is itself a low-friction, low-precision-required design, though it also means a player cannot set an arbitrary custom stake value, only the 6 available options (MIN, MAX, $2, $3, $8, $20).",
    "color_blind": "The three-way Red/Blue/Green range-and-history color scheme is the main color-blind risk area, but every colored element carries a redundant non-color cue: history chips and the crash readout print the NUMERIC multiplier value as text regardless of chip color; the three Trenball buttons are additionally distinguished by their printed odds text ('Payout: 1.81x' / '2x' / '10x') and by fixed left-to-right ORDER (Red always left, Blue always middle, Green always right); bet-history pills likewise show the numeric multiplier as text inside the color pill. Button STATE (BET/CASHOUT/BETTING/CANCEL) is redundantly conveyed via distinct printed words, not color alone. Toggle switches (Sound/Music/Auto Cashout) use knob POSITION (left/right) as a non-color cue in addition to track color.",
    "deaf_hard_of_hearing": "No information observed to be conveyed by audio alone; Sound and Music are separate, independently toggleable and both default OFF, and all round-state information (multiplier, crash, win amount, countdown) is rendered as on-screen text/graphics."
  },

  "not_captured": [
    {
      "claim": "No RTP value is printed anywhere in the game UI.",
      "methods": ["pixels: every dialog screenshot (settings.png, rules_p1.png, rules_p2.png, info.png, info_p2.png, bet_history_two_ranges.png) reviewed directly with vision - no RTP text found on any of them."]
    },
    {
      "claim": "There is no autoplay/auto-bet-series feature.",
      "methods": ["pixels: hamburger menu (settings.png) fully enumerated - only Sound, Music, Provably fair settings, Game rules, My bet history are present; no autoplay entry."]
    },
    {
      "claim": "No manual numeric stake-entry field exists.",
      "methods": ["pixels: _bet_field_click.png (a deliberate click on the stake-value text) shows no input caret, keyboard, or editable-field styling appearing - the field remains a static readout bounded by MIN/MAX buttons."]
    }
  ],

  "unreadable_or_uncertain": [
    "Whether a dedicated 'Team GREEN' table column appears in Trenball mode once the Green range has active bets - not observed in any captured frame (Green never had a live bettor at capture time), so its exact table layout/position relative to Team RED / Team BLUE is uncertain.",
    "Exact numeric threshold, if any, that recolors the top-right latency badge - it showed the same reddish tint at 172ms, 313ms, 471ms, 614ms and 810ms in different frames, so a color-coded good/medium/bad threshold could not be confirmed or ruled out from the available captures.",
    "The double-payout behavior implied by the printed overlap of the Blue ('2 and higher') and Green ('10 and higher') Trenball ranges at crash values >=10x - taken from rules text only, not observed in a captured round.",
    "Whether the Classic-mode BETTING/blue/Cancel queued-bet button state (used here for Trenball evidence in _trenball_bet_placed.png) looks pixel-identical in Classic mode - this specific behavior for Classic was confirmed through live interaction by the TL rather than through a dedicated Classic-mode screenshot of that exact button state.",
    "5-of-a-kind / deeper paytable-style breakdowns do not apply to this game (there are no reel symbols), so none are reported - this is a structural property of a crash game, not a gap in documentation."
  ]
}