Skip to main content
Formal Specification

Qatari Marble Hole and Ring Game — Formal Specification

Qatar · dexterity-throw · Confidence: low

← Back to game page

Implementation Suitability

Suitability: adaptation-requiredFidelity: probabilistic-proxyGap-fills: 2
# Al-Telah (التله) — AI-optimized specification ## General idea A marbles game in which **the right to shoot must be won separately from the shooting itself**. Striking an opponent's marble captures it, but only the "hunter" may strike, and hunter status is earned by pitching a marble into a small hole from four metres — so a missed strike does not merely end a turn, it returns the whole table to a pitching contest that anyone may win. The hole is a gate that reopens after every failure. ## Formal model - **Abstraction taken:** Real thumb-flick force, aim, and rolling behaviour on sand are collapsed into two stochastic checks — a pitch-into-hole probability from the 4 m line and a strike probability against a field marble at a given distance — since the entry describes technique qualitatively with no numeric model. The 8 cm hole and 4 m line are taken as stated (entry §Players & materials). - **Player/agent count:** 2-6 players. Each contributes 2-4 marbles to a common field pool at stake; the shooter marble *Al-Rahi* is personal equipment and is never captured. - **Turn model:** Alternating phases rather than fixed turns — a pitching contest open to all players, followed by a single hunter's strike attempts. ## Formal rules R1. Setup (entry §1): a shallow hole is dug; each player contributes 2-4 marbles to the field, which are scattered as targets. All players pitch from the 4 m line. R2. Pitching contest / *Al-Moot* (entry §2): all eligible players submit `pitch_at_hole()`, each resolving a stochastic entry check. The first player whose marble enters the hole gains `hunter` status and the right to shoot. R3. Strike (entry §3.1-3.2): the hunter submits `strike(target_marble)`, flicking their shooter from the hole at a marble lying on the field. This resolves a stochastic hit check. On success the struck marble is **captured** — removed permanently from the field and added to the hunter's won pile. R4. Continuation: a successful strike leaves the hunter in possession of the role, and they may strike again [gap-fill: the entry states only that a *miss* passes the turn (§3.3), and is silent on whether a hit grants another shot. Continuation-on-success is assumed, as it is what makes the hunter role worth winning and is the near-universal convention in capture-marbles games; the alternative reading changes pacing but not termination]. R5. Miss (entry §3.3): a failed strike revokes `hunter` status and returns play to R2 — a fresh pitching contest, open to all players, decides the next hunter. R6. Field depletion: captured marbles never return to the field. The field pool is strictly non-increasing over the whole game. R7. Game end and victory (entry §4): play continues until the field pool is empty; the player holding the most captured marbles wins [gap-fill: the entry names the victory metric but not the stopping point. Exhaustion of the field is the only terminal state the rules can reach, since every capture removes a marble and nothing replaces one]. ## Edge cases - Tie at the end: two or more players finishing with equally many captured marbles is unaddressed by the entry. Genuine silence — no tiebreak is stated, and none is invented here; an implementation should surface a shared win rather than manufacture a decider. - A player with no legal move: not applicable — during a pitching contest every player may always `pitch_at_hole()`, and a hunter with any marble remaining on the field may always `strike()`. If the field is empty the game has already ended by R7. - Repetition / cycles: pitch-miss-pitch cycles (R2, R5) may repeat arbitrarily many times with no state change at all. This is the one genuinely unbounded loop in the game and is handled by the hazard argument below rather than by any rule in the entry. - Simultaneous claims on one position: two marbles entering the hole on the same pitching round is possible in principle; R2's "first player whose marble enters" implies pitches are ordered, so the earlier pitch takes precedence and the contest admits exactly one winner. Field marbles occupy distinct positions and are struck individually. - Elimination mid-round and turn-order repair: no player is ever eliminated. A player whose contributed marbles have all been captured still participates fully — they may still win hunter status and capture others' marbles — so no turn-order repair is required. - Resource exhaustion: **this is the game's terminal condition, not a degenerate case.** The field pool is the consumable, it strictly decreases (R6), and its exhaustion ends the game (R7). Personal shooter marbles are never consumed. - Termination guarantee: **guaranteed.** The field pool is finite (2-4 marbles × 2-6 players) and strictly non-increasing, and never replenished (R6). Each pitching contest has a fixed positive probability that some player enters the hole, so a hunter is established with probability 1 in finite expected rounds; each strike then has a fixed positive probability of capturing, which decrements the pool. The pool therefore reaches zero with probability 1 in finite expected time, at which point R7 resolves the winner deterministically from the captured counts. ## State representation - Persistent (game) state: `field_marbles` (set, strictly shrinking), `captured[p]` (monotone non-decreasing count per player), `hunter` (player id or none). - Per-phase ephemeral state: `phase` ∈ {pitching, striking}, `shooter_position` (at the hole during striking), positions of remaining field marbles. - Observable information: fully observable — the field, the hole, and every player's captured pile are open on a sand patch. No hidden information. ## Action space - `pitch_at_hole()`: any player; precondition: `phase = pitching`. Resolves the hole-entry check that confers `hunter`. - `strike(target_marble)`: the hunter only; precondition: `phase = striking` and `target_marble ∈ field_marbles`. Resolves the capture check. ## Playability notes - Single-player-vs-AI: natural. The only decision a player ever makes is *which* field marble to target — near ones are easier, clustered ones may enable follow-ups — so a human-versus-AI match is a clean comparison of target-selection policy under identical hit models. - Reducing n > 4 to 2 agents: works, but changes the character of R2. With six players the pitching contest is a genuine scramble; with two it is close to alternating attempts, and the drama of losing the hunter role to a rival largely evaporates. - Physical-skill games: thumb-flick accuracy and force control are the entire game and are collapsed into two probability checks (R2, R3). No rolling physics, surface friction, or marble-on-marble collision is modelled, which also removes any notion of a shot that captures while leaving the shooter well placed. - What is lost: the tactile precision of the flick, the sand-surface reading that decides whether a marble rolls true, and the real stakes of the game — children playing for marbles they actually own and can actually lose. ## Implementation hints State is small (a shrinking set of field positions plus per-player capture counts), and branching factor equals the number of marbles remaining on the field, so it shrinks naturally as the game proceeds. The interesting modelling choice is making the strike probability distance-dependent, which turns target selection from a formality into a real risk-reward decision — a distant marble is worth the same one point but forfeits the hunter role more often. The representational trap is treating the shooter marble as capturable; it is personal equipment and removing it from a player breaks R2 for them permanently. Suggested first milestone: flat probabilities and two players, verifying that the field pool monotonically drains and the game ends — then add distance-dependence and check that target choice starts to matter.

Download as JSON

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

Download JSON
Cite this page

Qatari Marble Hole and Ring Game (Qatar). (n.d.). Games of Countries. https://gamesofcountries.com/games/qa-qatar/al-telah

@misc{gamesofcountries-qa-qatar-al-telah,
  title = {Qatari Marble Hole and Ring Game (Qatar)},
  year = {n.d.},
  publisher = {Games of Countries},
  url = {https://gamesofcountries.com/games/qa-qatar/al-telah}
}