Formal Specification
Mock Combat Missile and Shield Game — Formal Specification
Australia · stick-team · Confidence: low
← Back to game pageImplementation Suitability
Suitability: adaptation-requiredFidelity: discretizedGap-fills: 4
# Taktyerra — AI-optimized specification
## General idea
Two lines exchange soft missiles across a neutral zone, defending with shields, and missiles are retrieved and returned — so ammunition circulates rather than depleting. Elimination is by being struck, which makes it a continuous attrition game rather than a turn-based duel.
## Formal model
- **Abstraction taken:** the field becomes two ranks separated by a neutral zone; throws resolve as hit checks against a target's shield state and evasion. Missile flight is a one-tick delay, not a trajectory.
- **Player/agent count:** 2 teams of equal size, 6–15 per side.
- **Turn model:** ticked and simultaneous — both lines throw on the same tick.
## Formal rules
R1. The teams form facing lines 15–20 units apart across a neutral zone.
R2. Each tick, any player holding a missile may `throw(target)`; play is continuous, not alternating.
R3. A defender may `raise_shield()` or `dodge()` on a tick, which reduces the probability of being struck.
R4. A throw strikes with probability `p(distance, target_defence)`. [gap-fill] No hit model is given.
R5. A player who is struck steps back and is out until the end of the round.
R6. Missiles that land in the neutral zone may be retrieved with `retrieve()` and thrown back. Ammunition therefore circulates and is not consumed.
R7. Points are awarded for clean body hits.
R8. The round ends when one side is eliminated, or after a fixed time.
R9. [gap-fill] A player cannot both shield and throw on the same tick — the choice between offence and defence each tick is what gives the game its structure, and no source states it.
R10. [gap-fill] Retrieval requires entering the neutral zone, which forgoes shielding that tick.
## Edge cases
- **Tie at the end condition:** a timed round ending with both sides alive is decided on points under R7. Both sides eliminated on the same tick is possible with simultaneous throws — score it a draw.
- **Player with no legal move:** a player with no missile and none within reach may still shield or dodge, so no agent is ever stuck.
- **Repetition / cycles:** because ammunition circulates (R6), the exchange can continue indefinitely. R8's time cap is what guarantees an end; without it the game genuinely need not terminate.
- **Simultaneous claims:** two players retrieving the same missile resolve to the nearer, then lower index. Mutual simultaneous strikes both count — neither pre-empts the other.
- **Mid-round elimination and turn-order repair:** struck players are removed from their line for the round. Since all surviving players act every tick, no turn order needs repair; the line simply thins.
- **Resource exhaustion:** missiles are **not** exhausted, by R6. The exhausting resource is players.
- **Termination guarantee:** guaranteed by R8's time cap. Elimination alone does not guarantee it, since a cautious pair of survivors could shield indefinitely.
## State representation
Persistent: line positions, neutral zone width, team sizes, round time cap.
Per-player: team, `active|out`, missiles held, defence stance this tick.
Per-turn ephemeral: missiles in flight with target and arrival tick, missiles lying in the neutral zone.
Information set: fully observable.
## Action space
- `throw(target_id)` — precondition: actor is active and holds a missile.
- `raise_shield()` / `dodge()` — precondition: actor is active.
- `retrieve(missile_id)` — precondition: actor is active and the missile is within reach.
## Playability notes
- **Single-player-vs-AI:** natural with one agent per side choosing a joint action. The offence/defence tension in R9 gives it real decision content.
- **Group games (n>4):** reduces to small teams without structural loss, though the source describes lines of up to 15 and the massed-volley character is lost below about six a side.
- **Physical-skill model:** hit probability as a function of distance and the target's chosen defence.
- **What is lost:** that this is mock combat with cultural framing, not a dodgeball match. The missiles are deliberately soft and the game trained evasion for real conflict; the spec preserves the mechanic and none of the meaning.
## Implementation hints
The offence-or-defence choice each tick (R9) is a [gap-fill], but without it the optimal policy is to always throw and never shield, which collapses the game — so if you strip the gap-fills, expect the model to degenerate and understand that as a signal the source is incomplete, not that the game is trivial. First milestone: two lines, throws only, fixed defence, and confirm the time cap fires.
Download as JSON
Download the full game corpus entry for this game as structured JSON.
Download JSONCite this page
Mock Combat Missile and Shield Game (Australia). (n.d.). Games of Countries. https://gamesofcountries.com/games/au-australia/taktyerra
@misc{gamesofcountries-au-australia-taktyerra,
title = {Mock Combat Missile and Shield Game (Australia)},
year = {n.d.},
publisher = {Games of Countries},
url = {https://gamesofcountries.com/games/au-australia/taktyerra}
}