🏆 Competition · Driver + Strategist · Intermediate
Alliance Coordination
Two robots competing independently lose to two robots operating as a system. Alliance coordination is the difference between 24 points each and 30 points combined. This guide covers field splits, communication signals, and real-time fallback.
Evergreen guide: Two-robot coordination logic applies to every VRC game. Field splits and specific signals change by season — the coordination framework is permanent.
🗺 The Pre-Match Field Split — Two Options
The field split is the most important pre-match decision. It should be agreed before you walk to the field — not improvised during driver control.
Robot A owns the left half. Robot B owns the right half. Both cycle their own side, zero coordination needed after the match starts.
✓ Simple. Degrades gracefully. Default for most matches.
Robot A cycles aggressively. Robot B contests center zone and plays flexible support. Higher ceiling — requires communication.
↑ Higher ceiling. Use with a trusted alliance partner only.
Default to the half-field split in all qualification matches and first elimination matches with an unfamiliar partner. It degrades gracefully when communication breaks down — which it will under tournament pressure. The role split requires trust built through multiple matches together.
📡 Communication Signals — What Works in a Tournament
Tournaments are loud. Verbal communication degrades. Pre-agree specific signals before the match — not during it.
| Signal | Method | Meaning | When to use |
|---|
| 1 rumble | Partner controller button | "I'm jammed or limited" | Intake jam, mechanism failure, robot stuck |
| 2 rumbles | Partner controller button | "Switching to your half" | Crossing the field split, covering partner's zone |
| 3 rumbles | Partner controller button | "Going to endgame early" | Mechanical failure or significant score lead |
| "SWITCH" | Verbal, single word | Robot A go right / B go left | Mid-match split adjustment |
| "CENTER" | Verbal, single word | One robot contest center goal | Opponent dominating shared zone |
| "PARK" | Verbal, single word | Commit to endgame now | 20+ point lead, or T−40s regardless |
🚦 Traffic Management — Not Colliding with Your Partner
- Never approach the same goal from the same direction simultaneously. If your partner is at the left goal scoring, approach from the right. If both approach from the same side, one stops — that's a lost cycle.
- The robot carrying an element has right-of-way. An empty robot re-routes in 1 second. A robot about to score loses 3+ seconds re-routing at the goal. Empty robot always yields.
- If you cause a traffic jam, immediately reverse and find an alternative. 2 seconds of reversal is faster than 5 seconds of pushing. Don't fight for the same space.
🔄 When the Plan Breaks Down — Default Behavior
Your partner jams. Your auton failed. The opponent is double-teaming. The agreed plan is gone. Default immediately:
- Revert to half-field split. Each robot focuses on its own half. No communication needed. Both robots remain productive.
- The functional robot cycles; the broken robot secures endgame. Guaranteed endgame points beat zero points trying to fix an intake mid-match.
- Don't stop to help your partner. Moving to assist a stuck robot costs your own cycle time and usually doesn't actually help.
Know your partner's robot before the match. Use scouting data to check: their average cycle time, preferred side, auton reliability, and endgame success rate. A partner who consistently parks right means you should plan to be left at T−30. Don't discover this during the match.
Alliance coordination applies Nash equilibrium from game theory — each robot's strategy is optimal only when accounting for its partner's simultaneous actions. When both robots independently target the same goal, neither scores the zone control bonus; when they pre-commit to different zones, both scoring rates increase. Pre-match coordination converts a game-theoretic conflict into a cooperative solution that maximizes combined expected points.
🎤 Interview line: “We treat alliance coordination as an applied game theory problem. Pre-match, we map each robot's optimal zone and pre-commit to a split strategy. This eliminates the Nash equilibrium trap where both robots target the same goal. Our coordination protocol increased combined alliance score by 18% compared to uncoordinated matches.”
Your alliance partner gets pushed out of the center goal zone. You have 90 seconds left. What is the best response?
⬛ Stop and help your partner recover position
⬛ Execute your pre-agreed contingency: one robot contests center while the other maintains long goal pressure
⬛ Continue your own strategy and ignore the zone shift
📝Notebook entry tip: Tournament Prep — Red slide — Write a pre-match coordination entry before each event: agreed zone assignments, the signal for switching to your contingency plan, and endgame trigger. After the match, note which coordination moments succeeded. Alliance strategy that is documented before matches — and reviewed after — is evidence of systematic strategic preparation.