Formal Specification
Danguli (Tip-Cat Bat and Spindle) — Formal Specification
Bangladesh · dexterity-throw · Confidence: high
← Back to game pageImplementation Suitability
Suitability: engine-readyFidelity: probabilistic-proxyGap-fills: 2
# Danguli — AI-optimized specification
## General idea
A traditional Bengali bat-and-peg tip-cat game played with a long wooden striking stick (*danda*) and a double-tapered wooden spindle (*guli*). An attacking batter levers the spindle from a ground trench into the outfield; if uncaught, the fielder attempts to dismiss the batter by throwing the spindle back to hit the resting stick. Survived throws advance the batter to a high-scoring aerial tip-and-strike phase, with distances measured in a traditional 7-tier scale (*bari* to *mek*, *phul*, and *lal*).
## Formal model
- **Abstraction taken:** Trench launch and mid-air tip strikes are abstracted into aim angle and striking power rolls. The spatial distance achieved is mapped directly into traditional discrete units (stick lengths, *phul*, and *lal*). Fielding catches and return throws are modeled as spatial intercept checks and geometric hit rolls.
- **Player/agent count:** 2 teams of 4 agents (Batting team vs Fielding team).
- **Turn model:** Sequential individual batting turns within innings; 3 full innings per match.
## Formal rules
R1. Setup: Trench located at origin . Fielding team places 4 fielders across outfield sectors . Batting team sets up batter rotation . Match length is 3 innings.
R2. Phase 1 — Lever Launch (*ঘেটি থেকে চাল*):
- Batter submits `lever_launch(power, angle)`.
- Landing point is sampled:
R3. Phase 1 Fielding & Return Throw:
- Catch Check: If any fielder is within 3m of landing point during flight:
If caught, Batter is dismissed (**Out** / *আউট*), and the next batter steps up.
- [gap-fill] Return Throw: If uncaught, the batter places the *danda* across the trench. The retrieving fielder executes a return throw:
If the throw hits the resting stick (or lands in the trench), the batter is Out. If it misses, batter advances to Phase 2.
R4. Phase 2 — Aerial Tip-and-Strike (*ডাট মারা*):
- Batter chooses tip difficulty: `SINGLE_TIP` (1 tap), `DOUBLE_JUGGLE` (2 taps), or `TRIPLE_JUGGLE` (3 taps).
- Tip Success Check: for 1, 2, 3 taps respectively.
- If tip fails (misses contact), batter is Out.
- If tip succeeds, batter strikes the airborne guli downfield, gaining distance .
R5. Scoring & Distance Calculation:
- Total distance .
- Converted into *danda* lengths .
- Traditional conversion:
- 7 lengths (7 points).
- 7 *Phul* (49 lengths) (49 points).
- Remaining individual lengths () score corresponding points (*bari*, *duri*, *teri*, *chaghol*, *champa*, *jhek*).
R6. Inning Transition: When all 4 batters on a team are dismissed, the half-inning ends and teams swap batting and fielding roles.
R7. Win Condition: The team with the highest cumulative points after 3 complete innings wins the match.
R8. [gap-fill] Tiebreaker: In the event of a tie after 3 innings, each team nominates one champion batter for a single-launch sudden-death strike-off (furthest hit wins).
## Edge cases
- Tie at the end condition: Resolved via sudden-death single-batter strike-off per R8.
- A player with no legal move: Batting and fielding actions are always available during active turns.
- Repetition / cycles: Bounded strictly by the 3-inning limit and non-zero put-out probabilities.
- Simultaneous claims on the same resource or position: The closest fielder to the landing coordinate is prioritized for catch and return throw.
- Player elimination mid-round; turn order repair: Batter dismissal immediately passes turn to the next lineup index (); batting rosters reset at the start of each new inning.
- Resource exhaustion (pieces, tokens, space, time): All 4 dismissals immediately close the team's half-inning.
- Termination guarantee: Dismissal mechanics ensure finite batting durations; fixed 3-inning structure provably terminates the match.
## State representation
- Persistent state:
- `scores`: Array of 2 integers (cumulative points for Team 1 and Team 2).
- `current_inning`: Integer .
- `active_batting_team`: .
- `outs_count`: Integer .
- `active_batter_idx`: Integer .
- Per-turn ephemeral state:
- `guli_coord`: coordinate of the peg.
- `fielder_coords`: Array of 4 positions.
- `phase`: .
- Observable information: Fully observable field geometry, scores, outs, and fielder positioning.
## Action space
- `lever_launch(power_norm, angle_deg)`: Launch spindle from trench (power , angle ).
- `tip_strike(taps_count, power_norm)`: Execute juggle tip and mid-air strike (taps ).
- `position_fielders(positions_array)`: Fielding team sets coordinates for 4 fielders before each launch.
## Playability notes
- Single-player-vs-AI: Highly engaging as an arcade batting/aiming challenge with risk-reward trade-offs on multi-tap juggles.
- Group games (n>4): Modeled cleanly as a 4v4 team game where Agent 1 manages Batting team and Agent 2 manages Fielding team.
- Physical-skill games: Spindle aerodynamics, wood impact timing, and hand-eye coordination are mapped to timing-risk choices and attribute-weighted random variables.
- What is lost in the adaptation: The tactile crack of the wooden danda striking the spinning spindle in mid-air.
## Implementation hints
Moderate complexity. State machine flows cleanly through `Launch -> Catch_Check -> Return_Throw -> Tip_Strike -> Distance_Tally -> Out_Check`. Milestone 1: implement single-batter Phase 1 and 2 trajectory calculations and 7-tier point converter; Milestone 2: build outfield defensive positioning heuristics.
Download as JSON
Download the full game corpus entry for this game as structured JSON.
Download JSONCite this page
Danguli (Tip-Cat Bat and Spindle) (Bangladesh). (n.d.). Games of Countries. https://gamesofcountries.com/games/bd-bangladesh/danguli
@misc{gamesofcountries-bd-bangladesh-danguli,
title = {Danguli (Tip-Cat Bat and Spindle) (Bangladesh)},
year = {n.d.},
publisher = {Games of Countries},
url = {https://gamesofcountries.com/games/bd-bangladesh/danguli}
}