Formal Specification
Hat-stealing foot chase — Formal Specification
Azerbaijan · chase-tag · Confidence: medium
← Back to game pageImplementation Suitability
Suitability: adaptation-requiredFidelity: discretizedGap-fills: 2
# Papaqaldıqaç — AI-optimized specification
## General idea
A "keep away" tag game where the tagged object, not player position, determines who is vulnerable: the Chaser may only meaningfully tag whoever currently holds the hat, so field players constantly re-route possession via passes to stay ahead. A distinctive interception rule breaks the usual tag logic — if the Chaser catches an airborne pass, the *thrower*, not the intended catcher, becomes the new Chaser, since they are the one who put the hat within the Chaser's reach.
## Formal model
- **Abstraction taken:** Real sprint speed, passing accuracy, and tackle/tag contact are abstracted into stochastic per-attempt checks (pass success/failure/interception, tag success), since the entry describes them qualitatively without numeric models.
- **Player/agent count:** 1 Chaser, N Field players, N in [2, 10].
- **Turn model:** Synchronous ticks; all agents act simultaneously each tick.
## Formal rules
R1. Setup (entry §1.1-1.2): players gather loosely; the initial Chaser starts as the hat's owner, and one Field player submits `snatch()`, taking the hat and becoming the initial hat holder as they sprint away.
R2. Hat holder actions: each tick, the current hat holder may submit `move(direction)` or `pass_attempt(teammate_id)` (entry §2.2). A `pass_attempt()` resolves one of three stochastic outcomes: successful catch by the target, a dropped pass (hat falls to the ground at a position between thrower and target), or interception by the Chaser (R6) [gap-fill: the entry describes passing and ground-drops (§2.3) and interception (§4) as distinct possible outcomes but gives no probability model distinguishing them, so a three-way stochastic resolution is the minimal reading that accounts for all three named outcomes].
R3. Ground pickup (entry §2.3): if a pass is dropped, the hat becomes an unheld object at a fixed position; any Field player (including the Chaser is excluded, since only Field players hold the hat in this game's structure) may submit `pick_up()` while adjacent, becoming the new hat holder.
R4. Boundary foul (entry §2.4): if the hat holder's position crosses the outer boundary line while holding the hat, this is an immediate fault; treated identically to a successful tag (R5) for consequence purposes.
R5. Tag (entry §3.1-3.2): the Chaser may submit `tag(target_id)`; this only has an effect if `target_id` currently holds the hat (tagging a non-holder is a legal but inert action). A successful tag against the hat holder — or a boundary foul (R4) — makes that player the new Chaser.
R6. Role resumption (entry §3.3): the instant a new Chaser is established (R4 or R5), the previous Chaser immediately becomes a Field player and either retains the hat as its holder or submits an immediate `pass_attempt()` to another Field player; play resumes without pause, with no dedicated setup phase repeating R1.
R7. Interception (entry §4): if a `pass_attempt()` (R2) resolves as intercepted, the Chaser catches the hat and effectively swaps into the retrieving role of R6 — the Chaser becomes a Field player holding the hat, and the *thrower* of the intercepted pass becomes the new Chaser (not the intended catcher).
R8. Match end: the entry specifies no win condition, describing the activity as continuous energetic play (entry §5) [gap-fill: treated honestly — there is no formal terminal state, matching the entry's own framing rather than inventing a score threshold].
## Edge cases
- Tie at the end: not applicable — there is no scoring system or terminal state to tie at (R8).
- A player with no legal move: not applicable — the hat holder always has `move`/`pass_attempt` available; the Chaser always has `move`/`tag` available (even if inert against a non-holder); non-holding Field players always have `move` and, when adjacent to a dropped hat, `pick_up()`.
- Repetition / cycles: expected and structural — the Chaser role can rotate repeatedly among the same players via consecutive tags, fouls, or interceptions, consistent with the entry's own framing of continuous, non-terminating play (R8) rather than a flaw.
- Simultaneous claims on one position: not applicable — the hat has a single well-defined holder or ground position at all times; R2-R3 resolve possession changes one at a time.
- Elimination mid-round and turn-order repair: not applicable — no player is ever removed from the game; a role change (R5-R7) relabels the Chaser without eliminating anyone.
- Resource exhaustion: not applicable — no consumable resource; the hat is continuously reused.
- Termination guarantee: **not guaranteed.** The entry gives this game no win condition and describes it explicitly as continuous chase play (§5), matching the pattern of comparable "no formal endpoint" games in this batch. `termination_guaranteed: false` reflects this honestly rather than inventing a stopping rule the entry does not support.
## State representation
- Persistent (session) state: `chaser_id`.
- Per-tick ephemeral state: `hat_holder_id` (or `hat_on_ground_at(position)` if dropped), `positions` of all agents.
- Observable information: fully observable — all positions and hat status are public; no hidden information.
## Action space
- `snatch()`: any Field player, setup only (R1).
- `move(direction)`: any agent; always legal.
- `pass_attempt(teammate_id)`: the current hat holder only; precondition: holds the hat.
- `pick_up()`: any Field player; precondition: hat is on the ground and the player is adjacent.
- `tag(target_id)`: the Chaser only; precondition: none required to attempt, but only effective if `target_id` holds the hat (R5).
## Playability notes
- Single-player-vs-AI: natural on either side — human Chaser pursuing AI Field players' passing patterns, or human Field player managing pass timing against an AI Chaser's positioning.
- Reducing N > 4 to 2 agents: mechanically trivial (fewer passing options for the hat holder), but removes the tactical passing-network dynamic that gives the game its keep-away character.
- Physical-skill games: real sprint speed, passing accuracy, and tag reflexes are the entire game and are collapsed into stochastic checks (R2, R5); no genuine athleticism is modeled.
- What is lost: the actual sprint acceleration and decoy footwork of evading a chaser, the tactile drama of an intercepted pass, and the game's explicit cultural mirroring of the mounted `Papaq oyunu` reimagined as accessible pedestrian play.
## Implementation hints
State is minimal (a hat-holder pointer or ground position, agent positions, a Chaser pointer); the real design difficulty is calibrating the three-way pass-outcome distribution (caught / dropped / intercepted) and tag-success probability, neither of which the source quantifies. First milestone: implement the pass/tag/role-swap loop (R2-R7) with flat probabilities to validate the interception rule's thrower-becomes-Chaser logic (R7), then differentiate outcome probabilities by pass distance or Chaser proximity.
Download as JSON
Download the full game corpus entry for this game as structured JSON.
Download JSONCite this page
Hat-stealing foot chase (Azerbaijan). (n.d.). Games of Countries. https://gamesofcountries.com/games/az-azerbaijan/papaqaldiqach
@misc{gamesofcountries-az-azerbaijan-papaqaldiqach,
title = {Hat-stealing foot chase (Azerbaijan)},
year = {n.d.},
publisher = {Games of Countries},
url = {https://gamesofcountries.com/games/az-azerbaijan/papaqaldiqach}
}