Skip to main content
Formal Specification

Yidinji Mock-Combat Contest — Formal Specification

Australia · stick-team · Confidence: low

← Back to game page

Implementation Suitability

Suitability: adaptation-requiredFidelity: discretizedGap-fills: 4
# Puloga — AI-optimized specification ## General idea The Yidinji form of north Queensland mock combat. Structurally it differs from *prun* in one important way: players move into the playing area rather than holding two fixed lines, so it is a free-field skirmish rather than a volley exchange across a gap. ## Formal model - **Abstraction taken:** the field is a grid both teams occupy; throws resolve as hit checks against the target's response. The below-the-shoulders rule becomes a valid-target-zone constraint. - **Player/agent count:** two teams of eight to fifteen or more. - **Turn model:** ticked and simultaneous. ## Formal rules R1. Teams start at opposite ends and then move freely into the playing area. R2. Each tick, a player holding a missile may `throw(target, zone)`; a player without one may `retrieve()` or move. R3. A throw is legal only if the target zone is **below the shoulders**. Higher throws are not in the action space. R4. A throw hits with probability `p(distance, target_response)`. [gap-fill] No hit model is given. R5. A targeted player may `dodge()` on the arrival tick, reducing hit probability. R6. Missiles are retrieved and thrown back; ammunition circulates and is not consumed. R7. Play is continuous, with no turns. R8. [gap-fill] A contact is counted but does not eliminate. The source attests neither scoring nor elimination. R9. [gap-fill] The contest ends by agreement; impose a tick cap for a bounded artifact. R10. [gap-fill] A minimum throwing distance of 3 units applies, taken from the Commission's safety adaptation rather than from tradition, and it materially changes close-range play. ## Edge cases - **Tie at the end condition:** no scoring is attested (R8); under imposed contact-counting, equal counts are a draw. - **Player with no legal move:** never — moving, retrieving and dodging are always available. - **Repetition / cycles:** ammunition circulates and contacts do not eliminate, so the skirmish can run indefinitely. R9's cap is the only bound. - **Simultaneous claims:** two players reaching one grounded missile resolve to the nearer, then lower index. Simultaneous mutual contacts both count. - **Mid-round elimination and turn-order repair:** nobody is eliminated (R8); every surviving player acts each tick, so no order repair is needed. - **Resource exhaustion:** missiles are not exhausted; nothing else is consumed. - **Termination guarantee:** none attested; supplied only by R9. ## State representation Persistent: field bounds, minimum throw distance, missiles in circulation, tick cap. Per-player: team, cell, missiles held, response this tick, contacts taken. Per-turn ephemeral: missiles in flight with target, zone and arrival tick; grounded missiles. Information set: fully observable. ## Action space - `throw(target_id, zone)` — precondition: actor holds a missile; zone is below the shoulders; target at least the minimum distance away. - `dodge()` — precondition: a missile is arriving this tick. - `retrieve(missile_id)` / `move(direction)`. ## Playability notes - **Single-player-vs-AI:** natural as a team-level agent. The free-field movement makes positioning matter more than in *prun*, where the lines are fixed. - **Group games (n>2):** already two teams; scales down cleanly. - **Physical-skill model:** hit probability by distance and target response. - **What is lost:** the same as *prun* — the clan identification, the display, the dispute settlement. Also note that R10's minimum distance is a modern safety rule, not tradition, and it removes exactly the close-quarters contact that a real skirmish would have had. ## Implementation hints Compare with `prun.ai.md` before implementing: the two share a family but differ in field structure — fixed lines versus free movement — and that difference is attested, not invented. If you build one engine for both, make the line constraint a parameter rather than assuming it.

Download as JSON

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

Download JSON
Cite this page

Yidinji Mock-Combat Contest (Australia). (n.d.). Games of Countries. https://gamesofcountries.com/games/au-australia/puloga

@misc{gamesofcountries-au-australia-puloga,
  title = {Yidinji Mock-Combat Contest (Australia)},
  year = {n.d.},
  publisher = {Games of Countries},
  url = {https://gamesofcountries.com/games/au-australia/puloga}
}