Skip to main content
Formal Specification

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

Moldova · ball-team · Confidence: medium

← Back to game page

Implementation Suitability

Suitability: adaptation-requiredFidelity: discretizedGap-fills: 2
# Oina moldoveneasca (Oina moldovenească) — AI-optimized specification ## General idea The national Moldovan bat-and-ball team field sport (*Oina de toloacă* or *Țurca mare*). Two 11-player teams alternate roles across two innings: the Batting Team drives a leather-wrapped horsehair ball into a 70m×32m pasture field with conical ash-wood bats and sprints through two flanked running corridors to the back line and home, while defending fielders catch fly balls and throw accurate tag strikes (*ochirea*) at running batters. ## Formal model - **Field Coordinate Geometry:** 70m×32m rectangular plane partitioned into: - Batting Zone: x∈[0,32],y∈[0,5]. - Go Corridor (*Culoarul de ducere*): x∈[27,32],y∈[5,65]. - Back Line Safe Haven (*Linia de fund*): x∈[0,32],y∈[65,70]. - Return Corridor (*Culoarul de întoarcere*): x∈[0,5],y∈[5,65]. - Central Infield (Fielding Territory): x∈[5,27],y∈[5,65]. - **Player/agent count:** 2 teams of M players each (M∈[8,11]): Batting Team 𝒯bat, Fielding Team 𝒯field. - **Turn model:** 2 innings (halves) of sequential batting turns with continuous ticked spatial ball physics and corridor runner tracking. ## Formal rules R1. Inning Structure & Match Schedule: - Match consists of 2 equal innings. In Inning 1, Team A bats and Team B fields; in Inning 2, roles swap. - Each inning concludes when all M batters have taken their turn at bat and completed or forfeited their corridor runs. - Match scores: `team_points[Team_A] = 0`, `team_points[Team_B] = 0`. R2. Pitching & Batting Mechanics: - A designated server tosses the horsehair ball vertically above the batting plate (x=16,y=2.5). - Active batter Bk submits `strike_ball(elevation_angle, azimuth, impact_force)`. - 3D ball trajectory is simulated across gravity and aerodynamic drag. - **Batting Scoring:** - Ball lands past the 30m line (y≥30.0): `team_points[T_bat] += 1`. - Ball driven past the Back Line (y≥65.0): `team_points[T_bat] += 2`. - Foul hit (out of bounds x∉[0,32] or y<5.0): 0 batting points. R3. Mid-Air Catching (*Prindere din zbor*): - If a fielder catches the batted ball before it touches the turf: - `team_points[T_field] += 2`. - Ball is immediately live for throwing at corridor runners. R4. Corridor Running (*Ducerea și întoarcerea*): - After striking, batter enters the **Go Corridor** (x∈[27,32]) sprinting toward the Back Line (y=65.0). - At the Back Line, runners are safe (`is_safe = true`) and may wait for subsequent hits before committing to the **Return Corridor** (x∈[0,5]). - Completing a full circuit back to the Batting Zone (y≤5.0) untouched scores `team_points[T_bat] += 1`. R5. Fielding & Tagging Throws (*Ochirea*): - Fielders recover the ball and may execute `pass_ball(target_fielder_id)` to set up target angles. - Fielder submits `throw_tag_runner(target_runner_id, throw_velocity)`. - **Tag Collision:** - If ball intersects runner torso/limbs while inside an active corridor: `team_points[T_field] += 2`. - Runner may submit `palm_deflect()`: Successful palm block negates the strike [gap-fill]. - Head strikes are illegal fouls: awarding the runner an immediate free safe pass. R6. Match Victory: - After both innings conclude, the team with the highest cumulative point total is declared winner. ## Edge cases - Tie at the end condition: If aggregate points are tied after 2 innings, a 1-inning sudden-death 3-batter mini-half determines the victor [gap-fill]. - A player with no legal move: Inactive runners wait on the Back Line; batters take turns in fixed rotation. - Repetition / cycles: Each inning strictly exhausts the finite batting rotation of M players. - Simultaneous claims on the same position: Multiple runners may occupy the Back Line safe zone; maximum 2 runners may occupy a running corridor concurrently. - Elimination mid-round and turn-order repair: Runners are not eliminated when hit; they complete their run while conceding 2 points to the defense. - Resource exhaustion: Exactly 1 ball in play. - Termination guarantee: Monotonic progression through 2×M batting turns guarantees match completion in finite time (T≤1200 ticks). ## State representation - Persistent state: - `inning`: Integer ∈[1,2]. - `team_points`: Map of Team → integer. - `batting_order`: List of Player IDs. - `active_batter_idx`: Integer ∈[0,M−1]. - Per-tick ephemeral state: - `ball_pos`: 3D coordinates (x,y,z). - `ball_velocity`: 3D vector (vx,vy,vz). - `ball_carrier_id`: Agent ID or null. - `runner_states`: Map of Runner ID →{AT_BAT,IN_GO_CORRIDOR,AT_BACK_LINE,IN_RETURN_CORRIDOR,HOME}. - `fielder_positions`: Map of Fielder ID →(x,y). - Observable information: Fully observable continuous player coordinates, ball trajectory, and match scoreboard. ## Action space - `strike_ball(angle, azimuth, force)`: Batter impact execution. - `sprint_corridor(velocity)`: Runner forward advance. - `palm_deflect()`: Runner defensive hand block. - `pass_ball(target_id)`: Fielder relay throw. - `throw_tag_runner(runner_id, force)`: Fielder tagging throw. ## Playability notes - Single-player-vs-AI: Superb strategic bat-and-ball sports game. Batting tests projectile timing and directional power; fielding requires rapid spatial positioning and relay pass anticipation; corridor running is a tense gauntlet of dodges and palm parries. - Group reduction: Reducible to 2 teams of 4 players each on a scaled 40m×20m pitch. - Physical-skill games: Ash-bat sweet spot elasticity, aerodynamic drift of seamed leather horsehair balls, and dodging 90 km/h fielder throws while sprinting full-speed in corridors are modeled via 3D ballistics and hitbox collision checks. - What is lost: The crack of ash wood echoing across the village pasture, the sting of a dense wool ball on a runner's back, and the communal roar of spectators along the touchlines. ## Implementation hints 3D kinematic ball physics engine layered over a 2D zoned corridor collision grid. First milestone: build batting flight trajectory and boundary point calculation before implementing the multi-agent fielder relay AI and corridor tag collision checks.

Download as JSON

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

Download JSON
Cite this page

Moldovan Oina (Traditional Bat-and-Ball Field Sport) (Moldova). (n.d.). Games of Countries. https://gamesofcountries.com/games/md-moldova/oina-moldoveneasca

@misc{gamesofcountries-md-moldova-oina-moldoveneasca,
  title = {Moldovan Oina (Traditional Bat-and-Ball Field Sport) (Moldova)},
  year = {n.d.},
  publisher = {Games of Countries},
  url = {https://gamesofcountries.com/games/md-moldova/oina-moldoveneasca}
}