Skip to main content
Formal Specification

Oina (Romanian Traditional Bat-and-Ball Sport) — Formal Specification

Romania · ball-team · Confidence: high

← Back to game page

Implementation Suitability

Suitability: engine-readyFidelity: discretizedGap-fills: 4
# Oină — AI-optimized specification ## General idea A discrete, two-team asymmetric bat-and-ball territory game played on a 2D pitch with specialized running corridors. A batting agent hits an ascending ball to achieve depth and boundary clearances (scoring direct points), then executes corridor runs between safe zones while defending fielders pass and throw the ball to strike running agents for defensive points. ## Formal model - **Abstraction taken:** Field modeled as a 2D grid (L×W, e.g. 70×32 cells). Batting launch is parameterized by angle and force; corridor navigation is modeled as discrete movement along forward (y=0..5) and return (y=27..32) lanes; defensive throws are resolved via distance-dependent hit probabilities. - **Player/agent count:** 2 teams (Team 0 and Team 1), K agents per team (K∈[8..11], default K=8). - **Turn model:** 2 halves. Each half comprises K consecutive batting rotations and concurrent corridor running ticks. ## Formal rules R1. State tracking: `team_scores` ∈ℕ2, `current_half` ∈{1,2}, `active_batter_idx` ∈[0..K−1]. R2. Batting Phase: - Active batter selects striking power F∈[1..5] and vertical loft angle θ∈[15∘..60∘]. - Ball landing coordinate (xball,yball): - If xball≥70 (Back Line Clearance): Batting team scores 2 points (if in-flight) or 1 point (if bounced). - If xball<70 and within lateral boundaries (0≤y≤32): 0 direct points; ball is in play. - If outside lateral boundaries: Foul (0 points). R3. Fly Catch Defense: - If a fielder occupies a cell within radius r≤2 of the airborne ball's landing point: - [gap-fill] Catch probability Pcatch=0.70×skillfielder. - If catch succeeds: Fielding team scores 2 points (`team_scores[fielding] += 2`). R4. Corridor Running & Tag Defense: - Batters who hit the ball enter the forward corridor (`status = running_forward`). - On each tick t, running agents advance along their corridor (1 to 2 cells per tick). - Defending fielders can pass the ball (instantaneous if distance ≤10) and execute `throw_at_runner(runner_id)`: - [gap-fill] Hit probability: Phit=max⁡(0.10,0.85−0.08×distance+0.10×skillF−0.10×agilityR). - If hit: Fielding team scores 2 points (`team_scores[fielding] += 2`). The runner continues moving (no elimination). R5. Safe Zones: - Back Zone (x≥60): Safe from throws. Runners may rest before entering the return corridor. - Home Base (x≤0 on return): Completing the return corridor scores 0 extra points but secures safe arrival. R6. Half Transition & Win Condition: - After all K batters complete their turn and runs in Half 1, teams swap roles (B↔F) for Half 2. - The team with the highest aggregate score after both halves wins the match. R7. [gap-fill] Inning Step Ceiling: Maximum 500 ticks per half. If tick 500 expires, any runners remaining in the corridor are automatically declared safe. ## Edge cases - Tie at the end condition: If aggregate scores are tied after 2 halves, [gap-fill] a 3-batter sudden-death shootout half resolves the winner. - A player with no legal move: Waiting / advancing 1 cell is always legal for corridor runners. - Repetition / cycles: Bounded — corridor movement is unidirectional (forward corridor moves strictly +x, return corridor moves strictly −x). - Simultaneous claims on the same resource or position: Runners may share corridor cells; multiple fielders can participate in relay passes. - Player elimination mid-round; turn order repair: No eliminations (runners take hits for opponent points without removal); lineup rotation is strictly preserved. - Resource exhaustion: Conserved half and batter counters. - Termination guarantee: Monotonic progress along corridors and finite K-batter lineup guarantee termination per half. ## State representation - Persistent state: - `scores`: Array of 2 integers `[score_0, score_1]`. - `half`: 1 or 2. - `batter_index`: 0..K−1. - `runners`: Array of K structs: `[x, y, status, corridor_phase]`. - `fielders`: Array of K structs: `[x, y, has_ball]`. - Observable information: Fully observable. ## Action space - Batter: `strike(power, angle)`. - Runner: `advance(speed)` (speed∈{1,2}). - Fielder: `move(dx, dy)`, `pass_ball(target_fielder_id)`, `throw_at_runner(target_runner_id)`. ## Playability notes - Single-player-vs-AI: Excellent team tactical simulation. Human can control the batter and runner timing while managing defensive field coverage. - Group games (n>4): Parameterized for K=8 or K=11 agents per team. - Physical-skill games: Physical batting power and dodging agility mapped to trajectory mechanics and stochastic hit matrices. - What is lost: Physical sound of the wooden bat impact, sting of the leather ball, and pastoral field turf conditions. ## Implementation hints - Implement as a 2-phase simultaneous multi-agent environment. - Fielder AI heuristic: prioritize relaying the ball to the fielder adjacent to the corridor runner closest to the safe zone.

Download as JSON

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

Download JSON
Cite this page

Oina (Romanian Traditional Bat-and-Ball Sport) (Romania). (n.d.). Games of Countries. https://gamesofcountries.com/games/ro-romania/oina

@misc{gamesofcountries-ro-romania-oina,
  title = {Oina (Romanian Traditional Bat-and-Ball Sport) (Romania)},
  year = {n.d.},
  publisher = {Games of Countries},
  url = {https://gamesofcountries.com/games/ro-romania/oina}
}