Skip to main content
Formal Specification

Finnish baseball — Formal Specification

Finland · ball-team · Confidence: high

← Back to game page

Implementation Suitability

Suitability: engine-readyFidelity: discretizedGap-fills: 2
# Pesäpallo — AI-optimized specification ## General idea Finland's national bat-and-ball sport. Unlike American baseball or cricket, the ball is pitched completely vertically over a home plate directly in front of the batter, granting the offense high tactical control over ball placement (grounders, line drives, drop shots). Runners advance along a zigzag base path (Home → Base 1 → Base 2 → Base 3 → Home). Defensive play relies on throwing the ball to bases before the runner arrives to record force outs (*palo*) without needing physical tags. ## Formal model - **Abstraction taken:** The continuous zigzag playing field is modeled as a 4-node directed graph: Home→Base1→Base2→Base3→Home. Physical ball flight, vertical pitching legality, batting trajectory, and fielding throw times are abstracted into parameterized stochastic resolvers. - **Player/agent count:** 2 teams of 9 active fielders, with 9 regular batters and up to 3 joker batters per team (TA,TB). - **Turn model:** Inning-based structure with discrete at-bat cycles within each half-inning. ## Formal rules R1. **Match Structure:** - A regulation match consists of 2 periods (*jakso*), each comprising 2 innings (*vuoropari*). - Each inning has two half-innings: Team A bats (offense) while Team B fields (defense), then roles swap. R2. **Vertical Pitch & Strike Count:** - The fielding Pitcher (*lukkari*) delivers a vertical pitch at home plate. - The pitch is either `Legal` or `Balk/Fault`. [gap-fill] 2 consecutive pitching balks award the batting team a free base advance for their lead runner. - The batter is allocated up to 3 swings (*lyönti*) per at-bat. - The batter may take strikes 1 and 2 tactically to signal base runners or advance without running. On strike 3, the hit must be fair, or the batter is out/wounded. R3. **Fair Hit & Base Advancement:** - A fair batted ball enters play. The batter drops the bat and runs to Base1. - Runners on bases advance sequentially: Base1→Base2→Base3→Home. - **Home Run (*Kunnari*):** If a batter reaches Base3 on their own hit without being put out, they score 1 run and remain on Base3 as an active runner. - **Run (*Juoksu*):** A runner touching home plate safely before the defense secures the ball at home scores 1 run. R4. **Defense & Out Mechanics:** - **Force Out (*Palo*):** A runner is out if a fielder in possession of the ball touches the target base before the advancing runner arrives. - **Fly Catch (*Koppi*):** If a batted ball is caught in the air before hitting the ground, all runners attempting to advance must scramble back to their origin base; if the ball reaches the base first, they are out. - **Wound (*Haavoittuminen*):** If a runner fails to advance on a third strike or is forced out of an advance without incurring a formal defensive burn, the runner is "wounded" and returns to the bench with no out recorded against the 3-out limit. - When 3 outs are accumulated, the half-inning ends immediately. R5. **Match Resolution & Super-Inning:** - Each period is scored independently (period winner = team with more runs in that period; 1 period point). - If periods end tied (1–1 or two drawn periods), a decisive Super-Inning (*Supervuoropari*) of 1 inning is played. - [gap-fill] If still tied after the Super-Inning, a 5-pair shootout (*Kotiutuskilpailu*) is conducted (5 batters attempt to drive 5 runners home from 3rd base). ## Edge cases - **Tie at the end condition:** Handled strictly by R5 (Super-Inning, followed by 5-pair Kotiutuskilpailu shootout). - **A player with no legal move:** Batters choose between swing types or taking the pitch; fielders choose throw targets; base runners choose advance/hold. A valid choice always exists. - **Repetition / cycles:** Impossible — each half-inning terminates strictly upon recording 3 outs or exhausting the batting lineup without bases occupied. - **Simultaneous claims on the same resource or position:** Only 1 runner may occupy any individual base at a time; trailing runners are forced to advance or hold, and force outs resolve deterministically based on ball arrival time vs runner arrival time. - **Player elimination mid-round; turn order repair:** When a runner is put out or wounded, they leave the field and return to the batting bench. The batting lineup order remains invariant. - **Resource exhaustion (pieces, tokens, space, time):** Fixed team rosters and discrete 4-node base graph. - **Termination guarantee: why the game provably ends:** Guaranteed by fixed inning limits, the 3-out half-inning cap, and the definitive shootout tie-breaker. ## State representation - **Persistent state:** Period index ∈{1,2}; inning index ∈{1,2}; period scores (S1,S2); period point tallies (P1,P2); out counter O∈[0,2]; batting lineup index. - **Per-at-bat state:** Base occupancy map (Base 1, Base 2, Base 3 → runner ID / empty); strike counter S∈[0,2]; pitch type. - **Per-hit ephemeral state:** Batted ball placement vector; fielding retrieval and relay times; runner transit times. - **Observable information:** Fully observable game state. ## Action space - `pitch_action(type, height)`: (Pitcher only). - `bat_action(swing_number, hit_type, target_direction)`: (Active batter). - `runner_decision(runner_id, decision)`: where `decision` ∈{advance,hold,scramble_back}. - `fielder_throw(target_base)`: (Fielding team). ## Playability notes - **Single-player-vs-AI:** Highly playable as a managerial/tactical game. The user commands offensive signs (bunting, squeeze plays, sacrifice advances) or defensive pitch calls and outfield positioning against an AI manager. - **Group games (n>4):** Team sport (9 vs 9) reduces naturally to a 2-agent game: Offensive Manager vs Defensive Manager. - **Physical-skill games:** Vertical batting and fielding throws are modeled via calibrated multivariate distributions mapping hit placement to fielding retrieval delays. - **What is lost in the adaptation:** The physical crack of the carbon-fiber bat, the sprint sliding on gravel/turf, and the pitcher's rapid psychological feints. ## Implementation hints - Implement base running as a discrete time-arrival race: Δt=tball_arrival−trunner_arrival. If Δt<0⟹Out; else ⟹Safe. - Branching factor: Modest at the tactical level: ≈6 hit choices ×23 runner choices = 48 action combinations per pitch. - Suggested first milestone: Implement a single half-inning with 3 batters, the 4-node base path, and force-out logic, verifying out accumulation and 3-out side switching.

Download as JSON

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

Download JSON
Cite this page

Finnish baseball (Finland). (n.d.). Games of Countries. https://gamesofcountries.com/games/fi-finland/pesapallo

@misc{gamesofcountries-fi-finland-pesapallo,
  title = {Finnish baseball (Finland)},
  year = {n.d.},
  publisher = {Games of Countries},
  url = {https://gamesofcountries.com/games/fi-finland/pesapallo}
}