Formal Specification
Seven Stones / Pile of Tiles — Formal Specification
India · dexterity-throw · Confidence: low
← Back to game pageImplementation Suitability
Suitability: adaptation-requiredFidelity: probabilistic-proxyGap-fills: 2
# Lagori / Pitthu — AI-optimized specification
## General idea
Lagori (also known as *Pitthu* or *Seven Stones*) is a traditional Indian team sport combining target throwing, spatial evasion, and rapid collaborative construction. An attacking striker throws a ball to topple a vertical tower of seven flat discs, after which the attacking team scrambles to rebuild all seven discs in proper size order while dodging throws from defending fielders, who pass the ball among themselves to tag the builders out before the tower is completed.
## Formal model
- **Abstraction taken:** The 20m 15m field is discretized into a 2D continuous coordinate plane. The game decomposes into two discrete phases: (1) The Striking Phase (probabilistic ball-to-tower impact resolver), and (2) The Active Scramble & Reconstruction Phase (discretized time ticks s where ball passing, player motion, and stone placement are simulated).
- **Player/agent count:** 2 teams of agents (), where .
- **Turn model:** Two-phase round structure with role-swapping upon failure or inning completion.
## Formal rules
R1. **Setup & Initial Tower:**
- Tower of 7 flat stones stacked at origin in descending radius order ().
- Throwing crease marked at distance meters from the tower.
- Attacking team lineup queues at the crease; Defending team fielders disperse in the outfield.
R2. **Phase 1 (The Tower Strike):**
- Active striker receives up to 3 throwing attempts to hit the tower.
- Striker selects throw vector . Impact resolver evaluates:
- Tower hit probability: .
- Number of stones toppled .
- Post-strike ball trajectory and air time.
- **Fly Catch Check:** If the ball deflects off the stones and is caught directly in mid-air by a fielder before touching the ground, striker is "Out".
- If striker misses all 3 attempts without toppling any stone, is "Out", and the next teammate steps up to throw.
- If at least one stone is toppled and the ball hits the ground, Phase 2 is triggered immediately.
R3. **Phase 2 (Scramble, Tagging, & Stacking):**
- **Toppled Stones:** stones scatter randomly around the origin with positions .
- **Attackers' Objective:** Move to the stones, pick up un-stacked stones, and stack them at in strict descending order .
- Action `place_stone(stone_id)` takes a base duration of second (5 ticks) per stone.
- **Defenders' Objective & Ball Handling:**
- Defenders retrieve the loose ball and pass it (`pass_ball(target_defender)`).
- Defenders holding the ball cannot run (maximum 2 steps allowed before passing or throwing).
- Defender executes `throw_at_attacker(attacker_id)` targeting any active attacker within throwing range.
R4. **Elimination & Victory Conditions:**
- **Attacker Tagged Out:** If a thrown ball strikes an attacker below shoulder level before the 7th stone is stacked:
- The attacking team's round terminates immediately.
- Defending team scores point (or successfully terminates the offensive half).
- **Tower Restored ("Lagori!"):** If the attacking team successfully stacks all 7 stones in correct descending order without any player being tagged:
- The stacker shouts **"Lagori!"** (`claim_lagori()`).
- Attacking team scores point (or points in traditional scoring).
- Attacking team retains offensive striking rights for the next round.
R5. **Inning and Match Resolution:**
- When all strikers on the attacking team are eliminated without rebuilding the tower, teams swap roles ().
- The team with the highest score after an agreed number of innings (e.g. 2 full innings) wins the match.
- [gap-fill] If scores are tied after regular innings, a sudden-death 1-round shootout is conducted (team with fastest tower-reconstruction time wins).
## Edge cases
- **Tie at the end condition:** Handled by R5 (sudden-death timed shootout).
- **A player with no legal move:** Fielders always have pass/throw actions; attackers always have movement or stone-picking actions.
- **Repetition / cycles:** Phase 2 is bounded by [gap-fill] a maximum round duration of 3 minutes (900 ticks); if attackers fail to stack within 3 minutes, round defaults to defense.
- **Simultaneous claims on the same resource or position:** Multiple attackers can assist in gathering stones; stacking at enforces a single-stone-at-a-time mutex lock.
- **Player elimination mid-round; turn order repair:** Fly catch in Phase 1 advances batting index ; tag in Phase 2 terminates the entire team round immediately.
- **Resource exhaustion (pieces, tokens, space, time):** 7 stones are invariant; 3-minute round clock guarantees temporal bounds.
- **Termination guarantee: why the game provably ends:** Phase 1 terminates by striker elimination or toppling; Phase 2 terminates by ball-tag, successful 7-stone rebuild, or the 3-minute timeout.
## State representation
- **Persistent state:**
- Inning index; Round index; Match scores .
- Striker lineup queue ; Active striker index.
- **Per-round ephemeral state:**
- .
- Tower state: list of currently stacked stones at origin .
- Un-stacked stone coordinates .
- Ball state: .
- Player coordinates: Attackers , Defenders .
- Round timer .
- **Observable information:** Fully observable 2D field state.
## Action space
- `aim_and_throw_tower(angle, power)`: (Striker, Phase 1).
- `move_player(dx, dy)`: (All players, Phase 2).
- `pass_ball(target_defender_id)`: (Defender in possession).
- `throw_at_attacker(target_attacker_id, power)`: (Defender in possession).
- `pick_up_stone(stone_id)`: (Attacker within stone radius).
- `place_stone(stone_id)`: (Attacker at origin ).
- `claim_lagori()`: (Attacker upon placing 7th stone).
## Playability notes
- **Single-player-vs-AI:** Highly playable as a real-time tactical game. Human manages the attacker squad (diverting defenders, retrieving stones, timing the final stack) against AI passing fielders.
- **Group games ():** 6v6 or 9v9 team game reduces naturally to a 2-agent Commander format: Attacking Coordinator vs Fielding Coordinator.
- **Physical-skill games:** Ball throwing accuracy and stone stacking dexterity are modeled via distance-decayed hit distributions and stacking duration timers.
- **What is lost in the adaptation:** The adrenaline of diving behind a teammate to dodge a speeding rubber ball, and the communal roar of *"Pitthu Garam!"*.
## Implementation hints
- Implement Phase 2 as a discrete spatial simulation where defenders execute basic Voronoi area defense and nearest-neighbor passing heuristics.
- Branching factor: Striker has continuous throw parameters (discretized to choices); Phase 2 has multi-agent movement, passes, and stone pickups (commander macro branching factor ).
- Obvious representational trap: Allowing defenders to run with the ball; traditional rules strictly enforce passing or a 2-step limit.
- Suggested first milestone: Implement the 7-stone stacking queue at and a basic 2v2 scramble simulation where 1 ball-carrier passes to a teammate to tag a stone-carrier.
Download as JSON
Download the full game corpus entry for this game as structured JSON.
Download JSONCite this page
Seven Stones / Pile of Tiles (India). (n.d.). Games of Countries. https://gamesofcountries.com/games/in-india/lagori
@misc{gamesofcountries-in-india-lagori,
title = {Seven Stones / Pile of Tiles (India)},
year = {n.d.},
publisher = {Games of Countries},
url = {https://gamesofcountries.com/games/in-india/lagori}
}