Formal Specification
Tip-Cat / Bat-and-Peg — Formal Specification
Lithuania · stick-team · Confidence: low
← Back to game pageImplementation Suitability
Suitability: engine-readyFidelity: discretizedGap-fills: 10
# Muštukas — AI-optimized specification
## General idea
Muštukas (tip-cat / *čyžas*) is a traditional Lithuanian bat-and-peg striking and base-running game. The batter executes a two-phase strike: sharply tapping the tapered tip of a wooden peg to pop it spinning into the air, then driving it mid-flight into the outfield. While the peg is in flight and being retrieved, the batter attempts a round-trip sprint to a distant base and back to score runs, while the fielding team attempts a fly catch or a precision throw into the home base circle to record an out.
## Formal model
- **Abstraction taken:** Probabilistic-proxy. Continuous tip-cat pop aerodynamics, rotational spin, mid-air bat contact, sprint biomechanics, and fielder throwing trajectories are modeled as sequential stochastic events: , landing coordinates , runner transit time , and fielding return time [gap-fill].
- **Player/agent count:** 2 teams of agents each (): Batting Team and Fielding Team .
- **Turn model:** Sequential batter turns; an inning consists of batting until outs are recorded [gap-fill], after which teams swap roles.
## Formal rules
R1. Setup and Field Geometry:
- Home base is a circle of radius at [gap-fill].
- Far base is located at .
- Outfield covers the forward half-plane .
- Match length is fixed at innings per team [gap-fill].
R2. Two-Phase Strike Execution:
- Phase 1 (The Pop): Batter attempts to pop the peg. Success probability [gap-fill]. The batter is permitted up to 3 pop attempts; failing all 3 counts as an out.
- Phase 2 (The Hit): Upon a successful pop, the batter strikes the peg mid-air with chosen power and horizontal angle , projecting the peg to landing coordinate .
R3. Fielding and Defense:
- Fly Catch: If the peg trajectory intersects any fielder's catch radius () before ground touchdown, [gap-fill]. A successful fly catch immediately records 1 Out.
- Ground Retrieval and Throw: If the peg touches ground at , the nearest fielder retrieves it and throws toward . Fielding return time is computed as [gap-fill].
- Throw Accuracy: The thrown peg lands inside with probability [gap-fill].
R4. Base Running and Scoring:
- Upon striking the peg, the batter sprints from (total distance ). Runner transit time .
- If OR the fielder's base throw misses , the runner scores Run for .
- If AND the fielder's throw hits , the runner is ruled Out.
R5. Inning Transition and Rotation:
- When 3 outs are accumulated, the half-inning ends immediately, uncommitted base runs are cleared, and teams swap roles ().
R6. Match Win Condition:
- After complete innings, the team with the higher cumulative run total wins the match.
## Edge cases
- Tie at the end condition: If scores are tied after innings, teams play 1 additional extra inning until the tie is resolved [gap-fill].
- A player with no legal move: Not applicable — batter must submit pop/strike parameters; fielders position algorithmically.
- Repetition / cycles (and the loop-breaking rule): Infinite play is impossible because every batting attempt strictly increments either the run total or the out counter (capped at 3 outs per half-inning).
- Simultaneous claims on the same resource or position: If the runner touches on the exact same tick that the peg strikes (), the tie goes to the runner (safe, run) [gap-fill].
- Player elimination mid-round; turn order repair: An out retires the individual batter for the remainder of that half-inning; batting order proceeds to the next teammate in sequence .
- Resource exhaustion (pieces, tokens, space, time): The peg is retrieved after every hit; innings are strictly bounded by and .
- Termination guarantee: Provably terminates because each half-inning requires at most strike attempts to generate 3 outs, and the inning count is finite.
## State representation
- Persistent state: Inning count , half-inning index , team scores , active out counter , batting order pointer.
- Per-turn ephemeral state: Pop attempt counter , peg coordinates , runner progress , fielder positions , throw return vector.
- Observable information: Fully observable — all player positions, run scores, out counts, and peg ballistics are public.
## Action space
- `pop_and_strike(tap_force, swing_power, aim_angle)`: Execute two-phase peg launch.
- `set_fielding_formation(positions)`: Allocate fielding coverage across outfield zones.
## Playability notes
- Single-player-vs-AI: Highly natural — human plays as the batter balancing power hits with sprint timing against an AI defense.
- Group games (n>4): Can be reduced to 1v1 (as in the traditional *Vienetų muštukas* variant) where one player bats and one fields.
- Physical-skill games: The double strike (tapping a tapered peg into the air and hitting it on the descent) is abstracted into coupled stochastic launch and trajectory functions.
- What is lost: The sharp tactile crack of hardwood against hardwood, dust flying from grass turf, and the physical sprint between stakes are converted into timing simulations.
## Implementation hints
Discrete turn machine with an internal timing comparator ( vs ).
First milestone: Build the single-batter strike, trajectory generation, and base-running timing resolver, verifying out and run calculations.
Download as JSON
Download the full game corpus entry for this game as structured JSON.
Download JSONCite this page
Tip-Cat / Bat-and-Peg (Lithuania). (n.d.). Games of Countries. https://gamesofcountries.com/games/lt-lithuania/mustukas
@misc{gamesofcountries-lt-lithuania-mustukas,
title = {Tip-Cat / Bat-and-Peg (Lithuania)},
year = {n.d.},
publisher = {Games of Countries},
url = {https://gamesofcountries.com/games/lt-lithuania/mustukas}
}