// Section 01

Why Defensive Endgame Matters ⚙️

In Override, the alliance with more robots inside the midfield boundary at 0:00 claims center-goal yellow points. That makes the last 10 seconds a physical contest. A robot that's easy to push out gives up points. A robot that resists pushing earns them.

The Endgame Math

Per SC5b: yellow halves placed on the center goal score for whichever alliance has more robots in the midfield at the end of the match. Per the scoring table, each robot inside the midfield boundary at 0:00 is also worth 8 points directly.

Endgame outcome	Direct robot points	Center-goal yellow swing
Both alliance robots in midfield, 0 opponent robots	16 pts	All center yellow halves × 10
One alliance robot in, one opponent in (tied)	8 pts	Tied — no yellow swing
Pushed out at 0:01 (lost the count)	0 pts	Opponent claims yellow halves
Both alliance robots in, 1 opponent in	16 pts	Alliance claims yellow halves

If the center goal contains 4 yellow halves owned by the winning side, that's a 40-point swing on top of the 8 pt/robot base. A typical match decided by a 10-point margin can flip entirely on whether your robot stayed put for 10 seconds.

⚠️

The Endgame is allowed to be physical. Per SG12.2: Robots that attempt to end the Match in the Midfield should expect vigorous interactions from opponent Robots. Incidental damage from pushing, tipping, or entanglement is not a GG14 Violation in the Midfield. Plan for contact. Robots designed without push-resistance get pushed out.

What "Defensive Endgame" Means

Defensive endgame mechanisms are passive or actively-deployed systems whose job is one thing: stay in place when an opposing robot pushes you. That can take several forms:

Pneumatic brakes — pistons that drop a high-friction pad onto the field tiles, increasing the static friction holding your robot in place.
Drop-down anchors — mechanical (rubber-band-loaded) feet or pegs that deploy when triggered, gripping the floor without needing a motor.
Drop-center traction layouts — passive drivetrain configuration where the center wheels are slightly lower or use higher-grip rubber, optimizing for pushing contests over agility.
Mass distribution — not a mechanism, but a design choice. Putting battery and air tanks low + central improves resistance to pushing without adding parts.

What This Guide Covers

Tab 2 (Rules): what the manual actually says about pneumatic systems, defensive play, endgame mechanics, and field damage.
Tab 3 (Mechanism Catalog): 5 defensive endgame patterns with watts, complexity, and Override fit.
Tab 4 (Pneumatic Brake Build): step-by-step parts list and assembly for the most popular pattern.
Tab 5 (Trade-Offs): when defensive endgame is worth the build effort, when it isn't.

💡

This is Phase 3 / V2 territory. Defensive mechanisms aren't for the V1 Hero Bot. Build pickup-and-place reliability first; add defensive endgame once your team is consistently scoring and the next gain is in the midfield contest. See spartan-hero-bot for V1 priorities.

1 of 5

// Section 02

What the Manual Actually Says 📚

Defensive endgame mechanisms touch a lot of rules. Here's what the manual actually requires — verified against the Override v0.1 game manual, not paraphrased from forum threads or AI summaries.

⚠️

If you're reading rule citations elsewhere, verify them against the manual. AI assistants frequently cite plausible-but-wrong rule numbers (e.g., "G15 covers defensive play" — it doesn't; the rule is GG14). Every rule citation on this page has been verified against the manual text.

Rules That Apply to Pneumatic Brakes

R25 — Pneumatics are limited (V5RC)

Maximum two (2) VEX Air Tanks (276-8749) per robot.
Maximum 100 psi charge pressure.
Compressed air can only actuate legal pneumatic devices (cylinders, etc.). Not loose objects, not screws, not non-pneumatic mechanisms.

What this means for brake design: if you're already using both air tanks for intake/release pneumatics, you can't add a brake without sharing the air budget. Plan accordingly.

R26 — Pressure gauge is required

VEX Pressure Gauge (276-8748) must be installed.
Plumbed to high-pressure side if using a regulator.
Must be visible to inspectors without disassembly.

Practical note: if you don't already have pneumatics on the robot, adding a brake means adding a gauge, valves, tubing, and reservoir. That's ~30 minutes of mass and complexity even before you build the brake itself.

R28 — No modifications to pneumatic components

Pneumatic cylinders, valves, tubing, and reservoirs cannot be modified. You can mount them however you like, but you can't cut or alter the components themselves.

Rules That Apply During Endgame

SG12 — Some rules change during the Endgame period

Two clauses matter for defensive mechanisms:

SG12.1: Vertical expansion is limited to 18″ for any Robot that is partially or entirely within the infinite 3D vertical projection of the Midfield. (Same as starting size — you can't suddenly grow taller in the midfield.)
SG12.2: Robots in the Midfield should expect vigorous interactions. Incidental damage from opponents pushing, tipping, or becoming entangled is not a GG14 violation. Intentional damage may still be a S1 or G1 violation at the head referee's discretion.

Bottom line: getting pushed in the midfield during endgame is expected. The opposing alliance is allowed to push you. Your job is to not be moveable.

GG14 — Don't destroy other Robots, but expect defense

Defense is allowed. Strategies aimed solely at the destruction, damage, tipping over, entanglement, trapping, or forcing of opposing Robots are not part of the ethos of the competition.

What this means: a defensive brake mechanism is fine. A brake mechanism that includes spikes, sharp edges, or anything designed to damage opponents is not.

Rules That Apply to the Brake Foot Itself

S1 — Be safe out there (field damage)

If at any time the Robot operation or Team actions are deemed unsafe or have damaged a Field Element, Scoring Object, or the Field, the offending Team may receive a Disablement and/or Disqualification at the discretion of the Head Referee.

What this means for brake design: the foot/anchor that touches the field cannot mark, gouge, or tear the foam tiles. Hard plastic feet without rubber padding can leave indentations — risk of disablement. Always use rubber, silicone, or other compliant material against the floor.

Rules That Apply to AWP (Don't Forget)

SC8.3 — Neither Robot is contacting the Field Perimeter

AWP requires that neither robot is contacting the field perimeter at the end of autonomous. If your defensive brake mechanism deploys against the perimeter wall instead of the floor, you forfeit AWP.

Design implication: keep the brake oriented downward, not outward. Floor-friction works. Wall-bracing breaks AWP.

What is NOT a rule

Several common AI-generated claims about Override defensive play are fabricated:

"Rule G15 covers defensive play." G15 doesn't exist in Override. The actual rule is GG14.
"Rule R18 covers pneumatic limits." R18 is "Prohibited Items." Pneumatics are governed by R25, R26, and R28.
"Override has a 66W previous standard." No prior season had a 66W cap. Past V5RC seasons used 88W total; Override's 55W subsystem cap (R11a) is genuinely new.

If a forum post, AI assistant, or older guide cites a rule number you can't find in the manual, the citation is probably wrong. Always verify against override-manual-summary or the manual itself.

2 of 5

// Section 03

Mechanism Catalog 🧰

Five defensive endgame patterns. Color-coded for fit: green = good Override fit, gold = situational, purple = needs investment, red = avoid.

1. Pneumatic Brake (Drop-Down Friction Foot)

0W motor Build complexity: Medium Air budget: 1 cylinder fire

A vertically-mounted single-acting pneumatic cylinder. When fired, it pushes a rubber-padded foot down onto the field tile. The foot stays down via cylinder spring tension until the cylinder is reset. Result: ~3× static friction increase under the foot vs. wheel-only contact.

Override fit: excellent. Single fire at 0:11, hold position through endgame, no air consumed mid-match. Compatible with existing 2-tank V5RC pneumatic budget per R25.

Watch out: mounting must be rigid. A flexing mount under push pressure transfers force to the chassis, not the floor. Use steel or thick aluminum standoffs, not plastic.

2. Drop-Center Traction Wheel Layout

0W extra Build complexity: Low Passive (no actuator)

Six-wheel drivetrain layout where the center pair sits ~1/8″ lower than the outer corners (or uses higher-grip rubber). The center wheels carry most of the robot's weight when the chassis is level, maximizing static friction. Outer wheels lift slightly off the floor during turning, allowing easier pivoting.

Override fit: excellent baseline. Build into the V1 drivetrain from day one. No motor cost, no air cost, no rule risk.

Watch out: requires accurate center-wheel-height tolerance during build. Off by 1/16″ and you've done nothing different from a flat 6-wheel drive. Off by 1/4″ and your robot wobbles.

3. Rubber-Band Drop Anchor

0W motor Build complexity: Low Passive trigger

A spring-or-rubber-band-loaded foot held up by a string, latch, or pin. Driver pulls the latch (or a servo releases it) and rubber-band tension drives the foot to the floor. No air system required.

Override fit: good if you don't want to add pneumatics for one mechanism. Cheaper, simpler, no air budget.

Watch out: single-shot. Once deployed, you can't reset it during the match. If you fire too early, you're stuck. Driver discipline is critical.

4. Active Motor Brake (Servo-Driven Foot)

~5.5W (1 motor) Build complexity: Medium Resettable

A motor-driven foot that lowers and locks via mechanical advantage (worm gear, lead screw, or over-center latch). Resettable mid-match if needed. Gear ratio prevents the motor from being back-driven by push force.

Override fit: situational. Costs 5.5W of the 88W total cap (R10a) for a defensive-only mechanism. Most teams shouldn't spend a motor here unless they've maxed out scoring already.

Watch out: deployment time matters. If your motor takes 2 seconds to lower the foot, you've eaten 20% of the endgame window. Pneumatics deploy in 150ms; motors can't match that.

5. Wall-Bracing "Stinger"

0W motor Build complexity: Low AWP risk

A piston or arm that extends sideways to brace against the field perimeter wall, locking the robot in place via wall friction.

Override fit: avoid. If deployed during autonomous, this contacts the field perimeter and forfeits AWP per SC8.3. Even during driver control, it risks field-element contact violations and limits your maneuverability for the rest of the match.

Watch out: this pattern was viable in past games (Tower Takeover) where AWP didn't depend on perimeter clearance. Override's AWP rules close that loophole.

3 of 5

// Section 04

Pneumatic Brake — Build Guide 🔧

Step-by-step parts list and assembly for the most-recommended defensive endgame pattern. Assumes you already have a pneumatic system on the robot for another reason.

💡

Don't build pneumatics just for the brake. If your robot has no other reason to carry pneumatics (intake release, shifter, etc.), the cost of adding the system — tank, gauge, regulator, valves, tubing, weight — isn't worth a single defensive mechanism. Use the rubber-band drop anchor (catalog #3) instead.

Parts List

Part	Qty	Notes
Single-acting pneumatic cylinder, 3″ or 4″ stroke	1	Stroke length should be enough that the foot doesn't touch the floor when the cylinder is retracted (chassis must clear a max-height game element).
3-way solenoid valve	1	Standard VEX-supported solenoid valve.
VEX Pressure Gauge (276-8748)	1 (per system)	Already required by R26 if your robot uses pneumatics.
4mm pneumatic tubing	~12″	Run from solenoid to cylinder.
Brake foot plate (1.5″×1.5″ aluminum)	1	Bolted or zip-tied to cylinder rod end.
High-friction rubber pad	1	Cut from rubber tread, silicone sheet, or shoe-sole material. ~1/8″ thick. Glued or bolted to the foot.
1.5″ aluminum standoffs	4–6	For rigid mounting frame around cylinder.
L-channel or C-channel for mounting	1	Bolted to the chassis directly under the robot's center of mass.

Total mass added: ~150g if you don't already have a pneumatic system; ~50g incremental if you do.

Assembly Sequence

Locate center of mass. Build the brake mount directly under the robot's CG. Off-center brakes cause the chassis to rotate when force is applied — you stay in place but spin around the brake foot. Useless.
Build the rigid mount frame. 1.5″ aluminum standoffs forming a box around where the cylinder will sit. The frame transfers push force from the chassis through the cylinder body to the foot.
Mount the cylinder vertically, rod end pointing down. Bolt the cylinder body to the frame. Verify the rod can extend its full stroke without hitting any chassis member.
Attach the foot plate. Bolt or zip-tie the aluminum foot to the rod end. Verify it's perpendicular to the floor when the cylinder is extended.
Add the rubber pad. Cut a 1.5″×1.5″ piece of rubber tread or shoe-sole rubber. Bolt or contact-cement it to the bottom of the foot plate. This is the contact surface that protects the field tiles per S1.
Plumb the pneumatics. Solenoid mounts on the chassis (not the moving foot). Tubing runs from the high-pressure side of the solenoid to the cylinder. Pressure gauge stays on the high-pressure (tank) side per R26.
Wire the solenoid driver. Three-wire driver to a brain port. Map to a controller button (suggested: bottom paddle).
Test extension/retraction. Cylinder should extend (foot down) on button press, retract (foot up) on release. Verify ground clearance.
Test push resistance. Have a teammate push the robot before and after deployment. Should require visibly more force after.

Driver Macro

// Endgame brake macro (PROS / EZ-Template)
void deploy_brake() {
  brake_solenoid.set_value(true);   // extend cylinder, foot down
  master.rumble(".");                // haptic confirmation
}

void retract_brake() {
  brake_solenoid.set_value(false);  // retract cylinder, foot up
}
  

Driver maps deploy to a held button (button up = retract automatically). Or map to a toggle if the driver wants single-press deploy.

Calibration & Testing

Verify foot doesn't mark the floor. Deploy the brake on a foam tile for 30 seconds, then inspect the tile. If you see indentation or scuff marks, soften the rubber pad (use thicker or softer rubber).
Time the deployment. From button press to foot fully on the floor should be ≤200ms. If your tubing is too long or the solenoid is undersized, this may be longer.
Test the air budget. Single-acting cylinder fires use ~2 cubic inches of air per fire. With two charged tanks at 100 psi, you have plenty of capacity for one match's worth of brake fires. But if you're sharing tanks with other pneumatics (intake release), do the math on total fires per match and pressure-check between matches.
Push test with brake deployed. Have a teammate push the robot on tile. Compare to push force without brake. Should require 2–3× more force to move.

4 of 5

// Section 05

Trade-Offs — When To Build Defensive Endgame ⚖️

Defensive endgame is rarely the highest-priority mechanism. Here's how to decide whether your team should invest in it.

Don't Build A Brake If...

Your V1 hero bot isn't reliably scoring yet. Score first, defend later.
You're not running pneumatics for any other reason. Adding pneumatics for one defensive mechanism rarely pays off — use the rubber-band drop anchor instead.
Your team doesn't have at least one student fluent in pneumatic systems. Brake mechanisms that fail mid-match because of a leak or routing error cost you points instead of saving them.
You're still ironing out drivetrain reliability. A heavy or front-loaded chassis loses pushing matches even with a brake; fix the foundation first.
Your team strategy is to cycle through endgame instead of holding. If your scoring is volume-dependent (lots of pickup-and-place), you may be better served scoring one extra cycle in the last 10s than parking and braking.

Do Build A Brake If...

Your team consistently makes it to eliminations and matches go down to the endgame swing.
You're already running pneumatics for intake/release (incremental cost is low).
Your alliance partner can handle late-match scoring while you focus on defending the midfield.
You've scrimmaged enough to know that your robot is being pushed out of the midfield in >30% of endgame attempts. (If you're winning the push contest already with traction alone, don't add a brake.)
State competition is at least 4 weeks away. Rushing a brake mechanism in the last week introduces failure modes during the most important matches.

Decision Matrix

Pattern	Watt cost	Air cost	Build complexity	When to use
Drop-center traction	0W	0	Low (build into V1)	Always
Pneumatic brake	0W	1 fire / match	Medium	V2+, pneumatic system already on board
Rubber-band drop anchor	0W	0	Low	V2+, no pneumatic system, single-shot OK
Active motor brake	~5.5W	0	Medium	Rarely — motor watts better spent on scoring
Wall-bracing stinger	0W	1 fire	Low	Avoid — AWP risk per SC8.3

The Spartan Recommendation

For all 6 teams in Phase A: build drop-center traction into the V1 drivetrain. It costs nothing extra and improves push-resistance baseline.

For Phase D / E (post-camp, pre-state): teams that have running pneumatic systems and reliable scoring should add a pneumatic brake. Teams without pneumatics should consider a rubber-band drop anchor as a simpler alternative.

Do not build the active motor brake or wall-bracing stinger unless a specific scrimmage has shown they solve a real problem your team is having.

Cross-References

override-manual-summary — for full SG12, GG14, R25, R26, R28, S1 text and Override-specific scoring details.
override-endgame — tactical endgame strategy (when to commit, how to coordinate with partner).
override-drivetrain-config — 55W R11a drivetrain budget for high-traction wheel choices.
override-toggle-strategy — why the center goal's yellow halves are the dominant endgame point swing.
role-driver Drills tab — the "Midfield Pushback" drill for practicing defensive endgame.
spartan-hero-bot — V1 priorities (build pickup-and-place reliability before adding defensive mechanisms).

5 of 5