Skip to main content
Formal Specification

Palant (Polish Bat-and-Ball) — Formal Specification

Poland · ball-team · Confidence: low

← Back to game page

Implementation Suitability

Suitability: adaptation-requiredFidelity: discretizedGap-fills: 3
# Palant — AI-optimized specification ## General idea A two-team asymmetric bat-and-ball territory game where the batting team attempts to launch a ball deep into enemy territory and complete circuit runs across a hazardous corridor, while the defending team positions fielders to intercept airborne projectiles and eliminate runners via thrown ballistic tags. The core strategic dynamic is balancing sprint timing against defensive throwing coverage. ## Formal model - **Abstraction taken:** The 60×25 m field is discretized into a 12×5 zone grid (each cell 5×5 m). Zones 0–4 constitute the batting half (*Niebo*), Zone 0 contains the *Gniazdo* (batting box), Zones 5–11 constitute *Piekło*, and Zone 11 is the safety end zone (*kampa*). The continuous flight and throw trajectories are resolved via discrete ball landing vectors and stochastic intercept checks. - **Player/agent count:** 2 teams of 8 agents (Team A, Team B). At any time, one team is in the batting state (*Niebo*) and one in the fielding state (*Piekło*). - **Turn model:** Tick-based sequential phase structure within an inning. Each batting turn comprises: (1) Batting action, (2) Simultaneous movement ticks (3 discrete ticks per hit) for all active runners and fielders, and (3) Fielding resolution (catch, relay, or tag throw). ## Formal rules R1. **Setup:** The match consists of 4 innings (2 halves per team as batting and fielding). Team A starts in *Niebo*, Team B in *Piekło*. R2. **Batting phase:** The batting team selects the next agent in their fixed roster order (1 to 8, where agent 8 is the *matka*). The active batter executes `strike_ball(power, angle)`. - Power and angle determine the target landing zone in *Piekło* (Zones 5–11) via a stochastic distribution parameterized by agent skill. - If the landing zone is out-of-bounds or within *Niebo* (Zones 0–4), the strike is a foul. A foul consumes 1 attempt. Standard batters have 1 attempt; the *matka* has 3 attempts. R3. **Fielding interception:** If a fielder occupies the ball's target landing cell upon arrival, an airborne catch check `P_catch = f(fielder_skill)` is resolved. If caught in the air, the fielding team gains 1 defensive point immediately. R4. **Running phase:** Following a valid hit, the batter and any runners currently stationed at *kampa* may choose `sprint(direction)` across adjacent zones per tick (movement speed: 1 zone per tick; sprint action: up to 2 zones per tick with stamina cost). - Reaching Zone 11 (*kampa*) places a runner in "safe shelter". - Returning from Zone 11 to Zone 0 (*Gniazdo*) awards the batting team 1 run point. R5. **Tagging resolution (*skucie*):** A fielder in possession of the ball in *Piekło* may execute `throw_tag(target_runner)`. - The tag succeeds if `distance(fielder, runner) <= 2` zones and the stochastic accuracy roll passes. - Upon a successful tag on an un-sheltered runner, a turnover occurs: all batting runners must immediately reach a base while fielders sprint toward *Niebo*. [gap-fill] An immediate turnover is formalized: roles flip, and current inning half ends. R6. **Inning turnover:** An inning half concludes immediately when: (a) a runner is successfully tagged (*skucie*), (b) all 8 batters have exhausted their attempts, or (c) the fielding team accumulates 3 airborne catches in the half. R7. [gap-fill] **Match duration and victory:** The match terminates after exactly 4 completed full innings (8 halves). The team with the highest cumulative points (run points + catch points) wins. ## Edge cases - **Tie at the end condition:** If cumulative points are equal after 4 innings, [gap-fill] a sudden-death mini-inning (1 extra half per team with 3 batters each) is played until the tie is broken. - **A player with no legal move:** Batters must strike; if an agent's stamina is zero, the strike is executed with minimum power. Runners in shelter may choose `hold_position`. - **Repetition / cycles:** Bounded strictly by the finite batter queue (8 players per half) and the fixed 4-inning structure; infinite running without hitting is illegal. - **Simultaneous claims on the same resource or position:** Multiple runners may shelter concurrently in Zone 0 (*Gniazdo*) or Zone 11 (*kampa*). On intermediate field grid cells, collisions are allowed without blocking. - **Player elimination mid-round; turn order repair:** If an agent is tagged out (*skuty*), the entire half ends immediately, resetting positions for the next half. - **Resource exhaustion:** Balls are indestructible and reset to the *Gniazdo* after each play; stamina regenerates between innings. - **Termination guarantee:** Each half has at most 8 batting sequences with a fixed maximum number of movement ticks (10 ticks per sequence), guaranteeing strict polynomial-time termination. ## State representation - **Persistent state:** `team_scores` (Map[TeamId, Int]), `current_inning` (1..4), `current_half` (Top/Bottom), `batting_team_id`, `fielding_team_id`. - **Per-half state:** `batting_queue_index` (0..7), `active_runners` (List[RunnerState: {agent_id, zone_id, origin_direction}]), `fielders_positions` (Map[AgentId, ZoneCoord]), `catches_in_half` (0..3). - **Ephemeral state:** `ball_state` ({in_flight, carrier_id, pos_coord, target_coord}), `ticks_remaining` (Int). - **Observable information:** Fully observable state; all agents know ball location, player coordinates, score, and outs count. ## Action space - `strike_ball(power: Float[0..1], angle: Float[-45..45])`: Active batter only; triggers ball trajectory calculation. - `sprint(target_zone: Coord)`: Runner/fielder motion to an adjacent or 2-step connected cell. - `throw_tag(target_agent_id: AgentId)`: Ball-holding fielder attempts to hit an exposed runner. - `pass_ball(target_fielder_id: AgentId)`: Ball-holding fielder relays ball to a closer teammate. - `hold_position()`: Remain stationed in the current zone (mandatory when sheltered). ## Playability notes - **Single-player-vs-AI:** Highly natural — the human commands either the batter-runner decisions or the defensive fielding coordination against AI heuristic agents. - **Group games (n>4):** Reduces cleanly to 2 macro-agents (Batting Captain vs. Fielding Captain) controlling squad formations on the discretized grid. - **Physical-skill games:** Batting power, fielding catch chance, and tag accuracy are parameterized by 3 skill scalars: `batting_skill`, `catching_skill`, `throwing_accuracy`. - **What is lost:** Real-time physical dodging and manual bat-swing timing are replaced by stochastic success envelopes. ## Implementation hints Grid size is small (12×5), giving very low branching factor per turn (~4 movement choices and 2 tactical choices per agent). First milestone: implement the deterministic inning-rotation and batting-running scoring pipeline with deterministic straight-line hits, then add the fielding interception and tagging resolver.

Download as JSON

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

Download JSON
Cite this page

Palant (Polish Bat-and-Ball) (Poland). (n.d.). Games of Countries. https://gamesofcountries.com/games/pl-poland/palant

@misc{gamesofcountries-pl-poland-palant,
  title = {Palant (Polish Bat-and-Ball) (Poland)},
  year = {n.d.},
  publisher = {Games of Countries},
  url = {https://gamesofcountries.com/games/pl-poland/palant}
}