Push Back — The Game 🧱

The Volume-Plus-Defense Build

The strongest Push Back robots could score 15+ blocks per match while denying opponent blocks via descoring. The convergence over the season was toward an integrated intake-and-lift architecture that let a single mechanism handle both putting blocks in goals and pulling them out.

Why This Architecture Won

Three reasons the volume-plus-defense build dominated:

1. One mechanism, two functions. Reverse-direction intakes did both scoring and descoring without adding a separate mechanism — saving weight, motors, and complexity.
2. Block-throughput scaled linearly with cycle time. Faster cycles compounded over a 2-minute match: a robot averaging 8-second cycles produced ~50% more total points than a robot averaging 12-second cycles.
3. Defensive scoring offset opponent gains. Each descored block was effectively a 6-point swing (you denied 3 pts of theirs and freed the slot for 3 pts of yours). Teams that could descore reliably won close matches.

How a Match Played Out

Top-tier match flow:

• 0:00–0:15 Auton. Score 4-7 blocks plus AWP tasks (loader removal, goal coverage). Auton bonus = 10 pts.
• 0:15–1:00 Volume push. Both alliance robots cycle blocks into preferred goals. Match loads added by drive team.
• 1:00–1:30 Zone contest. Defense and descoring activate. Robots track which long-goal control zone matters most.
• 1:30–1:50 Final cycles. Last block deposits prioritized for zone control.
• 1:50–2:00 Park. Robots commit to alliance park zone for endgame bonus. Decision made based on score margin: if leading, park early; if losing, fight for one more cycle.

Strategic Asymmetry

Push Back's asymmetry was that cycle speed mattered more than mechanism complexity. A simple reliable robot doing 12-second cycles outscored a complex robot doing 6-second cycles if the complex one jammed once per match. The teams that won regionals were the ones that ran 80+ matches in scrimmages and tuned for consistency over peak performance.

The Volume-Maximizers

Volume-first teams treated every block placement as worth the same 3 points and optimized for total throughput. This produced the simplest and most reliable strategy: drive to nearest loader, intake match loads, drive to nearest available goal, deposit, repeat.

• Strength: consistency. With no decision-making overhead, drivers could focus on driving.
• Strength: match load utilization. Volume teams almost always cleared their loaders.
• Weakness: beat by zone-control teams in close matches when control bonuses pushed margins beyond raw block count.

The Zone-Controllers

Zone-control teams asked a different question: which goal will give us a multiplier on every block we put there? Push Back's long goals had control zones — the alliance with the majority of blocks in that zone gained a bonus. Concentrating cycles in one long goal was often higher-EV than spreading blocks across all four.

• Strength: higher per-block value when control was secured.
• Strength: created defensive priorities — opponents had to contest the zone or give up the bonus.
• Weakness: required more strategic awareness from drivers; harder to teach to rookies.
• Weakness: if zone control flipped late in a match, the entire bonus disappeared, costing a large point swing.

The Hybrid Approach

Mid-to-late season, the meta converged on a hybrid: commit one robot to the high-value zone, the other to flexible volume. The zone-committed robot defended its zone and added blocks; the flex robot took whatever scoring opportunities appeared. This split the alliance's job in a way that didn't require both drivers to think strategically in real time.

The Descoring Sub-Strategy

Descoring was a 6-point swing per block: your robot pulls a block off the opponent's scored zone (-3 for them) and now you can score a new block in the freed space (+3 for you). Top teams included descoring as a regular part of their cycle rotation, not a niche move. Specific top-team descoring rates need verification from match video analysis.

Cycle Time Reality Check

Reasonable Push Back cycle times by team level:

• Beginner team: 12–18 seconds per block (intake, drive, score). verify against Spartan team data
• Intermediate team: 8–12 seconds per block.
• Advanced regional team: 6–9 seconds per block, often holding 2–3 blocks at once.
• Worlds-tier: 5–7 seconds per block on cleanest cycles, with multi-block grabs hitting 4 seconds per block effective rate. unverified

Push Back AWP Conditions

For standard events, AWP required all four of:

1. 7+ blocks of your alliance color scored.
2. 3+ goals each containing at least 1 of your blocks.
3. 3+ blocks removed from your alliance loaders.
4. Neither robot touching the park zone barrier at the end of autonomous.

For events qualifying directly to Worlds, the bar was higher: 10+ blocks, 2+ blocks per goal across all 4 goals.

Why AWP Mattered Disproportionately

AWP delivered 1 Win Point in qualification rankings — equivalent to winning roughly 0.7 matches in tournament tiebreakers. A team consistently hitting AWP across 8 qualification matches gained the equivalent of 5-6 extra ranking-match wins. This was structural — you could be middle-of-the-pack in match wins and still rank top-10 by hitting AWP every match.

Top Skills Runs — Push Back

Skills (Driving + Programming) had aggressive ceilings. Top-tier programmed-skills runs hit numbers TBD — verify from RobotEvents archive. Driving skills ceilings were higher because match loads were available throughout the run. The structural difference between Programming and Driving skills:

• Programming: single robot, no human input, 1 minute. Score limited by auton consistency and how many cycles your code could chain together.
• Driving: single robot, full driver control, 1 minute. Score limited by driver cycle speed and match-load utilization.

What Top Programming Routines Did

The structure of high-scoring Push Back programming runs:

1. Score preload + nearest field blocks for fast initial points.
2. Hit one loader to grab match loads.
3. Cycle into Long Goal targeting control zone.
4. Optional descoring move on a setup-blocked goal.
5. Final park or final cycle depending on time remaining.

Total scored blocks in a 60-second programming routine ranged from 12 (intermediate) to 35+ (Worlds-tier). Spartan-team specific PB skills bests need confirmation.

Why Override Changes the Drive Budget

A 6×11W drivetrain uses 66W. It could fit Push Back’s 88W total budget, but exceeds Override’s 55W drivetrain limit. Compare the remaining mechanism power as well as drive performance.

For Override, R10 caps total motors at 88W and R11 caps drivetrain motors at 55W. A 55W drive leaves 33W; a 44W drive leaves 44W. These are current-season comparisons, not Push Back rules.

The Three Legal Drive Configurations

Push Back drives converged on three main options:

The PTO Era and Its End

A PTO can reuse motors for different tasks in games whose rules allow it. Treat any Push Back PTO example here as historical; do not infer Override legality from that example.

Override R11 prevents drivetrain motors (Subsystem 2) from powering mechanisms outside Subsystem 1. A drivetrain-to-lift PTO is not a workaround for the cap. See current drivetrain options.

Gear Ratio Trends

Push Back drives generally ran specific blue/green/red ratios TBD — verify against top-team CAD reveals. The dominant trend was toward speed (blue cartridge, ~360 RPM) for cycle-time optimization on the open field, with some teams using green (~200 RPM) for better defensive pushing power. Red cartridge (~100 RPM) was rare in Push Back drivetrains because the field was open enough that pushing power was secondary.

What Transfers

• Recheck the drivetrain. Transfer the design process, then count motor power again: Override’s 55W drivetrain limit may invalidate a Push Back chassis motor allocation.
• AWP discipline. The structural advantage of AWP-every-match is identical — 1 Win Point per match, same ranking math. Build for AWP first, peak performance second.
• Cycle time over peak performance. Push Back rewarded reliable 8-second cycles over inconsistent 5-second cycles. Override is the same: a robot that scores 6 owned-yellow pins reliably outscores one that scores 8 erratically.
• Match load utilization. Push Back match loads = Override pin/cup loaders. Same lesson: ignored loaders = points left on the table.
• Driver-led strategy decisions in scrimmages. Push Back drivers who could read which long-goal zone mattered most translate well to Override drivers reading toggle states.

What Doesn't Transfer

• Descoring. Override SG10 prohibits removing scoring objects from neutral/opponent goals. The entire Push Back descoring sub-strategy is now illegal. Teams that built around descoring as a primary lever have to rebuild their offensive playbook around toggle ownership instead.
• Volume-first scoring. Push Back rewarded 25+ blocks per match. Override caps possession at 1 pin + 1 cup (SG6) and scores per-half — raw cycle count matters less than which halves you own via toggles.
• Current Override rule: Current SG12: during the final 10 seconds, do not Place Scoring Objects on the Midfield Goal. The former approximate-starting-height provision was removed September 10. Lowering is an optional stability strategy; the 50-inch overall vertical limit and other rules still apply. Historical pre-September-10 context: Park endgame. Push Back parking was a fixed point bonus for entering a designated zone. Override eliminates this entirely — the endgame is a 10-second positional fight in the midfield with vertical expansion limited to 18″ (SG12). Mechanism designs optimized for parking solve the wrong problem.
• Zone-control multiplier thinking. Push Back long-goal control zones gave bonuses for majority block color. Override has no equivalent zone-multiplier — the analog is toggle ownership, which multiplies yellow-pin scoring within a quadrant. The mental pattern transfers; the mechanic doesn't.
• Recheck defense. Do not infer a universal goal-blocking rule from a past game. Override SG9 protects opposing Alliance Goals, SG10 protects Placed objects on neutral Goals, and SG13 protects Load Zones; the general interaction rules also apply.
• Multi-block grab cycles. Push Back robots commonly held 2-3 blocks simultaneously. Override SG6 restricts to 1 pin + 1 cup — mechanism designs that grabbed multiple Push Back blocks at once will need to be reconsidered.

The Mental Reset

The biggest carryover failure mode from Push Back is what we've been calling the "more is more" instinct — the assumption that scoring more is always better. Override breaks this in two places:

1. Toggle ownership doubles points without scoring more. Capturing a toggle in your alliance color converts every yellow-half placed in that quadrant from 0 to 10 pts. Teams that focus on "more pins" without thinking about ownership will be outscored by teams that capture toggles first.
2. Endgame position matters more than late cycles. 8 pts/robot at 0:00 in the midfield, plus center-goal yellow swing if both your alliance robots are there. A team that scores one extra cycle at 1:55 instead of moving to midfield by 0:00 loses 8–25+ pts on that decision.

What Returning Push Back Veterans Should Read First

If your team had a strong Push Back season and returning students are pattern-matching their old strategies onto Override, the priority reading list is:

What This Page Doesn't Cover

Several specific facts about Push Back are flagged with TBD markers throughout because they require verification from primary sources our team has access to but I don't:

• Specific Spartan team match scores, AWP rates, and skills bests for Push Back season.
• Top-team gear-ratio splits (blue vs green dominance).
• Observed Worlds-tier cycle times verified against match video.
• Specific Spartan-program lessons learned during Push Back — the things that should be archived for institutional memory but require interview-style input from returning students.

Action item for returning students: the placeholders in this guide are a structured chance for your engineering notebook's Reflection slide. What worked for our teams in Push Back? What didn't? What would you tell a Phase-A rookie this year about lessons from last year? See coach-notes for adding a Q&A or external review entry that captures these lessons before they're forgotten.