Skip to main content
Formal Specification

Marbles — Formal Specification

Brazil · dexterity-small · Confidence: high

← Back to game page

Implementation Suitability

Suitability: adaptation-requiredFidelity: probabilistic-proxyGap-fills: 3
# Bolinha de gude — AI-optimized specification ## General idea Marbles, played as a capture game: a shooter marble is flicked at target marbles in an agreed zone, and a hit transfers ownership. The decision content is target selection and shot ordering under an accuracy model that degrades with distance — a small combinatorial problem wrapped in a physical one. ## Formal model - **Abstraction taken:** the flick is replaced by an aim point plus a spread that widens with distance; marbles are points on a plane rather than rolling bodies, so ricochets and clusters are not modelled. - **Player/agent count:** 2 or more, individually owned marble pools. - **Turn model:** strictly sequential, clockwise. ## Formal rules R1. Players agree a target zone (hole, circle, or line) and deposit stake marbles in it. R2. Each player nominates one marble as its shooter (*bolinha de jogo*); the shooter is never captured. R3. A turn is one `flick(aim_point)` from the agreed firing line, resolved as a landing point drawn around the aim with distance-dependent spread. R4. A landing point within capture radius of a target marble captures it; the captured marble leaves play and joins the shooter's pool. R5. [gap-fill] Exactly one marble is captured per flick — the nearest within radius. The sources do not say whether a single shot can take several marbles; taking one keeps the rule unambiguous and can be stripped. R6. Turn passes clockwise regardless of hit or miss. R7. [gap-fill] Crossing the firing line with the hand is a foul costing the turn. The entry explicitly marks foul consequences undocumented; a rule is needed because without one the firing line has no force. R8. The game ends when the target zone is empty. The player holding the most captured marbles wins. ## Edge cases - **Tie at the end condition:** equal captures is a real possibility with an even stake. Resolve by a single sudden-death flick at a marble replaced in the zone; whoever hits first wins. - **Player with no legal move:** cannot occur — a player may always flick, even hopelessly, and the shooter is never lost. - **Repetition / cycles:** no cycles. Every capture strictly reduces the marbles in the zone, and misses do not restore them. - **Simultaneous claims:** turns are strictly sequential, so two players never contest the same marble. If a landing point is within radius of two marbles, R5 awards the nearer. - **Mid-round elimination:** there is none. A player who has captured nothing still holds a shooter and keeps taking turns. - **Resource exhaustion:** the stake marbles are the resource; their exhaustion is the end condition (R8). - **Termination guarantee:** the zone holds a finite number of marbles, captures are irreversible, and every capture removes one. [gap-fill] If no capture occurs for a full round of turns, players step the firing line one unit closer, which forces the capture probability upward and guarantees termination even with poor shooters. ## State representation Persistent: firing line, target zone geometry, capture radius. Per-player: shooter identity, captured-marble count, skill parameter. Per-turn ephemeral: the aim point and its resolved landing point. Information set: fully observable. All marble positions and all pools are open. ## Action space - `flick(aim_point: Vector2)` — precondition: it is the actor's turn; at least one marble remains in the zone. - `choose_shooter(marble_id)` — precondition: setup phase only. ## Playability notes - **Single-player-vs-AI:** natural. Target selection under a known spread model is a clean optimisation, and a greedy expected-value agent plays it well. - **Group games (n>2):** already n-player and needs no reduction; the game is a sequence of independent shots at a shared pool, so removing players changes only the turn order. - **Physical-skill model:** one parameter — spread as a function of distance and skill. That is the whole physical model. - **What is lost:** cluster dynamics. Real marbles scatter each other, which is why players aim at the edge of a pack rather than its centre. Treating marbles as points removes that entire layer of tactics. ## Implementation hints Represent marbles as points with a capture radius rather than simulating collision; the game is decided by aim choice, not by physics fidelity. The obvious trap is letting the spread model be distance-independent, which makes far shots as good as near ones and destroys the only real decision. First milestone: two players, fixed stake, greedy targeting, and confirm the closer-line rule terminates the game.

Download as JSON

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

Download JSON
Cite this page

Marbles (Brazil). (n.d.). Games of Countries. https://gamesofcountries.com/games/br-brazil/bolinha-de-gude

@misc{gamesofcountries-br-brazil-bolinha-de-gude,
  title = {Marbles (Brazil)},
  year = {n.d.},
  publisher = {Games of Countries},
  url = {https://gamesofcountries.com/games/br-brazil/bolinha-de-gude}
}