Skip to main content
Formal Specification

Storks (One-Legged Pushing Duel / Zhuravel) — Formal Specification

Ukraine · strength-endurance · Confidence: low

← Back to game page

Implementation Suitability

Suitability: adaptation-requiredFidelity: probabilistic-proxyGap-fills: 4
# Buzky — AI-optimized specification ## General idea A one-legged balance-disruption duel: two agents hop within a small circle, arms locked across their chests, and use only shoulder contact to force the opponent to touch down, unfold their arms, or leave the circle. What makes it structurally distinct is that the only legal interaction channel is shoulder-to-shoulder contact while both agents are themselves balancing on a single point of support — there is no grappling, striking, or resource economy, only positioning and contact under a continuous balance constraint. ## Formal model - **Abstraction taken:** The continuous act of one-legged hopping and balance is abstracted into a per-tick "stability" value per agent that a contact event can push toward instability; a bump does not deterministically fell an opponent, it raises the probability of an imbalance event on that tick. This is a probabilistic proxy for real balance physics, not a physics simulation. - **Player/agent count:** 2 agents per bout (Player A, Player B). A group format (4-12) is built by running sequential 2-agent duels in a bracket or round-robin; the underlying duel logic is unchanged. - **Turn model:** Synchronous ticks. Both agents submit an action simultaneously each tick (move/bump/feint/wait); outcomes resolve at tick end. ## Formal rules R1. Setup: both agents are placed inside a circular arena of diameter D (2-3 m, per entry). Each agent selects and fixes a `support_leg` for the entire bout (R2/R6 of the entry: changing support foot mid-bout is not permitted without referee permission). R2. Both agents begin in state `arms_crossed = true`, `support_foot_down = true`, `raised_foot_down = false`, `in_circle = true`. R3. On the referee's start signal, the bout enters the ACTIVE phase; simultaneous per-tick actions are allowed until a loss condition is triggered (R6). R4. Legal actions per tick (entry Rules §5): `move(direction)` (hop toward/around the opponent on the support leg), `bump()` (attempt shoulder contact with an opponent within contact range), `feint()` (a move that provokes but does not commit to bump range). R5. Illegal actions (entry Rules §6, fouls): `arm_push`, `headbutt`, `kick_with_raised_foot`, `switch_support_leg` without referee permission. Any illegal action committed by an agent immediately ends the bout with that agent as the loser. [gap-fill: the entry does not state whether a foul is refereed as instant loss or a warning-then-loss; instant loss on first foul is assumed, since the entry lists fouls directly under prohibited actions with no warning mechanism described]. R6. Loss conditions (entry Rules §7), checked at the end of every tick in which a `bump()` was contested: an agent loses the bout the instant any of the following becomes true for it: (a) any body part other than the sole of the support foot touches the ground (including the raised foot, a knee, or a hand), (b) the agent's position crosses the arena boundary, (c) `arms_crossed` becomes false. R7. Contact resolution: when agent X executes `bump()` against agent Y in contact range on a tick, resolve a stochastic imbalance check for both X and Y (a well-placed bump can also cost the attacker their own balance): each contested agent independently rolls against an imbalance probability `p_imbalance` that increases with cumulative ticks in the ACTIVE phase (fatigue) and with the number of consecutive bumps received without recovery. [gap-fill: the entry describes the mechanic qualitatively ("bump/nudge/feint... force the opponent to lose balance") but gives no numeric probability model; a monotonically-increasing-with-fatigue probability is assumed to make the physical description testable]. R8. End of bout: the bout ends the instant one agent triggers a loss condition (R6); the other agent is declared the bout winner. If, on the same tick, both agents simultaneously trigger a loss condition, the bout is a draw for that bout only. [gap-fill: the entry does not address simultaneous double-loss; a draw-that-bout ruling is assumed as the least-invented resolution]. R9. Match structure: bouts are contested best-of-three (entry §8). The match ends the instant one agent has won 2 bouts; that agent wins the match. A bout drawn under R8 does not count toward either agent's win total and an additional bout is played in its place. ## Edge cases - Tie at the end: Handled at the bout level by R8 (simultaneous double-loss → drawn bout, replayed) and is therefore never a match-level tie, since the match requires a clean 2-bout majority (R9). - A player with no legal move: Not applicable — `move`, `bump`, `feint`, and implicitly holding position are always available to a balanced agent; there is no state in which an agent has zero legal actions. - Repetition / cycles: Not applicable in the strict sense (no position/state loop can repeat game state indefinitely) because `p_imbalance` is strictly non-decreasing with tick count (R7), so indefinite stalling drives the imbalance probability toward 1, not a stable cycle. - Simultaneous claims on one position: Not applicable — agents may occupy overlapping contact space during a bump by design (that is what a bump is); there is no exclusive-tile ownership rule in this game. - Elimination mid-round and turn-order repair: Not applicable to the 2-agent duel (a bout has exactly one loser and ends immediately, R8). In the 4-12 player bracket extension, an eliminated agent is simply removed from the bracket and remaining agents continue their scheduled duels — no mid-duel elimination occurs since duels are strictly 2-agent. - Resource exhaustion: Not applicable — there is no consumable resource (no stamina meter, item, or currency) in the entry's rules; only cumulative fatigue driving `p_imbalance`, which is a probability, not a depletable resource. - Termination guarantee: Each ACTIVE tick in which contact occurs carries a strictly positive, non-decreasing probability `p_imbalance` of ending the bout (R7). Since this probability is bounded away from 0 after any finite number of ticks (fatigue only increases), the probability that the bout has NOT ended by tick t decays to 0 as t → ∞ (a standard "eventually almost-sure" argument for a non-decreasing hazard rate). The bout therefore terminates with probability 1. The match is a fixed sequence of at most 3 such bouts (R9), so the match terminates with probability 1 as well. ## State representation - Persistent (match-level) state: `bouts_won[A]`, `bouts_won[B]`, `bout_number`. - Per-bout state: `support_leg[agent]` (fixed at bout start), `position[agent]`, `arms_crossed[agent]` (bool), `ground_contacts[agent]` (bool, any illegal body-part touch), `in_circle[agent]` (bool), `ticks_elapsed`, `p_imbalance[agent]` (derived from `ticks_elapsed` and recent bump history). - Observable information: Fully observable — both agents see each other's position, stance, and arm state at all times; there is no hidden information in this game. ## Action space - `move(direction)`: hop one step on the support leg toward a target direction within the circle. Precondition: `in_circle = true`, bout ACTIVE. - `bump()`: attempt shoulder contact against an opponent currently within contact range. Precondition: opponent within range, bout ACTIVE. - `feint()`: a move that enters near-contact range without committing to `bump()`, used to provoke an opponent's imbalance check without one's own contact roll. [gap-fill: the entry names feinting as a permitted action (§5.2) but does not specify its mechanical effect distinctly from `move`; treating it as a no-contact provocation with no direct imbalance roll is the minimal reading]. - `wait()`: hold current position; always legal. - Illegal/foul actions (not in the legal action set, but the referee model must recognize an agent attempting them): `arm_push`, `headbutt`, `kick_with_raised_foot`, `switch_support_leg`. ## Playability notes - Single-player-vs-AI: Natural. A human plays one side of the duel against an AI opponent that selects `move`/`bump`/`feint`/`wait` to manage its own `p_imbalance` while raising the human's. - Reducing group play (4-12) to 2 agents: Direct — the game's own structure is already 2-agent duels; the bracket/round-robin wrapper is a scheduling layer outside the core mechanic, not a change to it. - Physical-skill games: The entire game is a physical balance/strength contest. It is represented here only as a stochastic contact-probability proxy (R7); no true balance physics, footwork skill, or reaction time is modeled. - What is lost: The tactile skill of shoulder timing, real fatigue and proprioception, the social/festive framing of the referee's call-and-response start signal, and the qualitative texture of "feinting" as a genuine psychological/physical fake — all collapsed into a single probability parameter. ## Implementation hints Branching factor per tick is small and constant (4 legal actions × 2 agents = 16 joint outcomes before contact resolution), so the game is trivially tractable computationally; the actual design difficulty is entirely in calibrating `p_imbalance` so bouts feel skill-driven rather than coin-flip. First milestone: implement the 2-agent duel with a flat (non-fatigue-scaling) `p_imbalance` per contested bump, verify R6/R8/R9 termination and best-of-three scoring, then add the fatigue-scaling term from R7.

Download as JSON

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

Download JSON
Cite this page

Storks (One-Legged Pushing Duel / Zhuravel) (Ukraine). (n.d.). Games of Countries. https://gamesofcountries.com/games/ua-ukraine/buzky

@misc{gamesofcountries-ua-ukraine-buzky,
  title = {Storks (One-Legged Pushing Duel / Zhuravel) (Ukraine)},
  year = {n.d.},
  publisher = {Games of Countries},
  url = {https://gamesofcountries.com/games/ua-ukraine/buzky}
}