Formal Specification
Burnball (Swedish rounders) — Formal Specification
Sweden · ball-team · Confidence: high
← Back to game pageImplementation Suitability
Suitability: adaptation-requiredFidelity: discretizedGap-fills: 7
# Brännboll — AI-optimized specification
## General idea
A traditional Nordic bat-and-ball team game where the batting team (*innelaget*) self-tosses and strikes a ball into an open sector and runs around four bases, while the fielding team (*utelaget*) catches the ball and relays it to a designated burner (*brännare*) at the burning plate. When the burner stomps the plate and announces "Bränd!", any baserunners caught in motion between bases are burned, forfeiting ground and conceding points. Both teams alternate roles, and the highest cumulative score across both halves wins.
## Formal model
- **Abstraction taken:** The continuous 3D aerodynamics of ball flight and sprint physics are replaced by a two-layer discrete model: (1) a spatial zone model for ball landing coordinates and fielder coverage sectors, and (2) a discrete time-tick sequence for baserunning progress ( segments per base). A stochastic resolver maps batting power/angle to landing coordinates and catch probabilities (, , ).
- **Player/agent count:** 2 teams of 8 agents (Team A and Team B). Batting lineup has 8 ordered batters; Fielding setup has 1 *brännare* stationed at the plate and 7 fielders assigned to spatial zones.
- **Turn model:** Sequential at-bats within timed/counted half-innings, with baserunning and ball retrieval resolved over discrete ticks ().
## Formal rules
R1. **Match Structure:** A match consists of 2 equal innings (halves). Team A bats and Team B fields in Inning 1; teams swap roles in Inning 2. Each half consists of complete plate appearances (2 full team rotations) [gap-fill].
R2. **Batting Action:** The active batter selects a bat type (`PADDLE` or `CYLINDRICAL`) and an aim direction/power vector .
- The engine samples an outcome from: `{LEGAL_HIT(x, y), FOUL_HIT, MISS}`.
- If `MISS` or `FOUL_HIT`, the batter may retry up to 3 total strikes. On a 3rd failed strike, the batter must run to Base 1 with a 2-tick delay penalty [gap-fill].
R3. **Fielding & Catch Resolution:**
- If a legal hit is produced, the engine determines if any fielder is in range of .
- Fly-ball catch probabilities are evaluated:
- Two-handed catch (*lyra*): Awards fielding team +1 point. Ball is instantly live with the fielder.
- One-handed catch (*enhandslyra*): Awards fielding team +2 points. Ball is instantly live with the fielder.
- Uncaught / Ground ball: Fielder closest to requires ticks to retrieve.
R4. **Relay & Burn Time:**
- The retrieving fielder throws the ball to the *brännare*. Total time until plate burn is [gap-fill].
- At tick , the plate is stomped ("Bränd!").
R5. **Baserunning Ticks:**
- During the window , all active runners on the bases simultaneously choose whether to advance or hold.
- Traversing one base leg (e.g. Base 1 to Base 2) requires ticks [gap-fill].
- Multiple runners may occupy the same base simultaneously with no capacity limit.
R6. **Burn Resolution & Scoring:**
- At tick , any runner who is between bases (not safely anchored on a base) is marked `BURNED`.
- Penalty: Each burned runner must return to the immediately preceding base, and the fielding team scores +1 point per burned runner [gap-fill].
- Safe arrival: Each runner who successfully reaches and touches Base 4 (Home) scores +1 point for the batting team.
- Home Run (*Frivarv*): If the batter circuits all 4 bases on their own legal hit before , the batting team scores +6 points (1 point for circuit + 5 bonus points).
R7. **All-Out Burn (*Utebränning*):**
- If all 8 players of the batting team are stranded on Bases 1, 2, or 3 with no eligible batter remaining in the queue, an *utebränning* is triggered.
- The fielding team is awarded +5 bonus points, and all stranded runners advance to Base 4 (scoring 0 circuit points) to clear the lineup for the next batter [gap-fill].
R8. **Victory:** At the end of Inning 2, the team with the higher cumulative match score wins.
## Edge cases
- Tie at the end condition: If both teams have equal points after 2 innings, the match is a draw (or resolved by 1 additional sudden-death batting rotation) [gap-fill].
- A player with no legal move: Batters must submit a swing; if an agent times out, a default neutral bunt swing is executed.
- Repetition / cycles: Strictly bounded by the fixed count of at-bats per half.
- Simultaneous claims on the same resource or position: Bases have infinite capacity; multiple runners occupying the same base do not collide.
- Player elimination mid-round: If a batting agent disconnects, their spot in the batting order is treated as an automatic out / skipped; if a fielder disconnects, their outfield zone is left unpatrolled.
- Resource exhaustion (pieces, tokens, space, time): Only 1 ball is active; base positions are fixed; time is bounded by inning length.
- Termination guarantee: Each at-bat terminates within ticks. Exactly at-bats occur per match, guaranteeing finite termination.
## State representation
- **Persistent state:**
- `inning`: 1 or 2.
- `scores`: `team_A_score`, `team_B_score` (integers).
- `at_bat_counter`: integer .
- `batting_order_index`: integer .
- **Per-turn ephemeral state:**
- `active_batter`: agent ID.
- `strike_attempts`: integer .
- `ball_state`: `IN_FLIGHT(x,y)`, `CAUGHT`, `GROUNDED(x,y)`, or `AT_PLATE`.
- `runner_positions`: map of runner ID .
- `burn_tick`: integer.
- **Observable information:**
- Fully observable: Scores, inning, ball landing coordinates, fielder positions, runner progress, and remaining at-bats are visible to all agents.
## Action space
- `select_bat(type)`: `PADDLE` (higher contact probability, lower distance) or `CYLINDRICAL` (lower contact, high distance).
- `swing(angle, power)`: float parameters .
- `advance_runner(runner_id, target_base)`: decision to run or stay for each active baserunner on each tick.
- `position_fielder(fielder_id, x, y)`: defensive formation setup prior to pitch.
## Playability notes
- Single-player-vs-AI: Highly playable — a human player can manage the batting lineup and baserunning decisions against an AI fielding engine, or act as the defensive manager optimizing fielder spatial distributions.
- Group games (n>4): The 8v8 game reduces naturally to a 2-agent manager game where Agent 1 controls offensive choices (batting vectors and running risks) and Agent 2 controls defensive positioning and relay decisions.
- Physical-skill games: Physical batting hand-eye coordination is abstracted into risk/reward bat selection and aim distributions; fielding reflexes are abstracted into catch probability curves.
- What is lost in the adaptation: The physical thrill of sprinting between bases, the loud collective shout of "Bränd!", and carnival tournament atmosphere of Brännbollsyran.
## Implementation hints
Moderate complexity. Structure the simulation as a discrete event queue: swing ball trajectory catch/ground check baserun loop until score update. First milestone: implement the deterministic baserun/burn logic on a 4-base cycle with hardcoded 8-tick burn timers before integrating the ball physics model.
Download as JSON
Download the full game corpus entry for this game as structured JSON.
Download JSONCite this page
Burnball (Swedish rounders) (Sweden). (n.d.). Games of Countries. https://gamesofcountries.com/games/se-sweden/brannboll
@misc{gamesofcountries-se-sweden-brannboll,
title = {Burnball (Swedish rounders) (Sweden)},
year = {n.d.},
publisher = {Games of Countries},
url = {https://gamesofcountries.com/games/se-sweden/brannboll}
}