Sources & confidence: Game rules and scoring per RECF Game Manual archive and Wikipedia summary. Triball field layout and elevation bar mechanics are from manual sources. The 88W motor power cap was introduced this season — verified via VEX Forum 2023 announcement thread. Specific Worlds-winning team identities are NOT named in this guide because I could not verify them with primary sources. Mechanism archetypes (catapults, wings, elevation hangs) are general patterns drawn from public reveals, not specific competition records.
// Section 01
Over Under — The Game 🥈
2023–24 V5RC season. Triballs (3-sided geometric balls), under-and-over goal scoring across a central barrier, and an elevation-bar climbing endgame. The strongest elevation-mechanism precedent for Override.
📚 Historical Reference🧠 Best Elevation-Endgame Precedent
Quick Game Summary
VEX Robotics Competition Over Under was played on a 12′×12′ field divided in half by a central barrier. Two alliances (red/blue) of two teams competed in 15-second autonomous + 1:45 driver-controlled matches. Per the official Wikipedia summary derived from the manual:
60 Triballs on the field (3-sided geometric ball-like shapes that rolled or slid).
2 goals (one per alliance, opposite sides of the barrier). Each Triball scored in a goal worth 5 points.
2 points per Triball scored in the alliance's side of the field (no need to make it into the goal).
4 match load stations — teams could feed Triballs into their own field area during the match.
Elevation bar per alliance at match end — climbing/hanging from the bar earned points based on hang tier.
8-point autonomous bonus for the winner.
AWP: score at least 1 Triball in goal, empty match load station, touch elevation bar at autonomous end.
What Made This Game Distinctive
Two unique elements defined Over Under:
The central barrier. Unlike most VRC games where the field is open, Over Under had a physical barrier separating the two alliance sides. Triballs scored in your offensive zone (opponent's side) were worth more, but getting them over the barrier required catapult-style mechanisms or specific over-bar handling.
The elevation bar. A horizontal bar at each alliance's side that robots could grab and lift themselves on. The first widely-played V5RC game with a hang/elevate endgame (versus parking or platform balance).
Why It Matters for Override
⚠
Override hook: If Override has a hang/elevation/climb endgame — and especially if there's a king-of-the-hill or elevated scoring zone — Over Under's elevation bar mechanisms are the most relevant elevation-endgame precedent in V5RC. The mechanism choices (passive hooks, pneumatic latches, motorized winches) and the strategic patterns (commit timing, hang tier selection) transfer directly. Verify against Monday's manual.
1 of 6
// Section 02
The Dominant Archetype 🧩
Over Under's meta converged toward a four-subsystem build: intake, catapult or shooter, deployable wings, and elevation hang.
The All-Around Build
🏆 The Over Under Meta Build
Drive
4-motor or 6-motor tank, 360 RPM, 3.25′′ or 4′′ omnis
Intake
Roller intake at floor level for picking up Triballs (often a single-stage spinning bar with anti-jam geometry)
Shooter / catapult
Spring-tensioned catapult that launches Triballs over the central barrier into the offensive zone or goal
Wings
Pneumatically-deployed lateral wings — pushed Triballs across the field, blocked opponent shots, or denied Triball flow
Endgame
Hang mechanism (hook or claw) that grabs the elevation bar; motor or pneumatic winch lifts the robot
Total motors
6–8
Why This Architecture Won
Catapults solved the over-barrier scoring — faster than alternative approaches (lifting and dropping).
Wings were a force multiplier — one wing-deployment could sweep 5–10 Triballs across the field at once. Highest points-per-action of any mechanism.
Elevation hang was high-value but cheap — a passive hook + motor winch could be added for relatively low motor cost.
The intake was the easy part — once a roller intake was built, it ran continuously without further attention.
How a Match Played Out
Autonomous (15s): Score preload Triballs into goal, hit the AWP requirements (touch elevation bar, empty match load), retreat to defensive position.
Early driver (0:00–0:30): Race to clear Triballs from your defensive zone — either intake them and shoot over, or wing-push them across the barrier.
Mid driver (0:30–1:15): Continuous catapult cycles — intake, fire over barrier, repeat. Wings deployed periodically for mass-Triball pushes.
Late driver (1:15–1:35): Final scoring push, last Triball loads, position for endgame.
Endgame (1:35–1:45): Elevation hang. Higher tiers required mechanical lift; lower tiers required only contact with bar.
Strategic Asymmetry
Over Under had an interesting strategic asymmetry: scoring on the opponent's side was worth more than on your own side (Triballs in opponent's offensive zone scored 2 points each just by being there). This created a unique strategy:
You wanted to push Triballs into the opponent's zone to score points.
Opponent simultaneously wanted to push Triballs back.
Wings became weapons of points-transfer — sweep Triballs across the barrier for a 2-point-per-ball swing.
This made wings the highest-EV mechanism on most builds. A robot without wings was at a structural disadvantage, even if its catapult was faster.
🧠
Asymmetric scoring lesson: When a game has scoring zones with different values (your-side vs. opponent-side, neutral vs. alliance), movement mechanisms become as important as scoring mechanisms. Wings, plows, and pushers can be competitive scoring tools without ever "handling" a game piece directly.
2 of 6
// Section 03
Pneumatic Wings 🌂
The signature Over Under mechanism. Lateral pneumatic flippers that deployed in seconds and swept Triballs en masse across the central barrier.
What Wings Were
Wings were two flat panels mounted on either side of the robot, hinged to fold flat against the chassis when not in use. A pneumatic cylinder (or motor) extended each wing out laterally to ~24′′ total robot width. Once deployed, driving forward pushed Triballs across the field via wing surface contact.
The 36′′ horizontal expansion limit (a V5RC standard rule) was the cap on wing extent. Most wings deployed to the limit and stayed there for most of the match.
Wing Mechanism Variants
Single-Stage Pneumatic
One cylinder per wing, single-action deployment. Extend at match start, retract for endgame mobility. Cheapest pneumatic option. Most common.
Two-Stage Pneumatic
Wings could deploy partially or fully. Partial deployment was useful for navigating tight spaces near the barrier; full deployment for mass Triball sweeps. More valves, more complexity, more capability.
Motorized Wings
Some teams used a motor + linkage instead of pneumatics. Slower deployment (1–2 seconds vs. instant) but no air budget concern. Could partially deploy to any angle.
Plow / Scoop Wings
Some wings were not flat panels but curved scoops — designed to corral Triballs rather than just push them. More effective for collecting; less effective for sweeping.
Wing Strategy
Deploy after autonomous. Wings could not be deployed during autonomous (size limit). First action in driver control was usually wing deployment.
Cross-field push at match start. A robot driving across the field with wings out could move 8–15 Triballs to the opponent's side in 5 seconds. Highest single-action point yield.
Defensive wing usage. Wings could also block opponent catapult shots or contain Triballs against your wall to prevent opponent push.
Retract for elevation hang. Wings interfered with hang positioning. Most teams retracted wings before endgame.
Why This Pattern Will Repeat
Whenever a V5RC game has asymmetric value scoring across a barrier or boundary, wing-style mechanisms will dominate. The mechanics are too efficient: a single deployment moves enough scoring to outweigh many cycles of conventional intake-and-shoot.
⚠
Override hook: If Override has zone-based scoring with point asymmetry across boundaries, expect wings to reappear — even if the game piece geometry differs. The Over Under wing mechanisms transfer directly to any "push pieces across a line" scenario.
3 of 6
// Section 04
The Elevation Bar 🏌
Over Under introduced V5RC's first true hang/elevation endgame. Reach a horizontal bar, grab it, and lift yourself for tiered point bonuses.
📋
Mechanism deep-dive: For detailed climb-mechanism design (passive hook vs. pneumatic latch vs. motor winch vs. cascading lift), see Climbing & Elevation Mechanisms. This page focuses on Over Under-specific elevation bar strategy.
How the Elevation Bar Worked
Each alliance had a horizontal bar at their side of the field. At match end, robots could grab the bar and lift themselves off the ground. The higher you hung, the more points you earned. A robot fully elevated (off the ground) scored more than one merely touching the bar.
Critically, both alliance robots could attempt to elevate — this multiplied the endgame points and made coordinated alliance hangs a real strategic factor.
Elevation Mechanism Archetypes
Passive Hook + Drive Pull
Static hook on the robot reaches over the bar; drive backward and the hook engages. Robot then pulls itself up using drive force. Mechanically simplest. Limited to lower tiers but very reliable. Most regional teams used this.
Pneumatic Latch
A pneumatic-deployed claw or latch grabs the bar. Once latched, motor winch or additional pneumatic actuation lifts the robot. Faster deployment than passive hook. More motor port flexibility (no dedicated drive-pull pose required).
Motorized Winch Lift
A high-reduction motor connected to a string or chain that pulls the robot upward after the hook engages. Capable of full elevation tiers. Slower (3–5 seconds) but reliably hits high-tier point thresholds.
Cascading Lift Climber
A multi-stage telescoping lift extends upward, grabs the bar, and lifts via the lift mechanism reversing. High capability but mechanically complex. Used by top-tier builds for max-tier elevation.
Strategic Patterns
Commit Timing
Elevation took 5–10 seconds reliably. Commit window:
Passive hook + drive pull: ~5 seconds before buzzer (must position, drive into bar)
Earlier commitment risked being knocked off by opponents. Later commitment risked failing to fully elevate before buzzer.
Alliance Coordination
Two alliance robots could both elevate, but they shared the same bar. Top alliances pre-rehearsed:
Approach order — who goes first, who goes second
Bar position — left side vs. right side of bar
Recovery plan if one robot fails — partner retries or commits to floor scoring
Denial Strategy
Opponent could physically block your elevation bar approach. Some defensive specialists made elevation denial their endgame role. Counter: elevation mechs that could deploy from a distance (long-reach hooks) rather than requiring close-range positioning.
Why This Matters for Override
If Override has any climb / hang / lift-self / king-of-the-hill endgame, the Over Under elevation mechanisms transfer directly. The four archetypes (passive hook, pneumatic latch, motor winch, cascading lift) cover the design space for any horizontal-bar or elevated-platform endgame.
🧠
Endgame-mech selection rule: Match the mechanism complexity to the point ceiling. If the endgame is worth ~15 points, a passive hook is sufficient. If it's worth ~40 points (like Tipping Point's platform tilt), invest in a more elaborate mechanism. Always consider: would an extra 10 seconds of mid-match scoring with a simpler endgame outscore the more complex endgame?
4 of 6
// Section 05
Drive Setups 🚗
Over Under drive choices balanced cross-field speed (push Triballs across barrier) with positioning precision (line up catapult shots, approach elevation bar).
Drive Standard
Same convergent answer as Tipping Point and High Stakes: 4–6 motor tank, 360 RPM, 3.25′′ omnis. The pattern repeats because it works.
Drive Style
RPM
Wheels
Used By
4-motor 257 RPM
257
4′′ omni
Beginner / regional teams; reliable but slow cross-field
4-motor 360 RPM
360
3.25′′ omni
Mid-tier balanced
6-motor 360 RPM
360
3.25′′ omni
Worlds-level standard
6-motor 450 RPM
450
2.75′′ omni
Speed builds for fast wing-pushes
X-drive
~360
3.25′′ omni @ 45°
Some teams — agility for close-range Triball play
Maneuverability vs. Power: The Tradeoff Over Under Forced
The 6-motor 360 RPM standard wasn't the obvious answer in 2023. It became the standard because Over Under's field forced teams to balance two competing demands:
Cross-field speed — pushing Triballs over the barrier required moving the full field width quickly. A 4-motor 257 RPM drive felt sluggish during Triball pushes; teams routinely lost possession battles before reaching the barrier.
Tight-space agility — close to the goal, especially in alliance home zones, robots needed to pivot, micro-adjust, and dodge defenders. Pure speed builds were graceless in these spaces.
Three practical metrics teams optimized for — and the same metrics will matter for Override:
Metric
What It Measures
Why It Matters
Top speed
Free-running ft/sec
Cross-field traverse time. Over Under: ~5–6 ft/sec target. Override: similar — goals are spread across the field.
Pivot footprint
Smallest space the robot can rotate 180° in
Goal-adjacent maneuvering. Tank with omnis: pivots in place; X-drive: same; wide robots with deployed wings: large turning radius.
Acceleration
0 to top speed in feet
Driver-control match flow — how quickly you can change direction. Over-geared drives accelerate slowly even when top speed is high.
The 6-motor 360 RPM standard hit all three reasonably well. 4-motor 360 was a notch behind on acceleration (less torque per wheel) but still competitive. 4-motor 257 won on torque but lost on speed; 6-motor 450 won on speed but felt twitchy in tight spaces.
Override translation: if Override's field has goals that require both cross-field traverse and goal-adjacent maneuvering (likely, based on the cup-shaped scoring receptacles confirmed at kickoff), the same maneuverability vs. power tradeoff applies. Whatever the legal motor count ends up being under the new rules, prioritize a drive that does both adequately rather than one that wins on a single metric. The teams that picked specialist drives (pure-speed or pure-torque) in past games consistently underperformed at high levels.
Wing-Robot Drive Considerations
Robots with deployed wings effectively had a much wider footprint. Implications:
Pivot point shifted with wing deployment — turning while wings were deployed required different driver instinct than turning without.
Acceleration was reduced — pushing wings full of Triballs across the field was hard work for the drive.
Field navigation changed — tight spaces near the barrier became impassable with wings out.
Catapult Drive Constraint
Catapult-equipped robots needed to aim shots. Drive precision (small heading adjustments via tank-turn or strafe) was important. X-drive teams reported smoother aim adjustment; tank teams reported faster cross-field repositioning. Trade-off was real but minor; both approaches won at high levels.
⚠
Override drive caveat: The 6-motor drives that won Over Under regions are not legal under Override. The 55W system electrical cap was explicitly confirmed in the Override game reveal video (April 24, 2026), continuing the rule introduced for Push Back (2025-26). The two main legal options are 4 × 11W blue (44W, simpler) or 4 × 11W green + 2 × 5.5W half motors (55W at the cap, more complex) — the Override 55W Drivetrain Decision guide walks through which to pick for your team. Specific exceptions — PTO carve-outs, special-case allowances, half-motor counting rules — are not yet specified and will be confirmed when the manual drops Monday April 27.
5 of 6
// Section 06
What Transfers to Override 🎯
Over Under's most valuable contributions: the elevation hang playbook, and the wing-mechanism pattern for asymmetric-zone scoring.
Universal Lessons
Asymmetric zone scoring rewards push mechanisms. Wings, plows, and sweepers can be high-EV scoring tools without ever "handling" a game piece.
Elevation/hang endgames need mechanism diversity. Four proven archetypes — passive hook, pneumatic latch, motor winch, cascading lift — cover the design space.
Endgame mechanism complexity should match endgame point ceiling. Don't over-engineer if the endgame is only worth 15 points.
Catapults remain a viable archetype for any over-barrier or far-target scoring.
Pneumatic deployments (wings, latches) trade air budget for instant action — well-suited to one-shot critical moments.
Mechanism-Specific Transfer
Pneumatic wings — if Override has zone-based scoring with point asymmetry, wings are the high-EV starting mechanism.
Catapults / spring-loaded launchers — for any over-barrier or far-distance scoring.
Passive hook + drive pull — simplest reliable elevation hang for low-tier point ceilings.
Pneumatic latch climbers — mid-tier hang capability with fast deployment.
Motor winch climbers — high-tier hang with reliable execution.
Strategic Patterns
Asymmetric scoring math first. If Override has zones with different point values, calculate which actions move the most net points.
Wing-vs-catapult vs both — if both push and shoot mechanisms are viable, alliance complementarity matters — one robot does each.
Elevation timing rehearsed — whatever your hang mechanism, practice the last 10 seconds hundreds of times.
AWP design — Over Under's AWP combined three actions (score Triball, empty load, touch elevation). If Override has a similar multi-condition AWP, design auton routes to nail all conditions.
Override Hooks (Speculation, Pre-Manual)
⚠
Pre-manual: Speculation only — verify against Monday April 27 manual.
If Override has any climb / hang / elevation endgame, the four Over Under archetypes are your design space.
If Override has asymmetric zone scoring, plan for wings or pushers as a primary mechanism.
If Override has over-barrier or far-target scoring, catapults are the proven archetype.
If Override has multi-condition AWPs, design auton routines to satisfy all conditions, not just maximize score.
Recommended Pre-Override Prep
Watch a 2024 Over Under Worlds match. Note specifically how teams handled the wing deployment and elevation hang.
If Override has elevation: prototype a passive hook + drive pull as your week-one hang mechanism. It's cheap, fast to build, and gives you a working subsystem.
If Override has asymmetric zones: design wings into the early CAD, even if you end up not using them. Knowing they fit gives you the option.
Practice multi-condition AWP routines — this is a programming skill that compounds across seasons.
🧠
Final principle: Over Under introduced wings as a serious mechanism category and proved elevation hangs work in V5RC. Both lessons are now part of the standard V5RC mechanism vocabulary — if Override calls for either, the design space is well-developed and the references are recent enough to be immediately useful.