Skip to main content
Formal Specification

Territory flag tag — Formal Specification

Georgia · chase-tag · Confidence: medium

← Back to game page

Implementation Suitability

Suitability: adaptation-requiredFidelity: discretizedGap-fills: 2
# Alamborobana — AI-optimized specification ## General idea A two-team territorial raid-and-rescue game on a field split by a center line: crossing into enemy territory exposes a player to tagging, tagged players become chained prisoners who can be freed by a teammate's touch, and the win conditions are flag capture-and-return or total imprisonment of the opposing team. What is structurally distinct is the chain-rescue mechanic: captured players are not eliminated but form a linked, jointly-liberatable group, and there is no rule that forces anyone to cross the line at all. ## Formal model - **Abstraction taken:** The continuous field and open-hand tag contact are discretized into two territory zones (Territory A / Territory B), each with a Base sub-zone and a Prisoner Pen sub-zone. "Tagging" becomes an adjacency-triggered action rather than a physical touch; sprint speed becomes a per-tick movement budget. - **Player/agent count:** 2 teams of N agents each, N in [4,10] per the entry's player range. - **Turn model:** Continuous/simultaneous — every agent may act (move, tag, pick up flag, rescue) every tick. There is no imposed turn order; this mirrors the entry, which describes no phase structure beyond "cross, tag, capture, rescue." ## Formal rules R1. The field is partitioned into Territory A and Territory B by a center line. Each territory contains a Base zone (holds that team's flag) and an adjacent Prisoner Pen. R2. A player's zone-status is Safe while positioned in their own territory and Vulnerable while positioned in the opposing territory. R3. `tag(target)` is legal for actor A targeting player T iff A is Safe, T is Vulnerable, and A is adjacent to T. On execution, T transitions to Captured and is relocated to A's team's Prisoner Pen. R4. A Captured player may only take the action `join_chain()`, forming an ordered chain of prisoners extending from the pen toward the center line, subject to the constraint that the rearmost (pen-anchored) prisoner keeps continuous contact with the pen boundary. R5. `rescue_tag(chain_lead)` is legal for a Free teammate of the imprisoned team who is Vulnerable (i.e., physically present in the enemy territory) and adjacent to the frontmost ("lead") prisoner's extended hand. On execution, every prisoner currently in that chain transitions from Captured to Free and is granted immunity from tagging for the movement segment back to home territory. R6. `pick_up_flag()` is legal for a Vulnerable player located at the enemy Base zone; the actor becomes Flag-Carrier. R7. If a Flag-Carrier is the target of a successful `tag` (R3), the flag resets to the enemy Base zone and the carrier is Captured per R3-R4. R8. If a Flag-Carrier crosses the center line back into their own territory while still carrying the flag, their team wins immediately and the game ends. R9. If, at any tick, one team has zero Free players remaining (all are Captured) and the opposing team therefore has no possible rescuer, the opposing team wins immediately. R10. Win conditions R8 and R9 are mutually exclusive and jointly exhaustive of the entry's stated victory conditions; no other terminal state exists in the source rules. ## Edge cases - **Tie at end:** Not addressed by the entry. [gap-fill: if both teams' flag-carriers cross their respective home lines on the same tick, the outcome is declared a draw.] - **Player with no legal move:** Never occurs; every agent can always `move`, and `tag`/`pick_up_flag`/`rescue_tag` are simply unavailable rather than blocking. - **Repetition/cycles:** Real and unresolved by the source rules — nothing forces a player to leave their own territory (contrast with a game like hunt-ja-lambad, which has a mandatory crossing phase). Two purely defensive teams produce an infinite stalemate with no rule-mandated escalation. - **Simultaneous claims on one position:** If two Safe defenders both satisfy R3 against the same Vulnerable target on the same tick, the target is Captured once; [gap-fill: the capturing team is whichever defender's tag is resolved first in tie-broken action order, since the entry does not specify multi-tagger precedence]. - **Elimination mid-round and turn-order repair:** Not applicable — there is no turn order to repair. Captured players remain part of the game state (in the Prisoner Pen) rather than being removed, and can re-enter play via R5. - **Resource exhaustion:** Not applicable — no consumable resource exists in the rules; the flag is singular per team and simply relocates. - **Termination guarantee:** `termination_guaranteed: false`. The entry specifies no match clock, no forced-crossing mechanism, and no rule that increases pressure over time. A pair of teams that both refuse to cross the center line satisfies no legal-move requirement to do otherwise, so the game can continue indefinitely without violating any stated rule. Termination in practice depends on player choice (risk-taking), not on rule-enforced progress. ## State representation - Persistent state: team rosters; each team's flag location (`at_base` | `carried_by:`); Prisoner Pen membership and chain order per team. - Per-tick ephemeral state: each player's position and status (`Free-Safe`, `Free-Vulnerable`, `Captured`, `Flag-Carrier`); rescue-immunity flag for players mid-return under R5. - Observable information: fully observable — the physical field, all player positions, and both flags are visible to all players at all times. No hidden information exists in this game (contrast with e.g. bechdobana or achk-kapuk). ## Action space - `move(dx, dy)`: displacement within movement budget, any zone. - `tag(target_id)`: precondition per R3. - `pick_up_flag()`: precondition per R6. - `join_chain()`: precondition — actor is Captured. - `rescue_tag(chain_lead_id)`: precondition per R5. ## Playability notes - Single-player-vs-AI: Adaptable but weakened — a human can control one invader or one defender against AI teammates/opponents, but the chain-rescue mechanic (R4-R5) depends on multi-player coordination and loses most of its meaning below 2 Free players per team. - Reducing n>4 to 2 agents (1v1 per side): Breaks the game. Flag defense and prisoner-chain rescue both assume a squad that can split roles (attackers vs. base-guards); a 1v1 reduction collapses to a simple race-tag game and discards the entry's central "leaving a companion is unacceptable" social mechanic. - Physical-skill modeling: Sprint speed and open-hand tag range are abstracted into a movement-budget-per-tick and an adjacency radius; the game as specified has no skill check beyond position, so no probabilistic contest is needed for tagging itself. - What is lost: the improvised, continuously negotiated risk/reward of when to cross (a purely social/tactical decision in real play), and the physical exhaustion that in practice limits how long a stalemate (see Edge cases) can actually last. ## Implementation hints Field as a discrete grid (e.g., 30x20 cells) split at x=15; Base and Pen as fixed 3x3 sub-regions per the entry's stated dimensions. Branching factor per agent per tick is small (4-8 move directions + at most one of tag/pick_up/rescue), but joint action resolution across up to 20 agents needs a defined tie-break order (see R3 edge case). Representational trap: the chain-rescue constraint (R4) is a linked-list-like structure with a pen-anchoring invariant, not a simple counter — model it explicitly rather than as "N prisoners freed." First milestone: implement a 2v2 scenario with flag-capture only (omit chain rescue) to validate the Safe/Vulnerable/tag/win loop before adding R4-R5.

Download as JSON

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

Download JSON
Cite this page

Territory flag tag (Georgia). (n.d.). Games of Countries. https://gamesofcountries.com/games/ge-georgia/alamborobana

@misc{gamesofcountries-ge-georgia-alamborobana,
  title = {Territory flag tag (Georgia)},
  year = {n.d.},
  publisher = {Games of Countries},
  url = {https://gamesofcountries.com/games/ge-georgia/alamborobana}
}