Formal Specification
Tip-Cat / Spindle-and-Bat — Formal Specification
Pakistan · stick-team · Confidence: low
← Back to game pageImplementation Suitability
Suitability: engine-readyFidelity: discretizedGap-fills: 2
# Gulli Danda — AI-optimized specification
## General idea
A turn-based team batting-and-fielding game played on an open coordinate plane with a base pit. The active striker launches a dual-tapered wooden spindle (*Gulli*) into the air and hits it downfield, while the fielding team attempts to catch it airborne or throw it back to hit the base bat. Score accumulates proportional to the distance between the final resting point and the home pit, measured in discrete stick-length units.
## Formal model
- **Abstraction taken:** The physical spindle flight and bat impact are modeled as a 2D trajectory on ground plane `(x, y)` with launch origin `(0, 0)`. The bat length is normalized to `L_danda = 1.0` distance unit.
- **Player/agent count:** 2 teams (Team A batting, Team B fielding), with `K` agents per team (standard `K = 4`).
- **Turn model:** Sequential batsman dismissal; each batsman executes launch and strike phases until dismissed.
## Formal rules
R1. Setup: Home pit is located at `(0, 0)`. Fielding team agents `F_1..F_K` are positioned in the half-plane `x > 10`.
R2. Phase 1 (Pit Launch): Striker selects launch power `P_1 in [10, 30]` and angle `theta in [-45, 45]`.
- Spindle landing position is sampled: `(x_1, y_1) = (P_1 * cos(theta) + eps_x, P_1 * sin(theta) + eps_y)`.
- Catch check: If distance from any fielder `dist(F_i, (x_1, y_1)) <= 2.0`, catch succeeds -> Striker is OUT immediately.
R3. Phase 1 Return Throw:
- If uncaught, nearest fielder throws spindle back at bat resting at `(0, 0)` with accuracy variance `sigma_throw`.
- If return throw lands within `dist <= 0.5` of `(0, 0)`: Striker is OUT (stumped).
R4. Phase 2 (Tip-and-Hit):
- If surviving Phase 1, striker at `(x_1, y_1)` taps spindle to pop up and executes strike with power `P_2 in [20, 60]`.
- Final spindle landing is `(x_final, y_final)`.
- If caught by fielders in Phase 2 -> Striker is OUT.
R5. Scoring:
- If surviving, score earned = `floor(sqrt(x_final^2 + y_final^2) / L_danda)`.
- Multiplier: If striker successfully executes a multi-tap juggle (simulated via high skill check), score is multiplied by `2x` or `3x`.
R6. Dismissal rotation: When a striker is OUT, the next teammate steps up to bat.
R7. Innings swap: When all `K` batsmen are dismissed, teams swap roles (Team B bats, Team A fields).
R8. [gap-fill] Match end: Both teams complete 1 full innings (or agreed `M` innings). The team with higher aggregate score wins.
R9. [gap-fill] Tie-breaker: If scores are tied after equal innings, each team nominates 1 striker for a single-shot longest distance contest.
## Edge cases
- **Tie at the end condition:** Handled by single-shot sudden-death longest distance strike (R9).
- **A player with no legal move:** Power and angle parameter selections always admit legal values.
- **Repetition / cycles:** Strictly finite horizon of `2 * K` batsman dismissals.
- **Simultaneous claims on the same resource or position:** The nearest fielder is uniquely assigned to the return throw based on minimal Euclidean distance.
- **Player elimination mid-round:** Batsman dismissal passes the turn directly to the next index in the team batting roster.
- **Resource exhaustion:** Team roster decrements to 0, triggering end of innings.
- **Termination guarantee:** Guaranteed by finite team rosters and non-zero dismissal probability per batting phase.
## State representation
- **Persistent state:** `scores[A, B]`, `current_innings in {1, 2}`, `active_batting_team in {A, B}`, `active_batsman_idx in {1..K}`.
- **Per-strike ephemeral state:** Coordinates of `(x_1, y_1)`, `(x_final, y_final)`, fielder positions, strike outcome, turn score.
- **Observable information:** Fully observable game state (scores, fielder coordinates, spindle location).
## Action space
- `launch_tulla(power, angle)`: Phase 1 ground launch parameters.
- `tip_and_strike(power, angle, juggle_intent)`: Phase 2 airborne striking parameters.
- `field_throw(target_x, target_y)`: Fielder defensive return throw.
## Playability notes
- **Single-player-vs-AI:** Natural; human striker aims for gaps in the AI defensive outfield and executes timing-based tip-strikes.
- **Group games (n>4):** Reduces directly; team batting sequence functions identically to standard cricket/baseball state machines.
- **Physical-skill games:** The double-action physics of the tip-and-strike is parameterized by a timing window function and precision variance.
- **What is lost:** The tactile snap of wood striking wood, the spin physics of the tapered spindle, and traditional Punjabi penalty piggybacks (*Sawari*).
## Implementation hints
Low-to-medium complexity. The geometry is straightforward 2D projectile landing sampling with Euclidean distance calculations. Build the Phase 1 launch-and-throw resolution first before adding Phase 2 tip-strike mechanics.
Download as JSON
Download the full game corpus entry for this game as structured JSON.
Download JSONCite this page
Tip-Cat / Spindle-and-Bat (Pakistan). (n.d.). Games of Countries. https://gamesofcountries.com/games/pk-pakistan/gulli-danda
@misc{gamesofcountries-pk-pakistan-gulli-danda,
title = {Tip-Cat / Spindle-and-Bat (Pakistan)},
year = {n.d.},
publisher = {Games of Countries},
url = {https://gamesofcountries.com/games/pk-pakistan/gulli-danda}
}