Skip to main content
Formal Specification

Kabi Kabi Running Ball Game — Formal Specification

Australia · ball-team · Confidence: low

← Back to game page

Implementation Suitability

Suitability: adaptation-requiredFidelity: discretizedGap-fills: 3
# Buroinjin — AI-optimized specification ## General idea An invasion game whose whole character comes from two constraints: a ball-carrier may run only about 10 metres before passing, and there is no tackling — only tagging, which forces a pass within 3 seconds. Together these make possession a timer rather than a contest of strength, and the game becomes about passing lanes. ## Formal model - **Abstraction taken:** the field becomes a grid and movement becomes cell steps per tick. The 10 m run limit becomes a step counter; the 3-second post-tag window becomes a fixed tick deadline. Interception is a probability along the pass lane. - **Player/agent count:** 2 teams of 6–8. - **Turn model:** ticked, simultaneous. All players move each tick; the carrier's pass resolves at end of tick. ## Formal rules R1. The pitch is a grid 50–70 units long by 30–40 wide, with a scoring zone at each end. R2. Play begins with a toss at the centre; possession goes to the winner. [gap-fill] The toss is modelled as a fair coin. R3. Each tick, every player may move one cell. The carrier additionally may `pass(teammate)`. R4. The carrier may move at most 10 cumulative cells while in possession. On reaching the limit the carrier must pass on the next tick or lose possession. R5. Passes are underarm or handball only, in any direction. Kicking and overhand throwing are illegal and are not in the action space. R6. A defender adjacent to the carrier may `tag()`. A tagged carrier must pass within 3 ticks or lose possession. R7. Tackling, tripping and collision are illegal; a defender may not enter the carrier's cell. R8. A pass is intercepted with probability rising in the number of defenders adjacent to the pass lane. [gap-fill] No interception model is given in the source; proportionality to lane coverage is the minimum assumption. R9. One point is scored by carrying the ball into the opponent's scoring zone, or catching a pass inside it. R10. The match ends at a set point target (11 or 21) or a fixed tick count. Highest score wins. R11. [gap-fill] There is no offside rule. The entry records offside as undocumented; adding one would change the geometry substantially, so none is imposed. ## Edge cases - **Tie at the end condition:** a timed match can end level. The point-target form cannot. For the timed form, play continues to the next point scored. - **Player with no legal move:** a carrier who is boxed in and has exhausted the run limit still has `pass` available to any teammate, and R8 permits a low-probability pass, so no deadlock arises. A non-carrier may always hold position. - **Repetition / cycles:** possession can cycle indefinitely without scoring. R4 and R6 bound how long any single possession lasts, and R10's tick cap bounds the match. - **Simultaneous claims:** two players moving into one cell resolve in favour of the team in possession, then by lower agent index. A pass and a tag landing on the same tick resolve tag first, which triggers R6 rather than cancelling the pass. - **Mid-round elimination and turn-order repair:** nobody is eliminated. Every player acts every tick, so there is no turn order to repair. - **Resource exhaustion:** the run allowance (R4) and the tag clock (R6) are the consumable resources; both reset on a completed pass. - **Termination guarantee:** R10's tick cap guarantees termination outright. Without it the point target alone would not, since a stalemate of endless passing is legal. ## State representation Persistent: grid dimensions, scoring zones, point target, tick cap. Per-player: team, cell, whether carrier. Per-turn ephemeral: ball position, run-cells used by the current carrier, ticks remaining on a tag, score. Information set: fully observable — this is an open-field game with nothing concealed. ## Action space - `move(direction)` — precondition: destination is on the pitch and not the carrier's cell if the actor is a defender. - `pass(teammate_id)` — precondition: actor is the carrier. - `tag()` — precondition: actor is a defender adjacent to the carrier. ## Playability notes - **Single-player-vs-AI:** natural with one agent per team choosing a joint action, or one agent as the carrier against scripted teammates. - **Group games (n>4):** reduces to 3v3 without losing the structure, since the run limit and tag clock — not team size — generate the tempo. - **Physical-skill model:** one parameter, interception probability as a function of lane coverage. Running and passing are otherwise exact. - **What is lost:** the kangaroo-skin ball's handling, and the judgement of when a tag has actually been made — in real play that is contested and social, and here it is a boolean. ## Implementation hints Implement the run limit and the tag clock before anything else; they are the game. A common trap is modelling this as rugby with tackling removed, which produces endless carrying — the 10-cell cap is what forces the passing game. Branching factor per player is small (4–8 moves plus a pass choice), but the joint action space across a team is large, so search over team-level joint actions needs pruning.

Download as JSON

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

Download JSON
Cite this page

Kabi Kabi Running Ball Game (Australia). (n.d.). Games of Countries. https://gamesofcountries.com/games/au-australia/buroinjin

@misc{gamesofcountries-au-australia-buroinjin,
  title = {Kabi Kabi Running Ball Game (Australia)},
  year = {n.d.},
  publisher = {Games of Countries},
  url = {https://gamesofcountries.com/games/au-australia/buroinjin}
}