Formal Specification
Go and Chase / Catch-and-Relay — Formal Specification
India · chase-tag · Confidence: high
← Back to game pageImplementation Suitability
Suitability: engine-readyFidelity: discretizedGap-fills: 1
# Kho-Kho — AI-optimized specification
## General idea
Kho-Kho is a high-speed traditional Indian tag and pursuit sport played on a rectangular court featuring a central lane and two end posts. Eight chasing players sit in alternate facing directions along the central dividing line while one active chaser pursues a batch of three defending runners. The active chaser can instantly transfer pursuit momentum to any seated teammate by tapping their back and shouting "Kho!", forcing the newly activated chaser into an explosive sprint in their pre-set facing direction, while adhering to strict directional commitment and central lane crossing rules.
## Formal model
- **Abstraction taken:** The 27.0 m 16.0 m court is discretized into a 2D coordinate grid of size cells (0.5 m resolution). Time progresses in discrete ticks seconds (5 Hz). The 8 central sitting squares and 2 end posts are modeled with exact geometric coordinate constraints.
- **Player/agent count:** 2 teams of 9 agents ().
- **Turn model:** 2 innings per match; each inning consists of two 9-minute turns ( ticks per turn), alternating chasing and defending roles.
## Formal rules
R1. **Court Architecture & Setup:**
- Court dimensions: , .
- Central lane along between posts at .
- 8 seating squares positioned along at regular intervals.
- Chasing team positions 8 players seated inside , with alternating facing vectors:
- 9th chaser starts as the active chaser in a free zone.
- Defending team partitions its 9 runners into 3 sequential batches of 3 runners each: . Batch enters the court at .
R2. **Chaser Movement Constraints & Fouls:**
- **Central Lane Constraint:** cannot cross the central dividing line () directly. To switch between the North () and South () halves, must run completely around one of the two end posts at . Crossing elsewhere incurs a *Central Lane Foul*.
- **Directional Commitment:** Once takes a step in a direction along the -axis (e.g. towards Post 1 at ), they cannot turn back or reverse towards Post 2 until they touch the post or execute a "Kho" (*Direction Foul*).
- Violating directional rules forces an immediate foul penalty (chaser must stop and yield position).
R3. **The "Kho" Relay Action:**
- may transfer the chase role to any seated teammate by moving adjacent to from behind, executing `give_kho(k)`.
- Upon `give_kho(k)`:
- Seated player is instantly activated as the new .
- The newly activated chaser MUST advance immediately into the half they were facing ().
- The previous sits down in square , adopting the required sitting orientation.
R4. **Elimination of Runners:**
- An active runner is declared "Out" if:
- Touched/tagged by with an open hand within legal distance ( cell).
- Both feet cross completely outside the outer boundary lines.
- Failure to enter the court within the prescribed time window upon batch elimination.
- When all 3 runners of batch are eliminated, the next batch must enter the court within 5 ticks.
- Chasing team scores point per eliminated runner.
R5. **Match Resolution:**
- A turn expires after 9 minutes (2700 ticks), or when all 9 runners (all 3 batches) are eliminated.
- If all 9 runners are eliminated before time expires, the chasing team scores 9 points and re-enters for the remaining time.
- Teams swap roles ().
- The team with the highest aggregate score after 2 full innings wins the match.
- [gap-fill] In knockout matches ending in a tie, an extra mini-inning (one 9-minute turn each, with the shortest time to eliminate 1 batch acting as the tiebreaker) is played.
## Edge cases
- **Tie at the end condition:** Handled by R5 (extra tiebreaker inning / minimum-time-to-first-batch metric).
- **A player with no legal move:** Seated chasers must remain seated until receiving a "Kho"; active chaser always has valid forward motion or `give_kho()` actions.
- **Repetition / cycles:** Chaser running endlessly without tagging is strictly bounded by the 9-minute turn clock countdown.
- **Simultaneous claims on the same resource or position:** If is adjacent to multiple runners, executing `tag()` eliminates the nearest runner.
- **Player elimination mid-round; turn order repair:** Eliminated runner is removed; when batch size drops from 3 to 0, next batch index increments monotonically ().
- **Resource exhaustion (pieces, tokens, space, time):** 9 players and 3 batches are fixed; turn clock guarantees temporal exhaustion.
- **Termination guarantee: why the game provably ends:** Guaranteed by monotonic tick countdown from 2700 to 0 per turn.
## State representation
- **Persistent state:**
- Inning index ; Turn index .
- Cumulative scores .
- Active batting/chasing team ID.
- **Per-tick ephemeral state:**
- Turn clock remaining .
- Seated chasers array: , each storing .
- Active chaser state: .
- Active batch index ; Runner states for .
- **Observable information:** Fully observable 2D court state.
## Action space
- `move_chaser(dx, dy)`: (Active chaser; subject to directional and lane constraints).
- `turn_around_post(post_id)`: (Active chaser at ; resets directional constraint).
- `give_kho(seated_square_id)`: (Active chaser; transfers active pursuit role).
- `move_runner(runner_id, dx, dy)`: (Active runners; 2D dodging and boundary navigation).
- `tag_runner(target_id)`: (Active chaser; checks collision and executes tag).
## Playability notes
- **Single-player-vs-AI:** Excellent tactical pursuit problem. The human controls the chasing team, orchestrating optimal "Kho" triggers to trap elusive AI runners between the seated grid and boundary walls.
- **Group games ():** Natural 9v9 structure reduces cleanly to a 2-agent Commander game: Chasing Tactician vs Evasive Navigator.
- **Physical-skill games:** Physical sprinting agility and diving tags are discretized into speed vectors and a probabilistic diving tag success resolver.
- **What is lost in the adaptation:** The sudden burst of physical acceleration when receiving a hard tap on the back, and the intense vocal rhythm of shouting *"Kho!"*.
## Implementation hints
- Represent the central lane as a strict impassable barrier in the pathfinding navmesh, with passable portal zones only at the two post vertices.
- Branching factor: Active chaser has 3 directional moves + 8 possible `give_kho()` targets ( actions); 3 active runners have 8 movement choices each ( joint evasive moves).
- Obvious representational trap: Allowing an activated chaser to choose their running half; they MUST enter the half they were already facing when seated.
- Suggested first milestone: Implement court geometry with the central impassable line and 2 posts; simulate 1 chaser chasing 1 runner with post-turning mechanics before adding the seated chaser relay.
Download as JSON
Download the full game corpus entry for this game as structured JSON.
Download JSONCite this page
Go and Chase / Catch-and-Relay (India). (n.d.). Games of Countries. https://gamesofcountries.com/games/in-india/kho-kho
@misc{gamesofcountries-in-india-kho-kho,
title = {Go and Chase / Catch-and-Relay (India)},
year = {n.d.},
publisher = {Games of Countries},
url = {https://gamesofcountries.com/games/in-india/kho-kho}
}