Spin Up — The Game 🎯

Archetype A: The Flywheel Shooter

The flywheel was the most-built archetype. A single high-RPM wheel pressed against the disc launches it via friction. Hood-style designs gave consistent arc trajectory; a queue system fed discs at controlled rate so the flywheel had time to spin back up between shots.

By Worlds, top-tier flywheel builds were achieving disc rates of ~1 disc per second with high accuracy, scoring 30+ disc points per match consistently. The flywheel won most regional events.

Archetype B: The Catapult

Catapults had higher single-shot impact than flywheels — a well-tensioned catapult could launch discs from across the field with great accuracy. Trade-off: slower reload time. Catapults were a top-tier choice for teams that prioritized accuracy over rate.

The mechanical risk: catapults stored a lot of energy. Snapped rubber bands or failed releases could damage the robot or, in rare cases, harm bystanders. Required careful design.

Archetype C: The Punch Shooter

Less common than flywheel or catapult but represented in a few high-tier teams. Pneumatic punch had instant action (no spin-up time) and consistent shot energy, but limited by air budget — you only got so many shots before refilling.

The Common Thread — The Roller Mechanism

Regardless of disc-shooting choice, every competitive Spin Up robot needed a roller manipulation mechanism. With 4 owned rollers worth 10 points each (40 points possible) and the AWP requiring 2 of them, ignoring rollers was not a competitive option.

The roller manipulation got its own dedicated section — see the next page.

How the Field Rollers Worked

Per the official Spin Up Game Manual: each roller is constructed from 2′′ nominal Schedule 40 PVC pipe, 250mm long, 60.3mm diameter, mounted to the field perimeter. The roller surface is wrapped with both alliance colors. The manual scoring rule: "If the area inside of a Roller's pointers only shows one color, that is considered ‘Owned’ by that Alliance." Each owned roller is worth 10 points at match end.

The pointers are physical reference marks on the roller; the rectangular area between them defines what counts for "owned" status. To own a roller, your robot has to spin it until that pointer-defined area shows only your alliance color.

Rollers can be re-spun at any point during the match, so "owned" status is not permanent — it can flip back and forth as either alliance contacts the roller.

Roller Mechanism — the Hero-Bot Pattern

The official 2022–23 V5RC Hero Bot "Disco" demonstrated the canonical Spin Up roller approach (per the VEX Library Disco documentation):

Most teams built variations of this Disco pattern:

Design Considerations (per public team discussion)

• Wheel height matters. The contact wheel must sit at roller height — too low or too high and the contact slips off.
• Friction matters. High-grip wheel materials (flex wheels, rubber) drove rollers more reliably than smooth plastic.
• Sensor integration. The Optical Sensor (per VEX Library) reports roller color, allowing teams to automate the "stop at my color" logic. Without sensors, drivers timed it manually.
• Contact-time vs. release. The roller has to be rotated until the pointer-defined area is solid color — depending on starting state, this is a partial rotation. Teams tuned spin time empirically.

Roller Strategy (documented patterns)

1. Autonomous Win Point requires both rollers on your side AND scoring 2 discs in your alliance high goal. Top auton routines hit both objectives. The AWP is one extra Win Point in tournament rankings — valuable for seeding.
2. Late-season meta convergence per public VEX Forum discussion: "overflow disks in the high goals and then focus on rollers and take the corners" — meaning, prioritize disc scoring early, roller ownership mid-match, and tile coverage in endgame.
3. Roller contests — because rollers can be re-spun any time, both alliances may exchange roller ownership multiple times during a match. The state at the buzzer is what scores.

The Override Roller Hook

If Override has any rotational state-flip scoring element, the Spin Up patterns transfer:

• Integrate roller contact into your existing intake mechanism (Disco pattern) to save motor ports.
• Use an Optical Sensor for automated color/state detection rather than driver timing.
• Tune wheel height precisely to the scoring element's geometry.
• Plan auton routines around any AWP that includes roller-style requirements.

How Tile Coverage Worked

Per the manual: at the end of the match, alliances received a 3-point bonus for each tile their robots are covering, excluding the tiles that make up the low goals. Critically: during the last 10 seconds of the match, there are no horizontal expansion limits.

Practically: in the first 1:50 of the match, robots had to fit within standard size constraints (typically the 18′′ cube). Once the final 10 seconds began, robots could expand horizontally to any size. Whichever tiles your expanded robot was covering at the buzzer scored 3 points each.

Endgame Mechanism Archetypes

Strategic Patterns

Commit Timing

The 10-second window was tight. Robots had to:

1. Position themselves at high-tile-count locations (away from low goals)
2. Trigger the deployment mechanism
3. Wait for full deployment (1–3 seconds typically)
4. Hold position until buzzer

Triggering too late risked an incomplete deployment at the buzzer (low score). Triggering too early gave opponents time to flip your rollers or descore your discs while you were committed to the endgame.

Tile Selection

Some tiles were worth more than others — specifically, tiles in the "dead center" of the field that were hard to occupy normally. Top alliances coordinated to cover non-overlapping high-value tiles, maximizing point yield.

Denial Strategy

Wallbot specialists dedicated themselves to physically blocking opponent endgame. If a string-launcher robot expected a clear lane to deploy, a wallbot pushing them out of position at 0:08 could destroy 30+ points of expected scoring.

Why This Matters for Override

If Override has a tile-coverage, position-claim, or expansion-based endgame — the Spin Up endgame archetypes apply. More importantly, the strategic pattern of having a dramatic mechanism deployment in the final seconds (with everything that entails for timing, coordination, and denial) directly transfers to king-of-the-hill style endgames.

Drive Standard

The most common competitive drive was 4-motor or 6-motor tank, blue cartridge with reduction to ~360–450 RPM, on 3.25′′ or 4′′ omnis.

Why X-Drive Was More Common Than Usual

Spin Up saw moderate X-drive adoption among shooter specialists. Reasoning:

• Strafing helped aim refinement. Once positioned roughly facing a goal, small lateral adjustments via strafe were faster than turning + repositioning.
• Field perimeter access. Rollers were on the field perimeter. X-drives could approach a roller, flip it, and strafe sideways to the next roller without rotating — faster than tank turning.
• The endgame expansion benefited from omnidirectional positioning.

That said, tank still won most regions. The trade-offs were close enough that team driver skill mattered more than drive choice.

Disc Cycle Time as the Variable

Top Spin Up teams achieved disc cycle times of:

• ~0.5–0.7 seconds per disc (intake to shot) for fast flywheels
• ~1.0–1.5 seconds per disc for catapults
• ~2.0+ seconds per disc for pneumatic punches

The drive's job was to feed the shooter discs as fast as the shooter could fire. A drive that took 2 seconds to return to the disc spawn point bottlenecked any shooter that could fire faster.

Universal Lessons

• Rollers / state-flip elements need contact-driven mechs. Powered scrap wheels are the cheapest reliable solution — do not over-engineer.
• Color-sensor integration for automated state detection beats manual timing every time.
• Multi-archetype seasons reward picking what your team can build well, not theoretical-optimum chasing.
• Last-seconds expansion rules, when allowed, completely change endgame mechanism design space.
• Cycle time remains the dominant variable for projectile / repeated-action games.

Mechanism-Specific Transfer

• Powered scrap wheel roller mech — if Override has any rotating scoring element, this is the proven baseline.
• Intake bars that double as roller contactors — motor-saving design pattern that transfers.
• String launchers / wing deployments — if Override has tile-coverage or position-claim endgame.
• Disc shooters — if Override has any projectile scoring, flywheel and catapult archetypes from Spin Up are the design-space starting points.

Strategic Patterns

1. Auton AWP as primary autonomous goal — if Override has an Autonomous Win Point, design auton routines around hitting AWP first.
2. Last-second state flips — if any scoring element in Override can be flipped, reserve cycles for last-seconds defense and theft.
3. Defensive specialty — wallbots / blockers exist when endgame is high-value. Plan for facing them, even if your team doesn't play one.

Override Hooks (Speculation, Pre-Manual)

• If Override has rollers, swings, or rotating scoring, the Spin Up roller mechanism playbook applies directly. Powered wheel = first-pass solution.
• If Override has projectile scoring, flywheel single-stage shooter is the proven default.
• If Override has end-of-match expansion permitted, plan for at least one team in your alliance to have a deployable endgame mechanism.
• Color sensor integration — whether or not Override has rollers, color sensors are now commodity hardware in V5RC. If your team has not used them, this is an offseason skill to develop.

Recommended Pre-Override Prep

1. Watch a 2023 Spin Up Worlds match or two. Pay specific attention to how teams handled the rollers — the mechanisms and the timing.
2. If Override has rollers, prototype a powered-wheel roller mech in your first weekend with the manual. It is fast to build and gives you a working subsystem to iterate from.
3. Practice color-sensor calibration as an offseason exercise — the procedure is mechanically simple but the calibration nuances take a session to learn.
4. If Override has end-of-match expansion, plan a deployable endgame mechanism early — do not bolt it on at the last minute.

Related Guides