UI name in toolbox: on track [INDEX]
Block type: Value block, output type Boolean
Definition: Checks which track a team is assigned to, enabling different game experiences for different teams.
When it becomes true: When a team is assigned to the specified track number.
How to build it:
- Drag
on track [INDEX]from Logic category - Enter the track number in
[INDEX]field - Connect to condition socket in WHEN block
Field:
[INDEX]: whole number, minimum 1
How it works:
- Teams are assigned tracks in the order they join the game
- Track numbers loop: 1, 2, 1, 2, 1, 2, …
- First team joins → Track 1
- Second team joins → Track 2
- Third team joins → Track 1
- And so on…
When to use:
- Creating different experiences for alternating teams
- A/B testing game variations
- Handicapping or difficulty adjustment
- Geographic routing (teams take different paths)
Example (Simple):
Block: on track 1
Scenario:
- First team joins → Assigned Track 1 → Condition TRUE
- Second team joins → Assigned Track 2 → Condition FALSE
- Third team joins → Assigned Track 1 → Condition TRUE
Example (Route variation):
Rule 1: When on track 1 → Show west-side tasks
Rule 2: When on track 2 → Show east-side tasks
Result: Alternating teams see different map regions
Example (Edge Case – Odd number of teams):
Teams:
- Team A → Assigned Track 1
- Team B → Assigned Track 2
- Team C → Assigned Track 1 (cycles back)
Result: Odd-numbered teams get Track 1; even-numbered get Track 2
Notes:
- Assignment is permanent (set at game start, doesn’t change)
- Useful for balancing teams or creating differentiated paths
- Block checks the team’s assignment, not dynamic re-routing
Common mistakes:
- Forgetting that assignment is based on join order, not team choice
- Creating logic that assumes teams can switch tracks (they can’t)
