Skip to main content
Formal Specification

Moroccan stone-stacking target throw (Rmi l-Ahjar) — Formal Specification

Morocco · dexterity-throw · Confidence: medium

← Back to game page

Implementation Suitability

Suitability: engine-readyFidelity: probabilistic-proxyGap-fills: 2
# Taqchab — AI-optimized specification ## General idea An asymmetric two-team outdoor game combining target throwing, dodgeball elimination, and spatial construction. Team A attempts to topple a central stone tower from a distance, then frantically gathers and restacks the scattered stones while Team B fields the ball, passes among defenders, and hurls the ball to eliminate rebuilders before construction is completed. ## Formal model - **Abstraction taken:** The 2D outdoor field (20×20m) is modeled with continuous coordinates and discrete synchronous time ticks (Δt=200ms). Tower structure is modeled as a stack count H∈[0,7] with physical stone pieces scattered upon impact. - **Player/agent count:** 2 teams (TA=Attackers, TB=Defenders), each with K=4 agents. - **Turn model:** Two phases: Phase 1 (sequential target throws) → Phase 2 (simultaneous real-time ticked dodgeball and construction). ## Formal rules R1. **Setup & Initial Tower:** - Field: Center at (0,0). Throwing line at Y=−10m. - Tower at (0,0) consists of Nstones=7 stacked stones (H=7). - Phase = 1 (*Target Throw*). R2. **Phase 1: Toppling the Tower:** - Agents of TA take turns throwing at (0,0) from line Y=−10m: - Throw action `throw_at_tower(power, aim_angle)`. - Hit probability Phit=f(distance,skill). - If a hit occurs: Tower topples (H→0), 7 stones scatter into radius R≤3m around (0,0), ball bounces into field, and match immediately transitions to Phase 2. - If all K agents of TA miss, roles swap (TA↔TB) and Phase 1 restarts. R3. **Phase 2: Rebuilding & Dodgeball:** - **Rebuilding Rules for TA:** - An agent of TA within 0.5m of a scattered stone executes `pick_up_stone(stone_id)` (can carry up to 2 stones). - An agent of TA within 0.5m of (0,0) holding a stone executes `place_stone()` to increment tower stack H←H+1 (takes 3 ticks to place). - **Hunting Rules for TB:** - An agent of TB within 0.5m of the ball executes `pick_up_ball()`. - The ball-carrier cannot move (V=0 while holding ball) and must choose to `pass_ball(teammate_id)` or `throw_at_attacker(target_agent_id)`. - Ball flight is a linear raycast vector; if ball collides with an active TA agent, that agent is eliminated (`status = eliminated`). R4. **Round Resolution & Victory:** - **Attacker Win:** If H reaches 7, TA executes `call_taqchab()`. TA earns +1 point and retains attacking role. - **Defender Win:** If all K agents of TA are eliminated while H<7, TB earns +1 point and becomes attacking team for next round. - [gap-fill] The first team to reach 3 round points wins the match. ## Edge cases - **Tie at the end condition:** Not applicable — round wins are strictly binary and mutually exclusive. - **A player with no legal move:** Movement, stone collection, or ball passing is always available while active. - **Repetition / cycles:** Bounded by a hard tick limit in Phase 2 (Tmax⁡=500 ticks, ~100 seconds). [gap-fill] If time expires before tower completion or full elimination, the defenders win the round. - **Simultaneous claims on the same resource or position:** If two agents reach a stone on the same tick, possession is awarded to the agent with higher agility attribute. - **Player elimination mid-round; turn order repair:** Eliminated TA agents drop any held stones at their current position and exit the field. - **Resource exhaustion:** Exactly 7 stones and 1 ball; field boundaries reflect out-of-bounds balls. - **Termination guarantee:** Guaranteed by finite tick limit Tmax⁡=500 per round and target match score of 3 points. ## State representation - **Persistent state:** Team scores (SA,SB), current attacking team ID, match phase ∈{1,2,ended}. - **Field & Object state:** Tower height H∈[0,7], positions of all 7 stones, position and velocity of the ball, ball holder ID (or null). - **Agent state:** Position (Xi,Yi), velocity, held stones count ∈[0,2], status ∈{active,eliminated}. - **Observable information:** Fully observable state for all agents. ## Action space - `move(dx, dy)`: Continuous movement vector (valid only for non-ball holders in TB, and all active TA). - `throw_ball(target_x, target_y, power)`: Valid for active ball holder. - `pick_up_stone(stone_id)` / `place_stone()`. ## Playability notes - **Single-player-vs-AI:** Excellent as human attacker (dodging and restacking under pressure) or human defender (coordinating passing and sniping rebuilders). - **Group games (N=8):** Multi-agent cooperative-competitive environment with distinct roles. - **Physical-skill games:** Ball throws and stone placement times parameterized with noise distributions. - **What is lost in the adaptation:** The physical sting of a rubber ball on the shoulder and the exhilarating chaos of scrambling on loose gravel. ## Implementation hints - Implement Phase 2 as a standard 2D top-down dodgeball/capture-the-flag state machine. - First milestone: Implement 1v1 Phase 2 (1 Attacker attempting to stack 3 stones vs 1 stationary Defender throwing balls) before scaling to 4v4 team passing.

Download as JSON

Download the full game corpus entry for this game as structured JSON.

Download JSON
Cite this page

Moroccan stone-stacking target throw (Rmi l-Ahjar) (Morocco). (n.d.). Games of Countries. https://gamesofcountries.com/games/ma-morocco/taqchab

@misc{gamesofcountries-ma-morocco-taqchab,
  title = {Moroccan stone-stacking target throw (Rmi l-Ahjar) (Morocco)},
  year = {n.d.},
  publisher = {Games of Countries},
  url = {https://gamesofcountries.com/games/ma-morocco/taqchab}
}