Formal Specification
Equestrian hat-snatching game — Formal Specification
Azerbaijan · equestrian-team · Confidence: low
← Back to game pageImplementation Suitability
Suitability: adaptation-requiredFidelity: discretizedGap-fills: 1
# Papaq oyunu — AI-optimized specification
## General idea
A mounted pursuit-and-snatch duel whose distinguishing mechanic is a mid-round role reversal: the instant the Attacker snatches the hat, they become the one being chased, and the original Defender becomes the pursuer trying to recover it before a boundary line is crossed. A round can therefore be won by the Attacker completing the theft, or by the Defender either recovering the hat via counter-snatch or simply surviving the round's timer.
## Formal model
- **Abstraction taken:** Real galloping speed, saddle balance, and the precise hand-snatch motion are abstracted into stochastic per-attempt success checks, since the entry describes technique qualitatively without numeric models.
- **Player/agent count:** 2 mounted riders per duel (Attacker, Defender), or 2 teams of 4-6 competing in sequential 1v1 heats (team-composition rules beyond sequential heats not specified by the entry).
- **Turn model:** Synchronous ticks; both riders move simultaneously each tick, bounded by a fixed 2-minute round timer.
## Formal rules
R1. Setup (entry §1.1-1.2): the Defender (wearing the `papaq`) starts 10 m ahead of the Attacker at the starting line. On the referee's whistle, the Defender begins moving; the Attacker is released 2 seconds later.
R2. Pursuit: each tick, both riders submit `move(direction, speed)`. When the Attacker is within snatch range of the Defender, the Attacker may submit `snatch_attempt()` (entry §2.1-2.2), resolving a stochastic success check.
R3. Illegal actions (entry §2.3): `strike_opponents_mount`, `grab_reins`, `bite`, `ram_horses`. Any of these committed by a rider results in immediate round loss for that rider (disqualification), regardless of possession state.
R4. Snatch success and role reversal (entry §3.1-3.2): the instant `snatch_attempt()` succeeds, the Attacker becomes the `Escaper` (now holding the hat, sprinting toward the finish boundary) and the Defender becomes the `Pursuer` (chasing to recover it). The Pursuer may submit their own `snatch_attempt()` (same mechanic as R2, roles reversed) against the Escaper at any point before the boundary is crossed.
R5. Counter-snatch (entry §4.2, "or successfully defends the hat"): if the Pursuer's `snatch_attempt()` against the Escaper succeeds before the boundary is crossed, the round ends immediately and the original Defender scores +1 point — this is the formal reading of "successfully defends the hat" as an alternative win path to simply outlasting the timer [gap-fill: the entry does not explicitly state the round-ending consequence of a successful counter-snatch, but §4.2 names hat-defense as a scoring path distinct from the timer expiring, and a successful counter-snatch is the only event in the rules that constitutes "defending" the hat after it was already taken].
R6. Attacker win (entry §4.1): if the Escaper (original Attacker) carries the hat across the finish boundary before being counter-snatched (R5), the original Attacker scores +1 point. The round ends.
R7. Defender win by timer (entry §4.2): if the 2-minute round timer expires with the hat still in the Escaper's possession and the boundary not yet crossed, and no disqualification (R3) has occurred, the original Defender scores +1 point. The round ends.
R8. Round transition (entry §4.3): starting roles (Attacker/Defender) swap between the two riders for the next round.
R9. Match structure (entry §5): best-of-three rounds; the match ends the instant one rider has won 2 rounds.
## Edge cases
- Tie at the end: not applicable — each round resolves to exactly one scorer (R5, R6, or R7 are mutually exclusive and jointly exhaustive within the 2-minute window), and the match requires a clean 2-round majority (R9).
- A player with no legal move: not applicable — both riders always have `move`/`snatch_attempt()` (when in range) available throughout a round.
- Repetition / cycles: not applicable — the round is bounded by the fixed 2-minute timer (R7) regardless of how many failed `snatch_attempt()`s occur before it.
- Simultaneous claims on one position: not applicable — the hat has a single well-defined holder at all times; R2/R4's snatch mechanic resolves possession changes one at a time.
- Elimination mid-round and turn-order repair: not applicable — a disqualification (R3) ends the round outright rather than removing a rider mid-sequence; there is no turn order to repair since movement is simultaneous.
- Resource exhaustion: not applicable — no consumable resource beyond the round timer itself, which is the intended bounding mechanic.
- Termination guarantee: each round is bounded by a fixed 2-minute clock (R7) independent of the stochastic outcome of any individual snatch attempt, with two earlier stopping conditions (R5's counter-snatch, R6's boundary crossing) that can only shorten it. The match is a fixed sequence of at most 3 such rounds (R9), so it terminates in bounded, deterministic time regardless of in-round stochastic outcomes.
## State representation
- Persistent (match) state: `rounds_won[rider]`, `round_number`, `starting_roles` (swapped each round, R8).
- Per-round state: `hat_holder`, `role_state` (Attacker/Defender pre-snatch, or Escaper/Pursuer post-snatch), `time_remaining`, `disqualified[rider]`.
- Observable information: fully observable — all positions, hat possession, and elapsed time are public; no hidden information.
## Action space
- `move(direction, speed)`: either rider; precondition: round ACTIVE, not disqualified.
- `snatch_attempt()`: the Attacker (pre-snatch) or the Pursuer (post-snatch, R4); precondition: within snatch range of the hat holder.
- Illegal actions the referee model must recognize but that are never in the legal set: `strike_opponents_mount`, `grab_reins`, `bite`, `ram_horses` (R3).
## Playability notes
- Single-player-vs-AI: natural, one side of the duel vs an AI opponent managing pursuit angle and snatch timing; the mid-round role reversal (R4) gives a natural dramatic turning point for either a human Attacker or Defender.
- Team variant (`Komanda Papaq oyunu`): the entry names a team goal-circle format but gives it no rule detail beyond "two teams of 4 riders each attempt to snatch and carry the hat to their team goal circle" — this is a distinct enough structure (shared team objective vs. individual duel) that it is not formalized here beyond noting the sequential-heats reading used for the base 2-team format.
- Physical-skill games: real galloping speed, saddle balance, and hand-eye coordination for the snatch are the entire game and are collapsed into stochastic checks (R2, R4-R5); no genuine horsemanship is modeled.
- What is lost: the actual bond between rider and horse, the tactical galloping angles used to draw abreast of an opponent, and the cultural weight of the `papaq` as a symbol of honor that makes its playful theft and defense meaningful.
## Implementation hints
State is modest (positions, hat holder, role state, a round timer); the real design difficulty is calibrating snatch-success probability as a function of relative position/speed, which the source does not quantify. First milestone: implement one round with a flat snatch-success probability to verify the role-reversal mechanic (R4) and the three mutually exclusive round-ending paths (R5-R7), then wire up the best-of-three match structure (R9) and role swap (R8).
Download as JSON
Download the full game corpus entry for this game as structured JSON.
Download JSONCite this page
Equestrian hat-snatching game (Azerbaijan). (n.d.). Games of Countries. https://gamesofcountries.com/games/az-azerbaijan/papaq-oyunu
@misc{gamesofcountries-az-azerbaijan-papaq-oyunu,
title = {Equestrian hat-snatching game (Azerbaijan)},
year = {n.d.},
publisher = {Games of Countries},
url = {https://gamesofcountries.com/games/az-azerbaijan/papaq-oyunu}
}