Skip to main content
Formal Specification

The Dock Stone — Formal Specification

Jersey · dexterity-throw · Confidence: low

← Back to game page

Implementation Suitability

Suitability: engine-readyFidelity: probabilistic-proxyGap-fills: 3
# Lé Doque — AI-optimized specification ## General idea A dynamic target-pitching and territory retrieval game where throwers attempt to dislodge a balanced target stone (*doque*) from a base boulder. When the target is felled, a scramble phase begins: throwers sprint to recover their fallen stones and retreat across a baseline before the guard can re-erect the target and tag them. The core tension is risk management: throwing close to the base stone provides better odds of hitting, but leaves the stone deeper in danger territory when attempting recovery. ## Formal model - **Abstraction taken:** The continuous physical throw is modeled as an aim-versus-accuracy probability distribution determining target strike probability and landing coordinate. The scramble/tag phase is discretized into sequential distance-speed checks based on field coordinates. - **Player/agent count:** 3 to 8 players (1 designated Guard, remainder Throwers). - **Turn model:** Sequential pitching phase, followed by an event-driven simultaneous or prioritized scramble phase upon target dislodgement. ## Formal rules R1. Setup: A baseline is established at y=0, and the target pedestal is fixed at coordinate (0,D) where D=12 metres. The target stone status is `UPRIGHT`. R2. Initial Guard assignment: All players throw one stone towards the pedestal; the player with the greatest Euclidean distance from the pedestal is assigned the `GUARD` role; all other players are `THROWERS`. R3. Pitching phase: Active throwers take turns pitching their stone (*galot*) from y≤0 toward (0,D). R4. Throw resolution: - If throw strikes target (probability Phit(d)): Target status transitions to `DOWN`. All throwers with stones in the field enter `RETRIEVAL` state. - If throw misses: Stone rests at landing coordinates (xi,yi). Thrower enters `WAITING` state; stone cannot be touched while target is `UPRIGHT`. R5. Scramble phase (when target is `DOWN`): - The Guard must execute `RESET_TARGET`, which requires moving to (0,D) and spending Treset ticks. - Throwers in `RETRIEVAL` state simultaneously declare movement vectors toward their stone coordinate (xi,yi) and subsequently toward y≤0. R6. Tagging resolution: - While target is `DOWN`, Guard cannot tag any thrower. - Once target is restored to `UPRIGHT`, Guard may tag any thrower located at y>0 who is currently in contact with their stone or moving back to baseline. - If Guard tags a thrower before that thrower crosses y=0 with their stone, that tagged thrower immediately becomes the new `GUARD` [gap-fill: roles swap immediately upon successful tag, and all stones are returned to owners]. R7. [gap-fill] Point scoring and game end: Each successful round where a thrower knocks the target down and recovers their stone across the baseline earns 1 point. A game terminates when a thrower reaches 5 points or after a fixed round limit (e.g., 20 rounds). ## Edge cases - Tie at the end condition: If multiple throwers reach the winning point threshold in the same round, the thrower with the fewest total guard assignments wins; if still tied, a sudden-death pitch closest to the target breaks the tie. - A player with no legal move: Not applicable; an active thrower behind the baseline always has a legal pitch action, and an agent in the field always has a movement vector. - Repetition / cycles (and the loop-breaking rule): If all throwers miss and all stones are stranded in the field, [gap-fill] the Guard must perform a "blind turn" facing away from the field for 5 seconds, during which throwers may attempt a stealth retrieval. - Simultaneous claims on the same resource or position: Physical locations in the field are continuous 2D coordinates; if two stones collide, both remain at their final resting coordinates without penalty. - Player elimination mid-round; turn order repair: No player elimination; if a player leaves the match, thrower rotation adjusts sequentially without affecting the Guard. - Resource exhaustion (pieces, tokens, space, time): Each player has exactly one personal stone; stones are never removed from play, only repositioned. - Termination guarantee: Bounded by the round cap (R7) and strictly non-decreasing player point tallies upon successful retrievals. ## State representation - Persistent state: - `guard_id`: Index of current Guard agent. - `scores`: Map of player ID → integer score. - `round_number`: Integer counter. - Ephemeral state (per round): - `target_status`: Enum (`UPRIGHT`, `DOWN`). - `stone_positions`: Map of player ID →(x,y) coordinate or `IN_HAND`. - `player_states`: Map of player ID → (`READY`, `WAITING`, `RETRIEVING`, `SAFE`, `GUARD`). - Observable information: Fully observable public state; all stone coordinates, player positions, target status, and scores are visible to all agents. ## Action space - `pitch(power, angle)`: Available to active thrower behind baseline. Consumed by the physics/stochastic trajectory model. - `sprint_to(x, y)`: Available to all active field agents during scramble phase. - `grab_stone()`: Available to thrower when within distance ϵ of their stone coordinates. - `reset_target()`: Available to Guard when within distance ϵ of pedestal (0,D). - `tag(player_id)`: Available to Guard when target is `UPRIGHT` and Guard is within reach distance of target player at y>0. ## Playability notes - Single-player-vs-AI: Natural and highly engaging; 1 human thrower against an AI Guard and 2 AI throwers. AI agents evaluate risk-reward based on distance to stone vs. Guard reset timing. - Group games (n>4): Scales naturally up to 8 players without modifying game structure; more throwers increases the chaos and opportunity during the scramble phase. - Physical-skill games: Modeled via 2D Gaussian landing distribution around aim point: σ(d)=k⋅d, where skill parameter reduces variance. - What is lost in the adaptation: Physical dexterity of stone selection, uneven ground deflection, and physical athletic body-checking or dodging during sprints. ## Implementation hints - State space is small and 2D-geometry based. - Collision detection between Guard and Throwers can be simplified to radius checks: dist(Guard,Thrower)≤Rtag. - Recommended milestone: Implement the deterministic turn state machine (pitching → target fall → reset/tagging) with static coordinates before adding continuous movement vectors.

Download as JSON

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

Download JSON
Cite this page

The Dock Stone (Jersey). (n.d.). Games of Countries. https://gamesofcountries.com/games/je-jersey/le-doque

@misc{gamesofcountries-je-jersey-le-doque,
  title = {The Dock Stone (Jersey)},
  year = {n.d.},
  publisher = {Games of Countries},
  url = {https://gamesofcountries.com/games/je-jersey/le-doque}
}