Skip to main content
Formal Specification

King of the Stone — Formal Specification

Estonia · wrestling-combat · Confidence: medium

← Back to game page

Implementation Suitability

Suitability: adaptation-requiredFidelity: probabilistic-proxyGap-fills: 8
# Kivikuningas (King of the Stone) — AI-optimized specification ## General idea A physical hill-defense and grappling contest played around an elevated stone. One player occupies the boulder summit as King, defending against continuous simultaneous assaults from ground challengers; challengers use grappling, pushing, and pulling techniques to dislodge the King and claim the elevated throne. ## Formal model - **Abstraction taken:** The continuous 3D physical grappling on an erratic boulder is replaced by discrete combat ticks where the King selects a defensive stance and Challengers select assault vectors, resolved by a stochastic physical balance and dislodgement resolver. - **Player/agent count:** 1 King (K), N Challengers (C1…CN, N≥2). Total agents =N+1. - **Turn model:** Simultaneous discrete action rounds resolved synchronously every tick. ## Formal rules R1. Topological Setup: - The stone is modeled as a central elevated node Zsummit with capacity =1. - Surrounding ground area is modeled as M perimeter approach sectors Z1…ZM [gap-fill: parameterized as M=4 cardinal approach sectors]. - At start, 1 agent occupies Zsummit with King status; all other agents occupy ground sectors. R2. Defensive & Offensive Action Submission: - Each tick, the King selects a defense stance: `BRACE_CENTER`, `DEFEND_SECTOR(i)`, or `COUNTER_PUSH(i)`. - Each Challenger at sector i independently selects an assault action: `STRENGTH_PUSH`, `LEVERAGE_PULL`, `FLANK_CLIMB`, or `REST`. R3. Dislodgement Resolution: - Net assault force on the King: Fassault=∑j∈AssaultSj⋅M(actionj,stanceK)+ϵ, where Sj is agent strength, M is a technique matchup multiplier, and ϵ∼N(0,σ2) [gap-fill: matchup matrix defined over 3 stances × 3 assault types]. - King defensive resistance: Rking=SK⋅Belevation⋅StanceBonus, where Belevation=1.4 represents the mechanical advantage of high ground [gap-fill: height advantage multiplier fixed at 1.4]. - If Fassault>Rking: The King loses balance and is dislodged to ground level (Zsummit←VACANT). R4. Throne Succession: - When Zsummit becomes vacant, the challenger who contributed the highest effective force arg⁡maxj⁡(Sj⋅M) immediately ascends to Zsummit [gap-fill: succession awarded to highest force contributor; ties broken by lowest agent ID]. - The new King receives a 1-tick stabilization grace period (`STABILIZING`). R5. Scoring and Victory: - Each tick spent holding Zsummit awards 1 Reign Point to the active King. - [gap-fill: The match terminates when any agent accumulates Ptarget=50 Reign Points, or after Tmax=200 ticks, with the highest point total winning]. ## Edge cases - Tie at the end condition: If two agents finish Tmax with equal Reign Points, victory goes to the agent holding Zsummit at t=Tmax [gap-fill: tiebreaker on final occupancy]. - A player with no legal move: Not applicable; agents always have stance or attack actions available. - Repetition / cycles: Bounded by the monotonic accumulation of Reign Points and the hard tick limit Tmax [gap-fill: cycle bound via score ceiling and tick cap]. - Simultaneous claims on the same resource or position: When the summit is vacated, multiple challengers contest it; succession is resolved deterministically by force contribution and ID tiebreaker in R4. - Player elimination mid-round; turn order repair: Challengers may drop out dynamically without disrupting the state; the summit node remains stable. - Resource exhaustion: Not applicable; no consumable physical tokens. - Termination guarantee: Enforced by the finite tick limit Tmax and monotonic point progression [gap-fill: termination guarantee via finite tick cap]. ## State representation - Persistent state: - `king_id`: Agent ID currently on Zsummit. - `reign_points`: Map of Agent ID → Integer score. - `agent_strengths`: Map of Agent ID → Float strength scalar. - `tick_counter`: Integer t∈[1,Tmax]. - Per-tick ephemeral state: - `king_stance`: Selected defense posture. - `challenger_actions`: Map of Challenger ID →(sector,action). - `force_contributions`: Map of Challenger ID → Float force. - Observable information: Current King ID, reign points, and sector positions are fully observable; current-tick submitted actions are revealed simultaneously at resolution. ## Action space - `select_stance(stance_type)`: (King) Choose `BRACE_CENTER`, `DEFEND_SECTOR(i)`, or `COUNTER_PUSH(i)`. - `assault(sector, action_type)`: (Challenger) Choose `STRENGTH_PUSH`, `LEVERAGE_PULL`, `FLANK_CLIMB`, or `REST`. ## Playability notes - Single-player-vs-AI: Natural and engaging. Human King defending against coordinated AI assaults, or human challenger timing coordinated flank attacks with AI peers. - Group games (n>4): Reduces to 1 King vs 1 Challenger without structural breakdown, though 1v1 loses multi-attacker coalition dynamics. - Physical-skill games: Physical balance and upper-body wrestling are parameterized into strength scalars and stance-matchup payoff matrices. - What is lost in the adaptation: The tactile grip on rough granite, physical balance adjustments against gravity, and the vocal taunt exchanges. ## Implementation hints Treat sector assaults as an aggregate vector sum. First milestone: Implement 1v1 King defense with stochastic balance checks before adding multi-sector coordination and multi-challenger force pooling.

Download as JSON

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

Download JSON
Cite this page

King of the Stone (Estonia). (n.d.). Games of Countries. https://gamesofcountries.com/games/ee-estonia/kivikuningas

@misc{gamesofcountries-ee-estonia-kivikuningas,
  title = {King of the Stone (Estonia)},
  year = {n.d.},
  publisher = {Games of Countries},
  url = {https://gamesofcountries.com/games/ee-estonia/kivikuningas}
}