Formal Specification
Sprint-and-Retrieve Running Contest — Formal Specification
Australia · strength-endurance · Confidence: low
← Back to game pageImplementation Suitability
Suitability: adaptation-requiredFidelity: probabilistic-proxyGap-fills: 3
# Tarnambai — AI-optimized specification
## General idea
A sprint against a moving target that must be collected without stopping. The interesting version is the traditional one: the object is wind-driven and therefore not controlled by any player, so the runner is intercepting a genuinely uncontrolled trajectory rather than a rolled ball.
## Formal model
- **Abstraction taken:** the object's motion becomes a position advancing per tick — under a partner's roll (decelerating) or under wind (variable). The pick-up-on-the-run requirement becomes a constraint that the runner's speed must be above zero at collection.
- **Player/agent count:** pairs, or small groups of 2–4, non-interacting except as timed rivals.
- **Turn model:** ticked within an attempt; attempts are sequential.
## Formal rules
R1. The object is released or rolled away from the start line.
R2. The object advances each tick: decelerating if rolled, or on a wind-driven path with variable speed and direction. [gap-fill] No wind model is attested; the traditional account says only that seed heads were blown along.
R3. The runner starts at the line and advances one cell per tick, up to a maximum speed.
R4. The object may only be collected after it has crossed the turn line.
R5. Collection requires the runner to be co-located with the object **while moving** — stopping to pick it up is not a legal collection.
R6. The runner returns to the start line carrying the object.
R7. Elapsed ticks are the score; fewest wins.
R8. [gap-fill] A failed collection may be re-attempted within the same run at the cost of ticks. The source does not address a fumble.
R9. [gap-fill] The traditional distance is not given; treat the turn line as a parameter.
## Edge cases
- **Tie at the end condition:** equal times are resolved by a re-run; no other criterion is attested.
- **Player with no legal move:** cannot occur — the runner may always continue running.
- **Repetition / cycles:** none. The object advances monotonically away and the run is a single out-and-back, so no state repeats.
- **Simultaneous claims:** in the relay and small-group forms, runners use separate objects and never contend. If a shared object is used, collection goes to the runner co-located first.
- **Mid-round elimination and turn-order repair:** nobody is eliminated; attempts are independent and sequential.
- **Resource exhaustion:** nothing is consumed; only elapsed time accumulates.
- **Termination guarantee:** guaranteed. The object's travel is finite (a rolled ball decelerates to rest; a wind-blown head leaves the field), and the runner's speed is bounded below, so every attempt ends.
## State representation
Persistent: start line, turn line distance, object type (rolled or wind-driven).
Per-runner: position, speed, whether carrying the object, elapsed ticks, best time.
Per-turn ephemeral: object position and velocity.
Information set: fully observable.
## Action space
- `run(speed)` — precondition: attempt in progress.
- `collect()` — precondition: co-located with the object, object has crossed the turn line, and current speed > 0.
- `release(direction, force)` — precondition: actor is the partner, at the start of an attempt.
## Playability notes
- **Single-player-vs-AI:** natural as a pacing-and-interception problem. R5's moving-collection constraint is what gives it content: the runner must arrive at the right speed, not merely the right place.
- **Group games (n>2):** runners do not interact; any n reduces to 1 without loss.
- **Physical-skill model:** collection probability as a function of approach speed and closing angle — too fast overshoots, too slow breaks R5.
- **What is lost:** the wind. The traditional game chased seed heads blown along a beach, and the whole character of that is an object no one controls. Substituting a partner's roll makes the trajectory predictable and removes the reason the game trained anything.
## Implementation hints
Implement the wind-driven object, not just the rolled ball — it is the traditional form and it is the more interesting problem. R5 is the rule that must not be dropped: allow stopping to collect and the game becomes an ordinary shuttle run.
Download as JSON
Download the full game corpus entry for this game as structured JSON.
Download JSONCite this page
Sprint-and-Retrieve Running Contest (Australia). (n.d.). Games of Countries. https://gamesofcountries.com/games/au-australia/tarnambai
@misc{gamesofcountries-au-australia-tarnambai,
title = {Sprint-and-Retrieve Running Contest (Australia)},
year = {n.d.},
publisher = {Games of Countries},
url = {https://gamesofcountries.com/games/au-australia/tarnambai}
}