OUT OR NOT?

Cinevva's analyzer read this game's design doc and its source, then wrote the brief below. "Make your own" hands it to the game creator as your opening message, so you start from a real spec rather than a one-line idea.

Create a playable browser game titled “OUT OR NOT?”: a broadcast-style 3D cricket LBW umpire simulator. Use a full-screen Three.js-like 3D scene with a cinematic perspective camera, dark blue-green stadium atmosphere, fog, soft shadows, and a low-poly/stylized professional cricket ground. The scene should contain a circular grass stadium floor, a narrow tan rectangular cricket pitch running toward and away from camera, white crease markings near both ends, three simplified players made from capsule-like bodies (a blue-clad bowler at the far end, a white-clad batsman at the near end, and a dark-clad umpire standing near the middle), a wooden bat beside the batsman, white stumps and gold bails at both ends, red cricket ball, and distant blocky spectator stands and tall floodlights arranged around the ground. Light the scene with cool ambient light plus warm directional sunlight and a subtle blue rim light.

The game loop is: show a start overlay first, then begin a delivery when the player presses START MATCH. The start panel is dark translucent blue-black with a yellow kicker reading “BROADCAST UMPIRE SIMULATOR,” a large two-line title “OUT OR NOT?” with “OR” in yellow, explanatory copy about reading line, length and impact and making LBW decisions from a cinematic broadcast view, and a wide yellow START MATCH button. Behind it, show the live HUD: top-left brand “OUT OR NOT?” (with OR yellow); top-right stat cards for SCORE, STREAK, ACCURACY, and OVER, initially 0, 0, 100%, and 0.1. Center-top status text says “WATCH THE DELIVERY.” At the bottom are two large buttons, red “OUT” and teal “NOT OUT,” initially disabled/dimmed while the ball is moving.

Each delivery lasts about 2.6 seconds. Spawn a red ball at the bowler’s end and animate it down the pitch toward the batsman, with a faint short peach trail. The ball follows a slightly varied trajectory: lateral line movement, swing, optional spin/turn, and a visible bounce arc. Vary the randomly selected bowling style among RIGHT-ARM FAST, RIGHT-ARM SPIN, LEFT-ARM FAST, and LEFT-ARM SPIN. Fast deliveries travel at roughly 28 km/h plus difficulty scaling, spin deliveries around 21 km/h plus scaling, with displayed speed randomized slightly. Randomize line, length, swing, turn, bounce, and whether the ball misses. The ball and camera should provide cinematic broadcast views selected randomly from three positions while it travels; after impact, move to a closer batsman/pitch view. The bowler subtly rocks/rotates during the delivery and the batsman subtly reacts near the end.

After the ball reaches the impact phase, stop the ball presentation and enable the two decision buttons. Change the center-top status to “MAKE YOUR CALL.” Change the hint to “Tap OUT or NOT OUT,” or, for a borderline delivery, “BORDERLINE DRS CHALLENGE.” Show a brief center toast such as “DECIDE” or “CLOSE CALL.” The player must choose OUT or NOT OUT. Generate the hidden physics verdict from the delivery: normally it is OUT only when the impact is sufficiently in line with the wicket corridor and low enough, subject to a probability check; misses always resolve to NOT OUT. Borderline deliveries occur with increasing probability as overs progress and can award extra points.

Once the player calls, disable both buttons and show a dark blurred translucent Decision Review System overlay centered over the 3D scene. The overlay should contain a kicker reading “DECISION REVIEW SYSTEM,” or “SPECIAL DRS CHALLENGE” for borderline balls; a title such as “YOU CALLED OUT” or “YOU CALLED NOT OUT”; a compact two-column review grid showing PITCHING (IN LINE or OUTSIDE LEG), IMPACT (IN LINE or OUTSIDE LEG), and WICKETS (HITTING or MISSING); a large color-coded final verdict, red/pink for OUT and mint green for NOT OUT; a small replay line containing bowling style, speed in km/h, and whether the call matched the physics; and a full-width NEXT DELIVERY button. Also display a brief center toast “CORRECT” in mint green or “WRONG CALL” in pink.

Scoring and HUD rules: every correct call increments streak and adds 10 points, plus 10 for borderline, plus streak bonuses at 3, 5, and 10; every third consecutive correct call adds another 5. A wrong call resets streak and subtracts 8 points but never below zero. Track total calls, correct calls, best streak, and show accuracy as rounded correct/total percent (100% before any calls). There are six balls per over: advance the ball counter after NEXT DELIVERY; after ball six increment the over number, reset the ball number to 1, and briefly toast “OVER N COMPLETE.” Start at over 0, ball 1. The DRS overlay’s NEXT DELIVERY button closes it and starts another randomized delivery.

Use responsive full-screen UI layered over the canvas. The visual style is premium sports broadcast: dark navy/charcoal translucent panels, thin subtle borders, rounded corners, backdrop blur, uppercase letter-spaced labels, bold white typography, yellow accent #f4c95d, red OUT controls, teal NOT OUT controls, and mint success feedback. Keep the buttons touch-friendly and disable them during delivery/review. Do not add unrelated game modes, extra characters, weapons, menus, or gameplay systems; the core experience is watching each 3D cricket delivery, making one binary LBW call, and inspecting the physics-style DRS verdict.