Formal Specification
Long Ball — Formal Specification
Åland · ball-team · Confidence: low
← Back to game pageImplementation Suitability
Suitability: adaptation-requiredFidelity: discretizedGap-fills: 5
# Långboll — AI-optimized specification
## General idea
A traditional Åland and Scandinavian bat-and-ball team fielding game where an "in-team" (*inlag*) bats and runs between a home base and an outfield base (*uteboet*), while an "out-team" (*utlag*) fields the ball. Fielders attempt to catch batted balls on the fly (*lyra*) or hit sprinting runners with the thrown ball (*bränna* / *kulla*) to force an immediate role reversal and scramble for home base safety.
## Formal model
- **Abstraction taken:** The continuous open-field running, ball flight physics, and pelting/tagging are discretized into a 1D/2D field model with three discrete zones: Home Base (), Open Field corridor (, length ticks), and Out Base (). [gap-fill] Batting trajectories, fielding catches, and throwing-tag accuracy are resolved via discrete stochastic success probabilities.
- **Player/agent count:** 2 teams of agents each (, commonly 8).
- **Turn model:** Two-level turn structure: sequential batting attempts within an inning, with simultaneous movement/fielding ticks while runners traverse the open field.
## Formal rules
R1. Setup: Team A starts as Inlag (batting/running), Team B starts as Utlag (fielding). The game is played for innings (default ) or a fixed number of side-swaps.
R2. Batting phase:
- The active batter receives a tossed pitch and chooses a swing direction/power.
- A hit generates an outfield landing coordinate and flight time .
- If a batter fails 3 consecutive swings, they must move to the runner queue at without scoring.
R3. Catch on the fly (*lyra*): If a fielder reaches the ball landing zone before flight time expires, a catch check is evaluated (). A successful catch triggers an immediate **Side Swap** (Inlag becomes Utlag and vice-versa).
R4. Base running:
- When a legal hit occurs, any runners at may choose to sprint toward , and runners at may sprint toward .
- Traversing requires movement ticks (e.g. 3 ticks per sprint).
- Each runner who successfully travels scores 1 run (*varv*) for the batting team.
R5. Pelting / Tagging (*bränning*):
- If fielders retrieve the ball while runners are in , the fielder holding the ball can attempt a throw at a runner within range.
- [gap-fill] Throw hit probability: .
- If a runner is struck by the ball in , an immediate **Scramble Swap** occurs: the fielder drops the ball, all former fielders sprint to , while former runners attempt to recover the ball and tag a former fielder before they reach .
R6. [gap-fill] Inning change: An inning half-turn ends upon a completed side swap.
R7. Win condition: The team with the highest cumulative run score after completed innings wins the match. [gap-fill] Ties are resolved by 1 additional sudden-death half-inning per team.
## Edge cases
- Tie at the end condition: Resolved by the sudden-death extra inning in R7.
- A player with no legal move: Not applicable — batters must swing or take strike; fielders and runners always have legal movement/throwing actions.
- Repetition / cycles: Bounded by the fixed number of innings and fixed batter rotation.
- Simultaneous claims on the same resource or position: Bases and accommodate unlimited simultaneous safe runners.
- Player elimination mid-round; turn order repair: No player elimination; batting order is a fixed cyclic queue that persists across side swaps.
- Resource exhaustion: Ball is permanent; running bases are non-depleting.
- Termination guarantee: Provably terminates because the number of innings is strictly finite, and each inning contains a bounded number of at-bats.
## State representation
- Persistent state: Inning count , current inning index , scores for Team A and Team B, current role assignment (which team is Inlag).
- Per-inning state: Batting order pointer per team, positions of all agents (, , or position in ), ball position and velocity.
- Per-tick ephemeral state: Active runner movements, fielder ball passes, throw attempt outcomes.
- Observable information: Fully observable — all agent positions, ball coordinates, scores, and batter queues are public.
## Action space
- `batter_swing(power, angle)`: Swing at pitched ball.
- `run_sprint(destination)`: Move runner from safe base into open field corridor toward target base.
- `stay_safe()`: Remain in base safe zone.
- `field_move(dx, dy)`: Move fielder toward ball landing spot.
- `throw_tag(target_runner_id)`: Fielder throws ball to tag runner in open field.
- `pass_ball(teammate_id)`: Pass ball to adjacent fielder.
## Playability notes
- Single-player-vs-AI: Needs adaptation — 1 human player controls the batting swing and team running commands (or pitcher/fielder actions) while AI coordinates team positioning.
- Group games (n>4): Naturally 2 teams of 6–12 agents; [gap-fill] reduction to 2 agents (1 batter/runner vs. 1 pitcher/fielder) reduces the tactical depth but preserves the hit-run-tag loop.
- Physical-skill games: Batting accuracy and throwing speed are parameterized by agent skill ratings.
- What is lost: The physical sensation of striking a leather ball with a solid wooden paddle, dirt scrambling, and dodging flying balls.
## Implementation hints
Moderate complexity due to simultaneous fielding and base-running transitions. First milestone: implement the discrete 3-zone movement graph with deterministic catches and tags to verify the side-swap state transition before introducing full continuous fielding coordinates.
Download as JSON
Download the full game corpus entry for this game as structured JSON.
Download JSONCite this page
Long Ball (Åland). (n.d.). Games of Countries. https://gamesofcountries.com/games/ax-aland/langboll
@misc{gamesofcountries-ax-aland-langboll,
title = {Long Ball (Åland)},
year = {n.d.},
publisher = {Games of Countries},
url = {https://gamesofcountries.com/games/ax-aland/langboll}
}