Skip to main content
Formal Specification

Laptok (Belarusian Folk Lapta & Bat-and-Ball Game) — Formal Specification

Belarus · ball-team · Confidence: medium

← Back to game page

Implementation Suitability

Suitability: adaptation-requiredFidelity: discretizedGap-fills: 3
# Laptok (Лапток) — AI-optimized specification ## General idea A traditional Belarusian bat-and-ball field sport where a batting team in the "City" hits a pitched ball into the open pasture, then sprints across the field to a far base line and back to score runs. Fielders attempt to catch hits on the fly for an immediate turnover or throw the ball to strike running batters mid-sprint, which initiates a dynamic scramble/counter-tag race to occupy the City. ## Formal model - **Abstraction taken:** The 2D field is modeled as a longitudinal corridor [0,L] with two safe end-zones: City (x≤0) and Base (x≥L). Batting trajectories, fly-catches, and throwing accuracy are modeled via parameterized stochastic checks. - **Player/agent count:** 2 teams (Team A, Team B) of M agents each (M∈[4,10]). - **Turn model:** Hybrid sequential batting turns coupled with simultaneous ticked movement during ball-in-play and sprint/scramble phases. ## Formal rules R1. Setup & Roles: One team begins as Batters (in City, x≤0), the other as Fielders (in Field, 0<x<L). Batters establish a batting queue B=[b1,…,bM]. Match is played for a fixed number of innings Ninnings [gap-fill: fixed innings count assumed for formal termination]. R2. Pitch & Bat: Active batter bi receives a vertical toss from the Pitcher and executes `strike_ball()`. - If the strike clears the 10m minimum distance, ball enters `IN_PLAY` status with target landing coordinates (xb,yb) and air time tair. - If the batter fails 2 consecutive attempts, batter forfeits turn and moves to the tail of the batting queue without running. R3. Fly-Catch Turnover: If a fielder positioned near (xb,yb) succeeds on a `catch_fly_ball()` check before tair expires: - An immediate role swap occurs: Fielders become Batters, Batters become Fielders. - All base runners are cleared back to their respective team rosters. R4. Baserunning: On a valid ground hit: - Batter bi becomes an active runner and executes `sprint_to_base()` towards Base (x=L). - Any runner already safe at Base (x=L) may choose `sprint_to_city()` towards City (x=0) or `hold_base()`. - A runner reaching Base (x≥L) becomes Safe at Base. - A runner completing the full return to City (x≤0) scores 1 run for the batting team. R5. Tagging & Counter-Tag Scramble (*Перасалка*): - While runners are in the open field (0<x<L), fielders retrieve the ball and execute `throw_at_runner(target_runner)`. - If the throw hits the runner: Runner is tagged. The phase shifts immediately to `SCRAMBLE`. - During `SCRAMBLE`: Former fielders sprint towards City (x≤0); former batting team retrieves the ball and may execute `counter_throw()` at any fleeing former fielder. - If former fielders reach City without anyone being struck, role swap is finalized (former Fielders become Batters). If a former fielder is struck before entering City, the batting team retains Batting status [gap-fill: counter-tag success restores original team roles]. R6. Inning completion: When all batters have had their batting turn or an unresolved tag turnover occurs, the half-inning ends and roles swap. R7. Match end: The match terminates after Ninnings complete innings; the team with the higher cumulative run score wins. ## Edge cases - Tie at the end condition: If run totals are equal after Ninnings, one additional sudden-death inning is played [gap-fill]. - A player with no legal move: Not applicable; batters must strike or forfeit turn; fielders and runners always have valid movement vectors. - Repetition / cycles: Scramble throws resolve in finite ticks since all agents are running toward boundary lines. - Simultaneous claims on the same position: Multiple runners may share safe zone coordinates at Base or City. - Elimination mid-round and turn-order repair: Players are not eliminated; batting order advances modulo M. - Resource exhaustion: Ball is singular and re-spawned at City/Pitcher after every play. - Termination guarantee: The game is strictly bounded by Ninnings innings, each consisting of at most M batting turns and finite-tick sprint phases. ## State representation - Persistent state: - `score`: Map of Team → integer runs. - `current_inning`: Integer ∈[1,Ninnings]. - `batting_team_id`: Team ID currently batting. - `batting_queue`: Ordered list of agent IDs. - Ephemeral state: - `ball_state`: Coordinates (x,y,z), velocity vector, owner ID. - `agent_positions`: Map of agent ID →(x,y). - `runner_states`: Map of runner ID →{CITY,TRANSIT_TO_BASE,AT_BASE,TRANSIT_TO_CITY}. - `phase`: Enum ∈{PITCH,IN_PLAY,SCRAMBLE}. - Observable information: Fully observable 2D field state to all agents. ## Action space - `strike_ball(power, angle)`: Active batter hits pitched ball. - `sprint_to_base()` / `sprint_to_city()`: Runner moves along longitudinal corridor. - `field_ball()`: Fielder retrieves ground ball. - `throw_at_runner(target_id)`: Fielder aims and throws ball at an open-field runner. - `counter_throw(target_id)`: Batting player throws ball at fleeing fielder during scramble. ## Playability notes - Single-player-vs-AI: Adaptable with human controlling the batter/runner or fielding captain while AI runs spatial pursuit/pathfinding. - Group reduction: Reducible to 3v3 (pastoral lapta variant) without modifying core mechanics. - Physical-skill games: Batting trajectory, ball speed, sprint speed, and throwing accuracy are parameterized as stochastic attributes. - What is lost: The physical impact of wooden paddle contact, catching stung hands, and open-field tactical shouting. ## Implementation hints Treat as a 2D discrete-time physics or vector grid with boundary triggers for City and Base. First milestone: implement the single-batter hit-and-run loop with fly-catch detection before adding the scramble counter-tag state machine.

Download as JSON

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

Download JSON
Cite this page

Laptok (Belarusian Folk Lapta & Bat-and-Ball Game) (Belarus). (n.d.). Games of Countries. https://gamesofcountries.com/games/by-belarus/laptok

@misc{gamesofcountries-by-belarus-laptok,
  title = {Laptok (Belarusian Folk Lapta & Bat-and-Ball Game) (Belarus)},
  year = {n.d.},
  publisher = {Games of Countries},
  url = {https://gamesofcountries.com/games/by-belarus/laptok}
}