⚡ Override 2026–27 · Game Analysis

Understand the Game.
Win the Match.

Most teams memorize the rules. Top teams analyze them — finding the highest-value actions, reading the meta, and making strategic decisions faster than anyone else on the field.

📋 This page applies the analysis framework to V5RC Override
Pins, cups, toggles, the 1+1 possession limit, and the 10-second midfield endgame. For deeper detail on any topic below, the dedicated Override guides go further:
📋 Manual Summary → ⭐ Toggle Strategy → ⏱️ Endgame → 🔄 Habit-Breaks →
📅 Kickoff Week?
After running the numbers here, use the Kickoff Week guide to route to the right mechanism preseason guide.
🔗 Kickoff Week Hub →
🎯 Need Override-Specific Strategy?
This page covers the general PPS framework. For the Override-specific scoring breakdown, 4-question decision process, and worked archetype examples, see the new Override Scoring page.
🎯 Override Scoring →
// Section 01
The Complete Scoring Breakdown
Before you can build a strategy, you need to know every way to score, every point value, and the maximum achievable score. Most teams only know half of this.
🎯
119
Game Pieces
Override 2026-27: 63 pins + 56 cups.
⏱️
2:00
Match Length
15s autonomous + 1:45 driver. Strategy decides who wins.
📊
PPS
Points/Second
The single most useful number in strategy.
📚
6
Sections
Scoring, PPS, score estimator, meta, in-tournament reading, framework.
🎮 Official Override Resources (2026-27)
🎥 Strategist Homework · community video
The community has already started analyzing the Override 0.1 manual. 9 Motor Gang's Override Game Manual Breakdown (48 min) walks through the rules, scoring, and field elements. Watch with a notebook and compare his interpretations against the official manual — that's how Strategists practice critical reading.

Every Way to Score Points

Override is scored by 4 actions. Maximum match scores depend heavily on toggle ownership and endgame midfield control. Per the Override v0.1 manual scoring table:

ActionPointsPer MatchNotes
Each Placed Alliance-colored Pin Core 5 Variable Pin nested in a Goal (or Cup nested to a Pin). One pin per cup half. SC2
Each Owned Yellow Pin Critical 10 Variable Yellow pin owned via toggle in matching quadrant, OR via majority of robots in midfield (center goal only). SC5
Each Robot in the Midfield (endgame) Critical 8 16 max per alliance Robot inside infinite vertical projection of midfield at 0:00. Both alliance robots = 16 pts. SC6
Autonomous Bonus Critical 12 12 / match Awarded to alliance with more points after auton. Tie = both alliances get 6. Violation in auton = bonus to opponent. SC7
Autonomous Win Point (AWP) Win Point +1 WP 1 WP / match 7+ pins placed for your alliance, 3+ goals each with 2+ alliance pins, neither robot contacting field perimeter. SC8
📚
Always verify against the latest manual. Rules and scoring values can change in v1.0 (expected July 2–9, 2026) based on Q&A input. The Spartan reference is override-manual-summary — a single-page rules cross-reference. The official Q&A opens May 14, 2026; track open questions on coach-notes § Q&A Backlog.

Field Layout — Know Your Zones

OVERRIDE 2026–27 — FIELD OVERVIEW (not to scale)

RED Q1
1 toggle · goals
BLUE Q1
1 toggle · goals
MIDFIELD — center goal · 8 pts/robot at 0:00
18″ height limit during endgame · SG12.1
RED Q2
1 toggle · goals
BLUE Q2
1 toggle · goals
■ 4 Quadrants — 1 toggle each ■ Midfield — center goal + endgame zone ■ 9 Goals total (5 neutral + 4 quadrant)

Game-Element Inventory — What's on the Field

Pins
Two-half cylinders
Each pin has 2 colored halves (yellow / alliance). Mid-section ~2.35″ diameter, 6.50″ tall.
Cups
Hourglass shape
Cups stack onto pins. Opaque/transparent sides — orientation matters for scoring. 6.48″ tall, 3.16″ rim.
4 Toggles
Quadrant ownership
One per quadrant. Set to red, blue, or yellow. Determines who scores yellow pins in that quadrant.
9 Goals
5 neutral + 4 quadrant
5 neutral goals scattered, 4 alliance-colored goals (2 per side). 1 center goal in the midfield.
💡
1+1 Possession Limit: a robot may possess at most one pin AND one cup at any time (SG6). Two pins, two cups, or three+ objects of any combination = penalty. This is the single most important constraint shaping mechanism design — it's why dual-grip architectures matter and why the "hold both, score both" cycle is the fastest theoretical pattern.

AWP Conditions — Standard vs Worlds-Qualifying

✅ Standard Events (per SC8)
  • 7+ pins placed for your alliance
  • 3+ goals each with 2+ alliance pins
  • › Pins on opposing-side quadrants don't count
  • › Neither robot contacting field perimeter at 0:15
⭐ Worlds-Qualifying Events
  • › The manual states the criteria will be modified for events qualifying directly to Worlds
  • › Modified criteria release in the Sept 3, 2026 manual update
  • › Examples cited: 8+ pins instead of 7, OR 4+ goals instead of 3
  • › Standard events use the SC8 criteria above
⚙ STEM HighlightMathematics: Game Theory & Constraint Analysis
Reading a game manual is a constraint analysis problem — the same skill engineers use when given design specifications. The scoring rules are constraints that define the solution space. A strategist's job is to find the maximum achievable score within those constraints, then determine which path to that maximum is most reliably achievable. For Override specifically, the dominant constraints are: 1+1 possession (shapes mechanism design), toggle ownership (shapes match strategy), and the 10-second midfield contest (shapes endgame design).
🎤 Interview line: “We start every season by doing a full constraint analysis of the game manual — extracting every scoring method, calculating the maximum possible score, and ranking actions by point value and achievability. For Override, we identified that yellow pin ownership via toggles produces the highest points-per-pin, so our strategy weights toggle capture over alliance-pin volume.”
Your alliance scores 4 yellow pins in a quadrant where the toggle is set to your alliance color. How many points does your alliance earn from those pins?
20 points (4 pins × 5)
40 points (4 owned yellow pins × 10)
0 points — yellow pins don't score in alliance quadrants
60 points (4 pins × 5 + 4 yellow × 10 stacked)
// Section 02
Points-Per-Second Analysis
Knowing point values isn't enough. The real question is: which action produces the most points per second of time spent? That ranking is your strategic priority list. Build your robot and practice your driver around #1 first.
The formula: Efficiency = (Points × Reliability) ÷ Cycle Time in seconds. An owned-yellow pin in a captured quadrant scored in 8s at 85% reliability = (10 × 0.85) ÷ 8 = 1.06 pts/sec. An alliance-pin scored in 6s at 90% reliability = (5 × 0.90) ÷ 6 = 0.75 pts/sec. The 8 pts/robot at 0:00 in the midfield, secured in the last 10s, = 0.80 pts/sec per robot. Use this calculator to rank your team's actual actions.

Points-Per-Second Calculator

Add up to 5 scoring actions. Enter the point value, your team's estimated cycle time in seconds, and your reliability (how often it works, 0–100%). Hit Rank to see your priority list.

Override — Pre-Calculated Benchmarks

These are starting estimates based on Override scoring rules, the 1+1 possession limit, and reasonable mechanism performance. Your actual numbers will differ — use the calculator above with your real scrimmage data once your robot exists.

ActionPtsEst. CycleEst. ReliabilityPts/SecPriority
Owned yellow pin in captured quadrant 10 7–9s 80–90% 0.89–1.29 Primary
Toggle capture (one quadrant) multiplier 4–6s 85–95% force-multiplier Critical setup
Alliance-colored pin (placed) 5 5–8s 85–95% 0.53–0.95 Secondary
Robot in midfield at 0:00 (endgame) 8 10s window 60–90% 0.48–0.72 End-game
Auton: 7+ pins for AWP +1 WP 15s (fixed) 50–75% Win Point
Auton: outscore opponent (12pt bonus) 12 15s (fixed) 40–70% 0.32–0.56 Critical
💡
The counter-intuitive insight: Yellow pin scoring is 2× the per-pin value of alliance pins (10 vs 5), but only when you own the toggle in that quadrant. A team that captures the toggle first and then dumps yellow pins outscores a team that scored more pins overall but didn't secure ownership. Toggle capture isn't a scoring action by itself — it's a multiplier that doubles the value of every yellow pin in that quadrant. See override-toggle-strategy for the full math.
1+1 Possession Limit shapes every cycle. A robot can hold one pin AND one cup simultaneously, but not two pins or two cups. This means your "maximum cycle" is one pin + one cup placement = up to 15 pts (10 yellow-owned + 5 alliance, if you place both). Robots that ignore the cup half of the rule cap their efficiency at 50%.
⚙ STEM HighlightMathematics: Expected Value & Optimization
Points-per-second analysis is an application of expected value optimization — the same framework used in economics, operations research, and game theory. Expected value = probability × payoff. By dividing by time, we convert it to a rate (points per second), which allows us to compare actions that have different time costs. For Override, the additional layer is that some actions are multipliers (toggle capture) rather than direct scorers — their EV depends on what they enable other actions to score.
🎤 Interview line: “We rank our robot's actions by expected points per second — that's points times reliability divided by cycle time. For Override, we treat toggle captures separately because they multiply the value of yellow pins we score afterward. Our priority order goes: capture toggle first, then dump yellow pins in that quadrant, then place alliance pins for AWP coverage.”
Robot A scores 6 alliance pins (5 pts each = 30 pts) in 36 seconds. Robot B captures one toggle (4s) then scores 4 yellow pins in that quadrant (10 pts each = 40 pts) in 32 seconds total. Which is more efficient?
Robot A — more pins scored = better demonstration of speed
Robot B — 40 pts in 32s = 1.25 pts/sec vs Robot A's 30 pts in 36s = 0.83 pts/sec. The toggle capture pays for itself by doubling each subsequent yellow pin.
Equal — both alliances score points so it cancels out
Robot A — alliance pins are more reliable than yellow pins
// Section 03
Match Score Estimator
Before every match, a top strategist knows the expected score range for both alliances. This tool lets you build a realistic projection based on what you know about your team and your opponent.
📌 Quick Take Score everything by points-per-second (PPS), not raw point values. A 5-point objective that takes 8 seconds (0.6 PPS) is worse than a 3-point objective that takes 4 seconds (0.75 PPS). Top teams optimize for cycle speed, not point value.

Build Your Match Score Projection

■ Your Alliance
■ Opponent Alliance
YOUR ALLIANCE
vs
OPPONENT
Fill in the estimates above

What Realistic Override Match Scores Might Look Like

Override is too new to have observed match data — the season starts after April 24, 2026. These are predicted ranges based on the manual's scoring math, the 1+1 possession constraint, and reasonable mechanism cycle times. Update these as scrimmage data comes in.

Team LevelPredicted ScoreKey DriverWhat Wins Matches
Beginner 25–55 pts Auton bonus often decides it Reliable auton + 5–8 alliance pins. Ignoring toggles entirely is common.
Intermediate 60–110 pts Pin volume + auton + endgame 10+ pins placed, occasional toggle capture, one robot to midfield by 0:00
Advanced 120–180 pts Toggle ownership + endgame Both alliance robots to midfield, multiple toggles owned, AWP-coverage alliance pins
Top Teams 180+ pts Toggle saturation + center goal contest Auton win, 3+ toggles owned, 2 robots midfield, contested center-goal yellow swing
⚠️
The 16-point endgame swing. Both alliances have access to 16 endgame points (2 robots × 8 each). In a close match, who controls the midfield at 0:00 is often the entire margin. Add the contested center-goal yellow pin swing (which goes to the alliance with more midfield robots) and the endgame can be worth 30+ points. See override-endgame.
You're projected to win 142–128 with 20 seconds left. Both your robots are mid-cycle scoring alliance pins. Your opponent has both robots heading to midfield. What's the better decision?
Abandon the cycles and send at least one robot to midfield. Two opponent robots = 16 endgame pts; if you send 0 they swing the match by 16. The 14-pt lead disappears.
Keep scoring — you're ahead and pin volume builds the lead
Send both robots to play defense in their alliance zone
Try to capture another toggle — toggles always pay off
// Section 04
Meta-Game Analysis
The “meta” is the dominant strategy at any given point in the season — what the best teams are doing and why. Understanding the meta tells you whether to follow it, adapt it, or beat it by being ahead of it.
📌 Quick Take The meta evolves. Early-season meta is usually simple cycling. Mid-season it becomes complex stacking. Late-season it's defense + counter-strategy. Read the meta and either fit it or counter it — don't ignore it.
📊
What is the meta? The meta is the set of strategies that produce the best results given the current skill level of the competitive field. It evolves as the season progresses. A strategy that wins early-season regionals may be countered by the time State comes around.

How the Meta May Evolve in Override

Override is brand new (revealed April 24, 2026). The meta below is a prediction based on the manual's constraints and what mid-2020s VRC seasons converged toward. As actual events run, update this with observed data.

E
Early Season — Single-Grip Robots, Toggles Ignored
Most teams build single-grip claw or roller intakes. The 1+1 possession rule isn't fully exploited. Toggles are mostly left at random colors. Endgame midfield contests are uncommon. Winning move: build any working dual-grip or capture the toggle in 1–2 quadrants.
M
Mid Season — Toggles Become Standard, Endgame Contested
Top teams routinely capture 2–3 toggles per match. Both alliance robots commit to midfield by 0:00. Cycle times converge around 7–9s for owned-yellow placement. AWP becomes contested. Winning move: 4-toggle saturation OR aggressive midfield defense.
L
Late Season / Regionals — Defensive Endgame & Center-Goal Contest
Pneumatic brakes / drop anchors appear for defensive endgame play (see override-defensive-endgame). The center-goal yellow swing becomes the deciding factor in close matches. Toggle-flip races on the last second. Winning move: pre-match decision on offensive endgame vs defensive anchor.

Pioneer vs Follow the Meta

🚀 Pioneer Early
For Override specifically: dual-grip mechanisms (one pin + one cup simultaneously) are the obvious pioneer move. Pneumatic-brake defensive endgame is a less-obvious one. Risk: dual-grip is mechanically harder; defensive endgame is high-risk if your offense is weak. Reward: early ranking advantage before opponents catch up.
📊 Follow and Refine
Watch top regional teams. Whatever architecture wins (claw vs roller-pinch, single vs dual grip), do it better. Risk: everyone's doing the same thing and driver execution becomes everything. Reward: proven strategy with a known ceiling.

Four Strategic Priorities Every Override Match

Win Autonomous (12 pts)
12 pts is structural — recovering it requires outscoring the opponent by 12+ pts in driver control. Win auton first. AWP second. Never skip auton practice to add one more cycle.
Capture Toggles, Then Score Yellow
A toggle capture is 4–6s of work that converts every yellow pin in that quadrant from 0 to 10 pts. Sequence matters: capture first, then dump yellow. See override-toggle-strategy.
Cover AWP Goals
SC8: 7+ alliance pins, 3+ goals each with 2+ alliance pins. Distribute pins across goals deliberately, don't pile them in one. AWP = 1 WP ≈ equivalent to several cycles in qualification ranking.
Secure Endgame Midfield
8 pts/robot at 0:00. 16 pts swing if both alliance robots commit. Plus the center-goal yellow swing if applicable. Decide BEFORE the match: offensive (commit both) or defensive (one anchors).
At your first Override scrimmage, you watch 4 matches. The top-scoring alliance captured 3 toggles in 3 of 4 matches. What's the right takeaway?
Immediately copy their toggle-capture sequence in your next match without further analysis
Record the data, identify WHY toggle capture beats raw pin volume in their matches, then decide whether your robot can replicate it or whether you should contest a different lever (e.g., defensive endgame)
Ignore it — every match is different and toggle strategy doesn't generalize
Pivot to defense against any team using toggles to neutralize their advantage
// Section 05
In-Tournament Game Reading
Scouting teams is one thing. Reading the game as it’s being played around you is another skill entirely. This is what separates strategists who can adapt from ones who can only execute a pre-planned script.
👀
The rule: Every match you’re not playing is a data collection opportunity. If you’re watching for entertainment, you’re wasting it. Your phone is your notebook. Tap the checklist below every match you watch.

In-Match Observation Checklist

Tap each item as you confirm it for any match you watch. Tracks per match. Reset between matches.

Patterns That Should Change Your Pre-Match Plan

What You ObserveWhat It MeansAdapt By
Opponent consistently wins autonomous Your 12-pt bonus is at risk every match Run AWP tasks during auton even if you lose the bonus — get the Win Point. Score 7+ alliance pins distributed across 3 goals.
Opponents capture toggles aggressively in 2–3 quadrants They're running a yellow-volume strategy Either contest the toggles before they capture them, OR commit to a different lever (defensive endgame, alliance-pin coverage of unclaimed quadrants)
Opponent robot is slow on one side of the field Mechanical or code limitation Start on that side — capture toggle and score yellow before they arrive
Opponent never sends a robot to midfield in endgame 16-pt swing is sitting on the table Send both your alliance robots to midfield — guaranteed 16 pts plus center-goal yellow swing
Opponent has fast auton that consistently fails at 0:15 Reliability problem — high ceiling, low floor Target the same quadrants their auton is trying to reach — when it fails, you get them for free
Matches are being decided by 5–15 points High-margin-sensitivity tournament Every decision needs justification — auton, AWP, toggle capture sequence, endgame commitment all matter more
Toggle states change rapidly in last 30s Toggle-flipping race is the deciding factor Reserve at least one robot for late toggle work; brief drivers on which quadrants matter for your score
Penalty calls (R25, SG12, S1) cluster around midfield contests Refs are watching pushing/contact closely in this tournament Brief drivers: minimize sustained contact, prefer parallel-to-perimeter contact. See override-defensive-endgame for legal contact rules.
⚙ STEM HighlightScience: Observation, Inference & Hypothesis Testing
In-tournament game reading is applied scientific observation. You observe (opponent always captures the toggle in Q1), infer (Q1 has favorable goal placement for their robot architecture), form a hypothesis (scoring in Q1 first will deny them their primary lane), then test it in your next match. This is the scientific method running in real-time. Every match is an experiment and every data point updates your model of the competition.
🎤 Interview line: “During tournaments, our strategist watches every match as a structured observation session — recording auton results, toggle capture sequences, endgame commitment patterns, and cycle times. We use that data to update our strategy between matches, the same way scientists update their model when new data comes in.”
You watch three matches and notice the team you're about to face never sends a robot to midfield at 0:00 — both robots stay in their alliance zone scoring pins. What's the strategic implication?
No implication — their pin-volume strategy might be working fine
They're leaving 16 pts on the table every match (2 robots × 8 pts) plus the center-goal yellow swing. If you commit both your robots to midfield, you bank 16+ pts they can't recover.
You should also stay back to keep things even
It means their robot is probably too slow to reach midfield in the endgame window
// Section 06
Strategic Decision Framework
Use this before every match. Work through each question in order. At the end you have a clear strategic priority for this specific match against this specific opponent.
📌 Quick Take A 6-question framework that takes ~3 min before each match: who is alliance, what's their bot, what are opponents, what's our role, what's the win condition, what's the contingency. Skipping this loses winnable matches.
When to use this: Fill this out during queue — the 2–3 minutes before you walk to the field. The answers to each question should already be in your head from scouting. This just structures the thinking.

Pre-Match Decision Tree

Q1 Did we earn AWP last match?
Check your consistency. AWP requires 7+ alliance pins, 3+ goals each with 2+ alliance pins, no perimeter contact at 0:15. If yes, it's part of your standard run. If no, identify which condition you missed.
↳ YES — keep the same auton routine
↳ NO — identify the missing condition before you queue (was it the 7-pin count, the 3-goal distribution, or perimeter contact?)
Q2 Is our opponent's autonomous reliable?
Did it work in the matches you watched? If they have a better auton than you, the 12-pt bonus is likely theirs. You need to outperform in driver control by 12+ pts (roughly 2 owned-yellow pins or 1 yellow + 1 alliance).
YES Their auton is reliable
Accept losing the 12-pt bonus. Focus driver control on toggle capture + yellow-pin volume. Target: outscore by 13+ pts via owned yellows.
NO Their auton is inconsistent
Run a reliable auton and win the bonus. Even a simple routine that works 9/10 beats a complex one that works 5/10. Bank 12 pts.
Q3 Which quadrants do we capture toggles in?
Decide pre-match. Toggle capture is 4–6s of work that doubles every yellow pin you score in that quadrant. Two robots can realistically capture 2–3 toggles per match. Don't spread thin — commit.
Aggressive 3–4 toggles + yellow saturation
Use this when: opponent isn't contesting toggles, your robot has fast toggle-capture mechanism, you have multiple yellow-pin pickups ready. Highest ceiling.
Conservative 1–2 toggles + alliance-pin AWP coverage
Use this when: opponent has fast toggle-flip game, your robot is slower at toggle capture, you need reliable AWP. Lower ceiling, higher floor.
Q4 What's the endgame plan?
Decide now, not at 0:15. Last 10s = 8 pts/robot in midfield. Both robots = 16 pts. Plus center-goal yellow swing if applicable.
Both Both robots commit to midfield
Default if you're in a close match or behind. Bank 16 pts plus center-goal yellow swing. Stop scoring cycles at 0:12 to be safely in midfield by 0:00.
Defensive One robot anchors, one scores
Use when: you're winning by enough that protecting the toggle states matters more than 8 endgame pts. The anchoring robot is at the perimeter or holding a captured toggle. See override-defensive-endgame.
Skip Neither robot to midfield
Almost never correct unless you're winning by 30+ AND opponent isn't going to midfield either. Leaves 16 pts on the table.
Q5 What do we do if a toggle gets flipped against us late?
Toggle flips can change ownership of every yellow pin in a quadrant. If the opponent flips your captured toggle at 0:30, you may lose 30+ pts. Pre-decide: flip it back, or accept the loss?
RECAPTURE If we have time + a robot near the toggle
Flip back if > 8 seconds left + a robot can reach it. Recapturing 4 yellow pins = 40 pts saved.
ABANDON If < 8s or no robot nearby
Commit remaining time to midfield endgame. Don't let one robot do half a job on toggle and miss midfield by 0:00.

The Match Call (One Sentence)

After working through the decision tree, summarize the entire strategy in one sentence. This is what your driver hears right before they queue.

🔅 Craft your match call
This is the last thing your squad hears before they walk to the field. Say it out loud.
🎮 Driver Guides — Translate This Analysis Into Action
The strategic priorities and match call above feed directly into these guides. Give your driver the match call; these guides give them the execution system.
⚡ Offensive Driving → 👁 Match Reading → 📍 Field Positioning → ⏱ Endgame → 🤝 Alliance Coordination → 🔧 Recovery Driving → 🏆 High-Stakes Driving →

Related Guides

🔬 Check for Understanding
Your team scores 7 alliance pins per match (35 pts) but the top teams in your region score 12 owned-yellow pins per match (120 pts). Your robot is faster than theirs — but they're winning. What should you analyze first?
Their drivetrain configuration — they must have a faster drive
Their toggle-capture sequence and yellow-pin pickup pattern — the 2× multiplier from owned yellow vs alliance pins likely explains the gap, not raw speed
Their autonomous program — they must have a more optimized PID tune
Their alliance partner — the extra points may be coming from coordination
Correct. Raw speed rarely explains a 35-vs-120 differential — scoring strategy and toggle ownership do. Yellow pins owned via toggles are 10 pts each vs 5 for alliance pins. A team that captures toggles first then dumps yellow can outscore a faster team that ignores toggles. Watch match videos and log the toggle sequence: when do they capture, when do they place yellow, when do they recapture if flipped. That data belongs in your Red (tournament/strategy) notebook slides.
📝
← ALL GUIDES