Formal Specification
Dutch Marbles — Formal Specification
Netherlands · dexterity-small · Confidence: low
← Back to game pageImplementation Suitability
Suitability: engine-readyFidelity: probabilistic-proxyGap-fills: 4
# Knikkeren — AI-optimized specification
## General idea
A sequential 2D spatial dexterity contest where agents navigate a marble across a continuous bounded arena into a central hole to become "active." Once active, agents hunt down and strike opposing marbles to eliminate them from the field.
## Formal model
- **Abstraction taken:** Physical thumb-flicking mechanics and surface friction are abstracted into a 2D vector shot model with parameterized error distribution: .
- **Player/agent count:** 2 to 6 individual agents.
- **Turn model:** Strictly sequential rotation order, with bonus turns awarded on successful hole entries or opponent strikes.
## Formal rules
R1. **Arena setup:** Flat 2D bounding area meters. A circular hole of radius m is centered at .
R2. **Throw-in phase:** At , all agents throw their marble from the baseline toward the hole. Turn order is set by ascending distance to the hole: .
R3. **Turn execution:** On agent 's turn, if agent is active/alive, it selects an action: `flick(angle, force)`.
R4. **Activation rule:** If agent 's marble comes to rest inside (or passes through with speed below capture threshold m/s), `is_activated[i]` becomes `true`, and agent receives 1 immediate bonus flick [gap-fill].
R5. **Elimination rule:** If `is_activated[i] == true` and the trajectory of marble collides with marble ():
- Agent is immediately eliminated (`is_alive[j] = false`).
- Marble is removed from the arena.
- Agent receives 1 immediate bonus flick [gap-fill].
R6. **Missed shot:** If a flick results in neither hole entry nor a legal strike, the marble rests at its final rest position, and turn passes to the next active player in rotation.
R7. **Boundary rule:** If a marble rolls out of the arena , it is placed at the point of boundary exit [gap-fill].
R8. **Win condition:** The game ends when exactly one agent has `is_alive == true`. That remaining agent is declared the winner.
## Edge cases
- **Tie at the end condition:** Not applicable; elimination is strictly sequential, leaving a single final survivor.
- **A player with no legal move:** Not applicable; any living agent can choose any `(angle, force)` vector on their turn.
- **Repetition / cycles:** To prevent indefinite cycling of mutual misses, if , the arena boundary shrinks by each round until resolution [gap-fill].
- **Simultaneous claims on the same resource or position:** Not applicable; turns are sequential.
- **Player elimination mid-round; turn order repair:** Eliminated agent is immediately marked inactive; rotation order simply skips on all subsequent cycles.
- **Resource exhaustion (pieces, tokens, space, time):** Not applicable; marble count decrements monotonically toward 1.
- **Termination guarantee:** Monotonic elimination of agents combined with the maximum turn limit / shrinking arena boundary guarantees game termination.
## State representation
- **Persistent state:** Arena dimensions, turn index, round counter , list of active agents.
- **Per-agent state:** Marble position , status flags (`is_alive`, `is_activated`), marble radius m.
- **Observable information:** Fully observable; all marble positions, activation states, and distances are public.
## Action space
- `flick(angle, force)`: Angle , Force magnitude N. Precondition: agent is alive and currently active in turn rotation.
## Playability notes
- **Single-player-vs-AI:** Natural; 1 human vs. 1–5 AI agents. AI computes aiming vectors toward the hole (if inactive) or nearest opponent (if active).
- **Group games (n>4):** Supports up to 6 players natively without rule modifications.
- **Physical-skill games:** Thumb-flicking dexterity is modeled by Gaussian noise inversely proportional to agent skill rating.
- **What is lost:** Micro-topography of dirt pits, spin/english on marble trajectories, and tactile thumb grip variations are simplified into standard friction equations.
## Implementation hints
- Low computational complexity; requires 2D point-circle collision detection and standard linear drag deceleration equations.
- First milestone: Implement 2-player 2D field with hole activation and collision elimination before adding multi-player turn rotation and arena boundary shrinkage.
Download as JSON
Download the full game corpus entry for this game as structured JSON.
Download JSONCite this page
Dutch Marbles (Netherlands). (n.d.). Games of Countries. https://gamesofcountries.com/games/nl-netherlands/knikkeren
@misc{gamesofcountries-nl-netherlands-knikkeren,
title = {Dutch Marbles (Netherlands)},
year = {n.d.},
publisher = {Games of Countries},
url = {https://gamesofcountries.com/games/nl-netherlands/knikkeren}
}