Formal Specification
Julba (Totem-Team Vine-Skipping) — Formal Specification
Australia · strength-endurance · Confidence: low
← Back to game pageImplementation Suitability
Suitability: adaptation-requiredFidelity: discretizedGap-fills: 3
# Julba (Totem-Team Vine-Skipping) — AI-optimized specification
## General idea
Two totem-identified pairs skip together over one continuously turning rope, passing through each other's positions; the instant the rope strikes any member of a pair, that whole pair's team is eliminated for the round and replaced by a new pair.
## Formal model
State: rope_turning (continuous), team_Daroin: {members, eliminated: bool}, team_Ggaiar: {members, eliminated: bool}, pass-through progress (whether the pairs have completed their position swap this cycle).
## Formal rules
R1. Rope-turners turn the vine continuously throughout the round. R2. Both pairs (Daroin in front, Ggaiar behind) skip simultaneously. R3. Each pair performs its totem-signalling action while skipping (unspecified action; see gap-fill below). R4. During the round, the two pairs cross and swap positions (front pair moves back, back pair moves forward) while both continue skipping. R5. Each active skipper faces a per-tick rope-strike risk; if any member of a pair is struck, that pair's entire team is eliminated immediately and must leave. R6. A new pair enters to replace an eliminated team, and skipping continues (R2-R5 repeat). R7. [gap-fill] Assume, absent a documented specific action, that the totem-signalling gesture (R3) is a fixed, non-strategic flourish (e.g. an arm motion) rather than a mechanically consequential move, since the source describes it as identification, not as part of the win/loss resolution.
## Edge cases
Tie at end condition: explicitly documented in the adaptation — if both teams are still skipping when a time limit expires, the round is a draw; [gap-fill] extend this to the traditional form for a bounded implementation, since the traditional account itself states no time limit. No legal move: not applicable — skipping and the position-swap are continuously available actions while a pair remains in play. Repetition/cycles: teams being replaced after elimination and play continuing indefinitely is the documented normal mode (R6), not a failure state. Simultaneous conflicting actions: both pairs' rope-strike checks (R5) resolve independently and could in principle both fail on the same rope pass; [gap-fill] assume simultaneous elimination of both teams is possible and, if it occurs, the round is scored as a mutual knockout/draw. Mid-round elimination: is the core mechanic (R5-R6), explicitly handled by replacement, not an exceptional case. Resource exhaustion: not documented — no limit on the number of replacement pairs available is given; assume an effectively unlimited pool of waiting players unless configured otherwise. Termination guarantee: NOT guaranteed by the traditional account alone; the adaptation's five-minute/30-second-change structure is the only documented bound and should be treated as the default gap-fill for any playable implementation.
## State representation
(rope_turning: bool, team_Daroin: {members, eliminated}, team_Ggaiar: {members, eliminated}, swap_progress: float, time_elapsed: float)
## Action space
skip(pair) — maintain timing with the turning rope; signal_totem(pair) — perform the team-identifying action (non-mechanical flourish per R7); swap_position(pair_A, pair_B) — execute the pass-through position exchange.
## Playability notes
The pass-through position swap (R4) while both pairs continue skipping is the most structurally distinctive and hardest-to-formalise element — the source gives no detail on how collision or interference during the swap was handled, so any simulation of that moment is a significant gap-fill. Preserve the totem framing (R3, R7) as flavour/identity state even though it does not affect win/loss, since it is one of the few socially-meaningful details this card attests.
## Implementation hints
Because the swap mechanic (R4) is undocumented in its mechanical detail, consider implementing it as an atomic, always-succeeding position exchange rather than attempting to model collision risk during the crossing — inventing a collision-failure mechanic would be unsupported speculation beyond what the source states.
Download as JSON
Download the full game corpus entry for this game as structured JSON.
Download JSONCite this page
Julba (Totem-Team Vine-Skipping) (Australia). (n.d.). Games of Countries. https://gamesofcountries.com/games/au-australia/julba
@misc{gamesofcountries-au-australia-julba,
title = {Julba (Totem-Team Vine-Skipping) (Australia)},
year = {n.d.},
publisher = {Games of Countries},
url = {https://gamesofcountries.com/games/au-australia/julba}
}