Skip to main content
Formal Specification

Dudes (Street Tip-Cat) — Formal Specification

Israel · stick-team · Confidence: high

← Back to game page

Implementation Suitability

Suitability: adaptation-requiredFidelity: discretizedGap-fills: 2
# Dudes — AI-optimized specification ## General idea Dudes is a competitive team sports game of physical precision and risk estimation. A batter performs a two-stage manual strike: tapping a pointed peg to make it rotate vertically, and striking it mid-air to maximize horizontal flight. The game-theoretic depth lies in the "Distance Estimation" phase, where the batter must estimate the flight distance in discrete units (bat-lengths); overestimating results in an immediate out, while underestimating yields sub-optimal points. ## Formal model - **Abstraction taken:** The continuous physical acts of tapping, flipping, and hitting are collapsed into a dual-stage stochastic system. Flight distance Dflight is measured along a 1D corridor of length 100 meters. The "Distance Estimation" phase is modeled as a betting round against a physical threshold. - **Player/agent count:** Two teams of 3 players each (Team A batting, Team B fielding). - **Turn model:** Strictly sequential innings. Team A bats in order, then Team B. ## Formal rules R1. **The Batting Sequence:** Each batter on the active team stands at x=0 (Home) and executes `attempt_batting()`. R2. **Two-Stage Mechanical Resolution:** - **Step 1: The Flip:** The batter attempts to flip the peg. Success rate is: P(flip)=Dexterity_Skill(agent) - **Step 2: The Strike:** If the flip succeeds, the batter swings. Success rate is: P(strike)=Eye_Hand_Coordination(agent) - If either step fails, the attempt is logged as a miss. The player has up to 3 attempts per turn. Failing 3 times results in an "out" (elimination). R3. **Flight Trajectory & Catching:** - On a successful strike, the flight distance is calculated: Dflight=Power_Factor(agent)×50×(1+ϵdist) meters where ϵdist∼𝒩(0,0.1). - The fielding team can attempt a `catch_peg()` action: P(catch)=0.05+0.01×Flight_Duration(Dflight) - If the catch check succeeds, the batter is immediately out, and no points are scored. R4. **The Estimation Round:** - If the peg lands uncaught at Dflight, the batter must submit an estimate E∈ℕ representing distance in "bat-lengths" (where 1 bat-length = 0.5 meters). - The fielding team can select an action: `accept()` or `challenge()`. - **Resolution of Challenge:** - If the fielding team selects `accept()`, the batter's team immediately receives E points. - If the fielding team selects `challenge()`, the actual distance Dbats=Dflight/0.5 is measured. - [gap-fill] If E≤Dbats, the estimate is validated: the batter's team receives E points and the batter remains active. - If E>Dbats (overestimate), the attempt is invalidated: the batter's team receives 0 points and the batter is declared out. R5. **Win Condition:** After 3 complete innings (where each team has batted fully), the team with the highest cumulative points wins the match. ## Edge cases - **Tie at the end condition:** If there is a tie, the team with the fewer total outs across the 3 innings wins the tiebreaker. - **A player with no legal move:** Not applicable; batters can always attempt to hit the peg. - **Repetition / cycles:** Because innings have a strict maximum count (3 innings) and each player's turn terminates after either scoring or accumulating 3 outs, the game is mathematically guaranteed to terminate. - **Simultaneous claims on the same resource:** Not applicable. - **Player elimination mid-round:** Once a batter is declared out, they are removed from the active slot, and the next batter in the queue is spawned. - **Resource exhaustion:** Not applicable. - **Termination guarantee:** Guaranteed by the finite inning limit and structured player rotation. ## State representation - **Persistent state:** - `team_scores`: Map of `team_id` to integer. - `active_team_id`: Integer. - `active_batter_index`: Integer. - `outs_count`: Integer. - `inning_count`: Integer. - **Per-turn ephemeral state:** - `flight_distance`: Float (meters). - `batter_estimate`: Integer. ## Action space - `attempt_batting()`: Execute the flip-and-strike sequence. Precondition: player is active batter and has remaining attempts. - `submit_estimate(E)`: Submit distance guess. Precondition: ball landed uncaught on the current turn. - `respond_to_estimate(action)`: Fielder team response (`accept` or `challenge`). ## Playability notes - **Single-player-vs-AI:** Highly playable. The user clicks to swing (rhythm timing), and then uses an on-screen dial to estimate the distance based on visual grid landmarks. AI fielders analyze the user's past estimation biases to decide whether to challenge. - **Group games (n>4):** Standard team rotation. - **Physical-skill games:** [gap-fill] Hand-eye reflexes and depth perception are modeled as quick-time coordinate clicks and risk-estimation algorithms. - **What is lost in the adaptation:** The physical wind resistance, the danger of being hit by a flying wooden spike, and the manual whittling of the sticks are lost. ## Implementation hints - Implement the sequential batting and inning-swapping state machine. - Write the distance calculation and the stochastic catch resolver. - Program the estimation betting logic with correct score updates on challenges. - Design an AI batter that calculates the optimal estimate E to maximize expected score: E∗=arg⁡maxE⁡[P(accept)×E+P(challenge)×E×𝕀(E≤Dbats)]

Download as JSON

Download the full game corpus entry for this game as structured JSON.

Download JSON
Cite this page

Dudes (Street Tip-Cat) (Israel). (n.d.). Games of Countries. https://gamesofcountries.com/games/il-israel/dudes

@misc{gamesofcountries-il-israel-dudes,
  title = {Dudes (Street Tip-Cat) (Israel)},
  year = {n.d.},
  publisher = {Games of Countries},
  url = {https://gamesofcountries.com/games/il-israel/dudes}
}