VEX V5RC Override Game Manual

Prefix

Changelog

Version 0.2 - June 4, 2026

• Updated a typo in the Game Design Philosophy to clarify that the Endgame is 10 seconds long
• Revised <SC2>, <SC3>, <SC4>, <SC5>, <SC8>, <SG9>, <SG10>, <RSC3>, <VUG6> and their corresponding figures for clarity, in regards to Pins that are Placed / Scored
• Updated <R11> to clarify intent
• Updated <R23a> to allow anodizing, painting, dyeing, or otherwise changing the color of any legal VEX parts (other than for official events held in mainland China)
• Updated <T6> to add white tape in place of blue/red tape for Load Zones as a permissible Field modification
• Revised tiebreakers in <T22>
• Added figures to Section 6 to show the starting configuration of a VEX U Head-to-Head Match
• Updated <VUG4> to clarify that both Cups and Pins may be introduced into the Loaders in VEX U Matches
• Added a note to <R11> and <VUR11> to clarify that the 55W drivetrain motor restriction does not apply to VEX U
• Added new drawings to Appendix A for Toggle starting orientation, and AprilTag numbering locations
• Added new definitions for Plowing, Possession and Scored to Appendix B
• Other minor typo / formatting fixes

Version 0.1 - April 27, 2026

• Initial release

Quick Reference Guide

Section 1 - Introduction

About the Game Manual

The VEX V5 Robotics Competition Game Manual is the most authoritative source of information for the VEX V5 Robotics Competition. Contained within this document are all of the rules, boundaries, constraints, and other relevant information you will need to properly understand and play this year’s game.

This manual is:

• A technical reference document for gameplay, Robot construction, and event operation
• A binding set of rules for Teams, coaches, referees, Event Partners, and all other volunteers and participants to adhere to
• The primary source of truth for all things related to the VEX V5 Robotics Competition
  

This manual is not:

• A strategy guide to score the most points
• An instruction set to build the best Robot
• A replacement for referee training, Event Partner training, or other event procedure

How to Read the Game Manual

The rules in this game manual are intended to work together to create a system of constraints. These rules are not intended to be understood independently of one another or in isolation from other information contained in this document. Many situations may require Teams, referees, or other volunteers to use logic from multiple places in the manual to properly form an interpretation. It is critical that the entire manual is read and understood, not just parts.

Information in the game manual is presented in the following ways:

Definitions in Appendix B establish the meaning of a term with regards to this document. Sometimes, these definitions may not perfectly match a more commonly accepted dictionary definition. In that case, the VEX definition takes precedence. If there is no VEX definition for a term, it can be reasonably assumed that a dictionary definition can be used.

General Rules establish the baseline rules for competition that Teams must adhere to at all times. These include, but are not limited to, conduct at an event, roster eligibility, competition integrity, and authority and enforcement.

General Game Rules begin to outline the rules that Teams must follow in every VEX game, not just the rules specific to this season’s game. Many of these rules do not change from year to year, and help prevent the game from devolving into immediate chaos.

Scoring Rules define how points are earned and evaluated.

Specific Game Rules describe what Robots and Drive Team Members may and may not do during a Match, specifically for this season’s game. These rules are subject to change from year to year, depending on how the game is designed and meant to be played.

Robot Rules define how Robots may be built and configured.

Tournament Rules describe how competitions are run, and how Teams are ranked at events.

Some rules also reference Violation Notes that are located in Appendix C. These notes provide additional guidance on enforcement, escalation, or special circumstances. If a rule doesn’t include a cross-reference to Violation Notes, standard Violation definitions apply. See Appendix C for information about rule Violations and penalties.

There are also red boxes of text placed in some areas of the game manual. These are intended to provide further clarification and guidance in places that the Game Design Committee has deemed may benefit from things being said a different way, or presented slightly differently. Red Boxes are meant to be supplements to, not replace, rules or definitions.

Game Manual Updates

This manual will have a series of “major” and “minor” updates over the course of the season. Each version is official and must be used in official V5RC events until the release of the next version, upon which the previous version becomes void.

The latest version of the Game Manual can always be found at https://link.vex.com/docs/26-27/v5rc/game-manual.

Known major release dates are as follows:

In addition to these known major updates, there may also be unscheduled updates released throughout the season if deemed critical by the Game Design Committee.

Any scheduled or unscheduled updates will always be released on a Thursday, no later than 5:00 PM CST (11:00 PM GMT). These updates will be announced via the VEX Forum, automatically pushed to the VEX V5 Hub app, and shared via VEX Robotics social media & email marketing channels. Once announced, the new version of the Game Manual will be immediately available at the link above.

Generally, Game Manual updates, scheduled or unscheduled, will include a grace period before the updated rules go into effect for competitions. See the release table above for specific dates. This grace period does not apply to the Version 0.1 Release, which serves as the initial rule set for the season.

Any events that begin before the 7-day grace period has ended must continue using the rules from the previous Game Manual Release. This policy ensures fairness and consistency, allowing Teams to adapt their strategies and gameplay accordingly before the changes are enforced in official competitions.

Once a manual update occurs, the previous version will be re-uploaded with an “Obsolete” watermark. Those will be found at https://link.vex.com/docs/26-27/v5rc/game-manual-obsolete and will be available to reference through the rest of the season.

The Game Design Committee reserves the right to enforce critical updates to the Game Manual as effective immediately upon release, if we feel that the changes are critical for competitive integrity, safety, and/or other extenuating circumstances.

Multi-week league events (or similar) that cross over a grace period should use the version of the Game Manual that is in effect at the beginning of each league session. Leagues should update to new versions of the Game Manual between sessions as appropriate.

The Q&A System

When first reviewing a new robotics game, it is natural to have questions about situations which may not be immediately clear. Navigating the Game Manual and seeking out answers to these questions is an important part of learning a new game. In many cases, the answer may just be in a different place than you first thought - or, if there is no rule explicitly prohibiting a gameplay strategy, then that usually means it is legal!

However, if a Team is still unable to find an answer to their question after closely reviewing the relevant rules, then every Team has the opportunity to ask for official rules interpretations and clarifications in the VEX Robotics Question & Answer System. These questions may be posted by a Team’s Adult representative via the events.vex.com account that is associated with that Team.

All responses in this Q&A system should be treated as official rulings from the VEX Robotics Game Design Committee, and they represent the correct and official interpretation of the VEX V5 Robotics Competition rules. The Q&A system is the only source besides the Game Manual for official rulings and clarifications, and is functionally an extension of the Game Manual. Unlike Game Manual updates, Q&A rulings are effective immediately upon release.

The VEX V5 Robotics Competition Question & Answer System will open May 14th, 2026.

Before posting on the Q&A system, be sure to review the Q&A Usage Guidelines:

1. The Q&A system is for rules clarifications only.
2. Only registered Teams, certified Event Partners, and certified V5RC Head Referees can post questions.
3. Read and search this Game Manual before posting.
4. Read and search existing Q&As before posting.
5. Quote the applicable rule from the latest version of this Game Manual in your question.
6. Make a separate post for each question.
7. Use specific and appropriate question titles.
8. Questions will (mostly) be answered in the order they were received.
9. This system is the only source for official rules clarifications.
10. The Game Design Committee cannot and will not overrule a Head Referee’s decision.

If there are any conflicts between the English-language PDF of the Game Manual and other supplemental or translated materials (e.g., referee training materials, the V5RC Hub app, the game reveal video, a translated game manual, etc.), the most current version of the English-language PDF of the Game Manual takes precedence.

Similarly, it can never be assumed that definitions, rules, or other materials from previous seasons apply to the current game. Q&A responses from previous seasons are not considered official rulings for the current game. Any relevant clarifications that are needed should always be re-asked in the current season’s Q&A.

Hierarchy of Information

There is no rule in this game manual that is more important than another rule. All rules are intended to be enforced with the same vigor.

The following hierarchy applies when determining official rulings while using information from beyond the Game Manual:

1. The most current English-language PDF of this Game Manual
2. Official rulings published in the VEX Robotics Question & Answer (Q&A) system
3. All other supplementary documents, policies and media

The latest version of the game manual supersedes all previous versions once effective (see the Game Manual Updates section, for more information). If discrepancies exist between this manual and other materials (videos, apps, translations, training documents), the latest version of the English-language PDF version of this manual takes precedence.

Section 2 - The Game

VEX V5 Robotics Competition Override: A Primer

VEX V5 Robotics Competition Override is played on a 12’ x 12’ square Field, set up as illustrated in the figures throughout this manual.

In Head-to-Head Matches, two (2) Alliances — one (1) “red” and one (1) “blue” — composed of two (2) Teams each, compete in Matches consisting of a fifteen (0:15) second Autonomous Period followed by a one minute and forty-five second (1:45) Driver Controlled Period.

The object of the game is to attain a higher score than the opposing Alliance by stacking Pins and Cups on Goals, setting Toggles to your Alliance color, and ending the Match with your Robot in the contested Midfield.

An Autonomous Win Point is awarded to any Alliance that completes a set of assigned tasks by the end of the Autonomous Period.

An Autonomous Bonus is awarded to the Alliance that has the most points at the end of the Autonomous Period.

Teams may also compete in Robot Skills Matches, where one (1) Robot tries to score as many points as possible. See Section 3 for more information.

At the VEX U Collegiate level, Teams play in a modified Tournament with a 30-second Autonomous Period and additional Robot build challenges. See Section 6.

Field Overview

The V5RC Override Field consists of the following:

• 56 Cups
  • 20 Match Loads
    • 10 for red Alliance
    • 10 for blue Alliance
  • 24 that start the Match in predetermined locations on the Field (gray side up)
  • 12 that start the Match in predetermined locations on the Field (clear side up)
    
• 63 Pins
  • 4 red/blue that start the Match in predetermined locations
  • 20 red/yellow
    • 2 Preloads
    • 10 Match Loads
    • 8 that start the Match in predetermined locations
  • 20 blue/yellow
    • 2 Preloads
    • 10 Match Loads
    • 8 that start the Match in predetermined locations
  • 19 yellow/yellow
    • 2 Match Loads
    • 17 that start the Match in predetermined locations
      
• 9 Goals
  • 4 Alliance colored
    • 2 red
    • 2 blue
  • 5 neutral colored
    • 4 short
    • 1 tall
      
• 4 Toggles
  
• 4 Loaders, two adjacent to each Alliance Station

Note: The illustrations in this section of the Game Manual are intended to provide a general visual understanding of the game. Some figures may highlight or change the appearance of certain Field Elements and Scoring Objects to emphasize or clarify intent.

Teams should refer to official Field specifications, found in Appendix A, for exact Field dimensions, a full Field bill of materials, and exact details of Field construction.

Game Design Philosophy - A Letter from the GDC

We want to take the opportunity to explain how this game was designed and what kind of gameplay we expect to see during the season. This section also points out parts of the game that we will watch closely in case updates are needed.

This is not a rules section. It does not add any new rules. Instead, it helps you understand the purpose of the game and what we as designers had in mind.

What This Game is About & Scoring

Override is a game that focuses on stacking and teamwork. We intend for Teams to work together with their Alliance partners to assemble stacks, gain points using Scoring Objects, and control Toggles to outscore their opponents.

Because of this, success in the game is not just about building a good Robot. It also depends on how well you:

• Communicate with your partner
• Plan your strategy
• Time your actions during a Match

Teams that coordinate well and make smart decisions will have an advantage.

The game is designed so that most points come from constructive actions, such as:

• Building stacks
• Flipping Toggles
• Positioning your Robot effectively

Interaction with the opposing Alliance is still an important part of the game. However, Matches cannot be dominated by tearing down what the other Alliance has built. Some defense and disruption is expected, but the main focus should stay on building and scoring.

If strategies that focus mostly on preventing stacks become too common, the Game Design Committee may consider making changes to ensure the game remains interesting with many strategy choices. We will look at how often these strategies are used and how they affect gameplay compared to our intentions.

Large Point Swings with Toggles and Yellow Pins

The scoring values in Override are designed to encourage dynamic strategy and decision making. Because of this, it is possible for actions like controlling Toggles or scoring yellow Pins to create large point swings during a Match.

These moments can be exciting, but they should not become the only way to win. Teams should still have multiple viable strategies, including building stacks and competing in the Endgame.

We will monitor how these point swings impact Matches throughout the season. If they begin to outweigh other scoring opportunities or reduce strategic variety, the Game Design Committee may adjust point values to maintain a balanced and engaging game.

The Endgame: Final 10 Seconds

The last 10 seconds of the Match are designed to feel more intense and competitive. During this time, the game shifts to a “king of the hill” style challenge in the Midfield. This section of the Match will likely include increased Robot interaction. As such:

• Positioning and timing become critical
• Robot durability matters more

Teams should expect more crowded and contested conditions than earlier in the Match.

At the same time, there are still rules in place (like limits on how Robots can expand) to help prevent issues such as tipping over or getting tangled with other Robots. If the Endgame consistently leads to problems like Robots getting stuck, tipping too often, or not being able to recover, the Game Design Committee may adjust rules to keep Matches fair and playable.

Using Sensors in the Game

Override is a game where sensors can be very helpful. Tools like AI Vision Sensors and Optical Sensors can help your Robot :

• Identify objects
• Interact with Toggles
• Navigate the Field

The Game Design Committee will work to support sensor use through Field and game design. However, real-world conditions are not always perfect. Lighting and object placement may vary. Because of this, Teams should design and code their Robots so their sensors can handle small changes and still work reliably during a Match.

In addition, Robot rules will continue to be reviewed to make sure the game stays fair throughout the season. One important focus is preventing Teams from building Robots that could interfere with sensors in unfair ways like intentionally trying to confuse sensors or adding parts that look like Field Elements.

Making sure all Teams can rely on their sensors to work as expected is an important part of fair competition.

Have a great season!

- The VEX V5 Robotics Competition Game Design Committee

Scoring

<SC1> All scoring statuses are evaluated after the Match ends. Scores are calculated five seconds after the Match ends, or once all Scoring Objects, Field Elements, and Robots on the Field come to rest, whichever comes first.

1. This 5-second delay is intended to be the only permitted “benefit of the doubt” for last-second scoring actions. If an object or Robot is still in motion and “too close to call” between two states at the 5-second mark, then the less advantageous of the two states should be awarded to the Robot (s) in question. A Robot which is breaking the plane of the Midfield but slowly droops down and away from the Midfield at five (5) seconds would not be considered in the Midfield.
2. At the end of the Match, the on-screen timer displayed by Tournament Manager will hold the current Match information and “0:00” for five (5) seconds before moving to queue the next Match. This should be the primary 5-second visual cue used by Teams and Head Referees.
3. This 5-second delay is only intended to be a “benefit of the doubt” grace period, not an extra five seconds of Match time. Robots which are designed to strategically exploit this grace period will receive a Minor Violation, and any post-Match movement will not be included in score calculation (i.e., the Match will be scored as it was at 0:00).
4. Referees should avoid contacting or moving Robots and/or Scoring Objects as much as possible while evaluating scoring statuses. If an object must be moved to evaluate the status of another object, its status must be agreed upon by all Teams and the Head Referee, and noted or recorded, before it is moved.
5. Referees must record counts based on verified scoring statuses evaluated after the Match, using final positions of Scoring Objects, Field Elements, and Robots. Point considerations used to determine whether a Violation is Match Affecting (e.g., specified in Violation Notes) should NOT be added to or deducted from the actual score, and points scored during a Violation should not be deducted from a score.

<SC2> Placed Scoring Object criteria.

1. A Pin is considered Placed if it meets all of the following criteria:
   1. The Pin is partially or entirely nested with a Goal, or with a Cup that is partially or entirely nested with another Placed Pin.
   2. Each Goal and/or each half of a Cup nested with that Pin contains a maximum of one Pin half. (See Figure SC2-2.)
2. A Cup is considered Placed if it meets the following criteria:
   1. The Cup is partially or entirely nested with a Placed Pin.

In the context of <SC2>, nested means that one half of a Pin is partially or completely contained within the inner volume of the Cup. In other words, the Pin is breaking an imaginary plane at the opening of a Cup, in any way. Robot contact does not matter for the purposes of <SC2>, and a Robot that is contacting or Possessing a Pin that still meets the criteria presented in <SC2> does not negate the Placed status, provided no other rules are broken (particularly <SG6>.

<SC3> Each Pin consists of two halves. Each Placed Pin can have zero, one or two Scored halves. To count as Scored for the corresponding Alliance, the half of the Placed Pin must remain fully visible (i.e., cannot be partially or fully nested inside the opaque half of a Cup).

1. Each visible red half of a Placed Pin counts as a Scored red Pin, earning points for the red Alliance.
2. Each visible blue half of a Placed Pin counts as a Scored blue Pin, earning points for the blue Alliance.
3. Each visible yellow half of a Placed and Owned Pin counts as a Scored yellow Pin, earning points for the Alliance that Owns the Pin. (See <SC5>.)

<SC4> A Toggle is considered set to a color when it meets all of the following criteria at the end of the Match :

1. The Toggle must be fully seated, such that there is a face of the Toggle in contact and parallel with its mounts on the Field Perimeter at rest. (see Figure SC5-1)
2. The Toggle is not in contact with a Robot from either Alliance.

If a Toggle is not considered set to a color, it is considered a neutral (yellow) Toggle by default, and neither Alliance receives Ownership of the yellow Pins Placed in that Quadrant. While the Toggle has infinite potential orientations, only three discrete orientations are considered scored states.

<SC5>Yellow Pin Ownership. Each Placed Pin with one or more yellow halves can be Owned by an Alliance.

1. A yellow Pin Placed in a Quadrant is Owned by an Alliance if the Toggle in that Quadrant is set to the Alliance's color. If the Toggle is set to yellow, Placed yellow Pins in that Quadrant are not Owned and do not score points. (See <SC3>.)
2. A yellow Pin Placed in the Midfield is Owned by the Alliance that ends the Match with a greater number of Robots in the Midfield. (See <SC6>.)
   1. If both Alliances end the Match with an equal number of Robots in the Midfield, yellow Pins Placed in the Midfield are not Owned and do not score points.

Toggle: Yellow	Toggle: Blue	Toggle: Red
Red Pins: 15 points	Red Pins: 15 Points	Red Pins: 15 Points
Blue Pins: 5 Points	Blue Pins: 5 Points	Blue Pins: 5 Points
Yellow Pins: 0 Points	Yellow Pins: 30 Points (Scored for Blue)	Yellow Pins: 30 Points (Scored for Red)
Total Red : 15 Points / Blue : 5 Points	Total Red : 15 Points / Blue : 35 Points	Total Red : 45 Points / Blue : 5 Points

<SC6> A Robot counts as being in the Midfield if any part of the Robot is within the infinite 3D vertical projection of the Midfield at the end of the Match.

<SC7> Scoring of the Autonomous Bonus is evaluated immediately after the Autonomous Period ends.

1. Points for ending the Autonomous Period in the Midfield are not included in the calculation of an Alliance’s score for the purposes of determining the Autonomous Bonus.
2. If the Autonomous Period ends in a tie, including a zero-to-zero tie, each Alliance will receive an Autonomous Bonus of six (6) points.
3. Any Violations, Major or Minor, committed during the Autonomous Period will result in the Autonomous Bonus being automatically awarded to the opposing Alliance. See <GG13>.
4. Per rule <GG13>, if both Alliances commit Violations during the Autonomous Period, then no Autonomous Bonus will be awarded.

This rule is applied differently for VEX U. See Rule <VUG5>.

<SC8> An Autonomous Win Point is awarded to any Alliance that ends the Autonomous Period with all of the following tasks completed, and that has committed no Violations during the Autonomous Period :

1. At least seven (7) Pins Scored for your Alliance. (Does not include Pins Scored in Quadrants on the opposing side of the Autonomous Line )
2. At least three (3) Goals each contain at least two (2) Pins Scored for your Alliance. (Does not include Goals in Quadrants on the opposing side of the Autonomous Line )
3. Neither Robot is contacting the Field Perimeter

Autonomous Win Point criteria will be slightly modified for events which qualify directly to the World Championship (e.g., Event Region Championships and Signature Events) and may be further modified for the World Championship.

The modified criteria for events which qualify directly to the World Championship will be released in the September 3, 2026, Game Manual update. Any Championship-qualifying events held prior to September 10, 2026, will use the standard criteria listed in this rule.

The modification(s) will be minor, and will be intended to provide an increased challenge over the criteria listed above. For example, one possibility could be “At least eight (8) Pins Scored” instead of seven (7) and/or “At least four (4) Goals” instead of three (3). The standard criteria for all other events will not change.

This rule is applied differently for VEX U. See Rule <VUG6>.

Specific Game Rules

<SG1> Starting a Match. Prior to the start of each Match, each Robot must be placed such that it meets all of the following criteria:

1. No larger than 18” (457.2 mm) long by 18” (457.2 mm) wide by 18” (457.2 mm) tall.
2. Not contacting any Scoring Objects other than a maximum of one (1) Preload. See rule <SG5>.
3. Not contacting Goals, Loaders, Load Zones, or Toggles.
4. Not contacting any other Robots, and not sharing a Quadrant with another Robot.
5. Completely stationary (i.e., no motors or other mechanisms in motion).
6. Contacting the Field tiles and Field Perimeter on their Alliance’s side of the Autonomous Line.
   

Note: Using external influences, such as Preloads or the Field Perimeter, to maintain a Robot's starting size is only acceptable if the Robot would still satisfy the constraints of <R3>defterm and pass inspection without these influences.

This rule has additional Violation notes. See Appendix C.

Clause A of this rule is applied differently for VEX U. See Rule <VUG1> and <VUG3>.

<SG2> Horizontal expansion is limited. Once the Match begins, Robots may expand horizontally beyond the starting size limit within the following criteria:

1. The Robot can never be larger than 24” wide or 24” long (must always be able to fit within a 24”x24” square horizontal footprint).

Teams should be aware that Robots may incidentally expand horizontally while extending vertically (e.g., mechanisms that arc, swing, or deploy upward). Upon request, Teams must be prepared to demonstrate that their Robot does not exceed the maximum size constraint of 24” x 24” at any point, including while any vertical expansion mechanisms are in use.

This rule has additional Violation notes. See Appendix C.

<SG3> Vertical expansion is limited. Once the Match begins and until the Endgame period begins, Robots may expand vertically beyond the starting size limit, but no part of the Robot may exceed an overall height of 50” at any point during the Match (must always be able to fit within a hypothetical 50” vertical sizing box).

<SG4> Keep Scoring Objects in the Field. Teams may not remove Scoring Objects from the Field. A Scoring Object that leaves the Field during Match play, intentionally or unintentionally, will be returned to the Field in a location near where it left, in contact with the Field tiles and the Field Perimeter but no other Field or Scoring Objects and no Robots. Volunteers should return Scoring Objects as quickly as possible, but this time will vary between Events and Matches, and any delay in returning an object should not be considered Match Affecting or cause for a replay.

1. If a Scoring Object is leaving the Field (as determined by the Head Referee ), but is deflected back into the Field by a Drive Team Member, field monitor, ceiling/wall, or other external factor, it should still be considered “out of the Field ” and removed by a Scorekeeper Referee or Head Referee. If the redirection occurred due to contact with a Drive Team Member, it will be at the Head Referee’s discretion whether or not <GG4> (hands out of the Field ) should apply.
2. A Scoring Object that comes to rest on top of the Field Perimeter is still considered to be inside the Field unless it contacts something outside of the Field (e.g., volunteer, Drive Team Member, field monitor, etc.), and cannot be retrieved by a Drive Team Member or volunteer.
   

   This rule has additional Violation notes. See Appendix C.

<SG5> Each Robot gets one Pin as a Preload. Red Alliance Preloads are red/yellow Pins ; blue Alliance Preloads are blue/yellow Pins. Prior to the start of each Match, each Preload must be placed such that it meets all of the following criteria:

1. Contacting one Robot of the same Alliance color as the Preload.
2. Not contacting the same Preload as another Robot.
3. Not contacting other Scoring Objects.
4. Not contacting any other Goals, Loaders, Load Zones, or Toggles.
   

Note: If a Robot is not present for their Match, then that Robot’s Preload may be used as a Match Load in accordance with <SG11>.

This rule has additional Violation notes. See Appendix C.

<SG6> Possession is limited to a maximum of one Pin and one Cup. Robots may not have Possession of more than one (1) Pin at once. Robots may not have Possession of more than (1) Cup at once. Robots in Violation of this rule must immediately stop all actions except for attempting to remove the excess Scoring Objects.

If they are unable to remove the excess Scoring Objects, then they must return to a legal starting position (as described by <SG1> ). They will not be eligible to receive points for ending the Match in the Midfield, and cannot interact with Toggles, Goals, or other Scoring Objects while in Possession of excess Scoring Objects.

1. Plowing multiple Scoring Objects is permitted. Teams which employ Plowing strategies are encouraged to clearly demonstrate that none of the Scoring Objects are being Possessed, e.g., by using a flat face of the Robot with no active mechanisms.

<SG7> Don’t cross the Autonomous Line, and don’t interfere with your opponents’ actions. During the Autonomous Period, Robots may not contact foam tiles, Scoring Objects, or Field Elements which are on the opposing Alliance’s side of the Autonomous Line.

1. The Autonomous Period should be primarily Offensive, with Teams focusing on scoring and executing strategic maneuvers rather than Defensive disruption. Teams should avoid actions that are primarily Defensive in nature, including but not limited to:
   1. Intentionally disrupting Scoring Objects or Field Elements on the opponent’s side of the Autonomous Line.
   2. Deliberately contacting an opponent’s Robot to interfere with their autonomous path.
2. Scoring Objects that begin the Match in contact with the Autonomous Line are not considered to be on either side, and may be utilized by either Alliance during the Autonomous Period. For the purpose of this rule, all 20 Scoring Objects that begin the Match on or at the Autonomous Line are considered to be in contact with the Autonomous Line. See Figure SG-7.
3. While incidental contact or unintentional interactions may occur with Robots on the other side of the Autonomous Line, Teams that employ deliberate Defensive autonomous strategies that impact their opponents’ autonomous routines may be subject to Minor or Major Violations at the discretion of the Head Referee.
4. Teams cannot intentionally place Scoring Objects on the opponent’s side of the Autonomous Line.
5. Contact with either of the following during the Autonomous Period will result in the Autonomous Bonus and an Autonomous Win Point being awarded to the opposing Alliance, unless the opposing Alliance also breaks rules in the Autonomous Period :
   1. An opponent Robot that isn’t interacting with the Autonomous Line, objects that begin the Match positioned above or in contact with the Autonomous Line, or the Midfield (see <SG8> ).
   2. Scoring Objects on the other side of the Autonomous Line.
      

This rule has additional Violation notes. See Appendix C.

<SG8> Engage with the Midfield and/or Autonomous Line during the Autonomous Period at your own risk. Any Robot that engages with the Midfield and/or Scoring Objects that begin the Match on the Autonomous Line should be aware that opponent Robots may also choose to do the same. Per <GG12> and <GG13>, Teams are responsible for the actions of their Robots at all times.

1. For the purposes of this rule, “engages with” means any combination of:
   1. Contacting foam tiles within the Midfield
   2. Contacting the Goal in the Midfield
   3. Contacting Scoring Objects that begin the Match on the Autonomous Line
2. If opposing Robots contact one another while both engaging with the Midfield or the Autonomous Line, and a possible <GG14> Violation occurs (e.g., damage, Entanglement, or tipping over), a judgment call will be made by the Head Referee within the context of <GG14> and <GG15> (just as it would if the interaction had occurred during the Driver Controlled Period ).
3. If opposing Robots contact one another while both engaging with the Midfield or Autonomous Line, and an incidental Violation of <SG4> occurs, no penalty will be assessed on either Alliance.
4. Intentional, strategic, repeated, or egregious offenses, such as negatively impacting Robots that are not engaging with the Midfield or the Autonomous Line, may still be deemed a Violation of <GG13>, <GG14>, <GG15>, <SG7>, <G1>, and/or <S1> at the Head Referee’s discretion.

The Midfield and the Scoring Objects that begin on the Autonomous Line are intended to be utilized by both Alliances during the Autonomous Period. This will inevitably result in Robot -on-Robot interactions, both incidental and intentional. The overarching intent of <SG8> is for the vast majority of these interactions to result in no rule Violations and / or penalties for either Alliance, just as no rules Violations occur in 99% of Driver Controlled interactions.

Teams are responsible for the actions of their Robots at all times. A Robot with a small wheel base, which tips over every time they enter the Midfield and contacts an opponent, should not attempt to claim a <GG14> Violation on their opponent.

With that being said, the Midfield is a neutral zone, not a “free-for-all” zone. The intent of clause D is to provide Head Referees with the leeway to still make a judgment call, if needed, when a Team has chosen to exploit this rule beyond its intent. Reckless or unsafe strategies aimed solely at the destruction, damage, tipping over, Entanglement, Trapping, or forcing of an opponent into a penalty are still prohibited in the VEX Robotics Competition.

<SG9> Alliance Goals are protected. Robots may not directly or indirectly interact with the opposing Alliance-colored Goals. This includes both Placing Scoring Objects and removing Placed Scoring Objects.

This rule has additional Violation notes. See Appendix C.

<SG10> Placed Scoring Objects cannot be removed from neutral or opposing Alliance-colored Goals. Robots may only remove Placed Scoring Objects from a Goal if that Goal matches their Alliance color.

This rule has additional Violation notes. See Appendix C.

<SG11> Match Loads may be introduced during the Match under certain conditions. For the purpose of this rule, “introduce” refers to the moment when a Drive Team Member has released a Scoring Object into a Loader.

During this action, a Drive Team Member’s hands may temporarily break the plane of the Field Perimeter. This momentary interaction is an exception to rule <GG4>. Excessive, unnecessary, or unsafe actions while introducing a Match Load may be considered a Violation of <S1> and/or <G1> at the Head Referee’s discretion.

Drive Team Members may introduce Match Load Scoring Objects by placing a single Pin, a single Cup, or a nested Cup and Pin into either of their Alliance-colored Loaders. Scoring Objects can be introduced through the top of the Loader when the Loader is not lifted, or through the back of the Loader when the Loader is raised by a Drive Team Member.

1. Scoring Objects may only be introduced into Loaders during the Driver Controlled Period of the Match.
2. A Match Load Scoring Object may not be contacted by a Robot prior to being introduced into a Loader.
3. Match Load Scoring Objects may only be removed through the bottom opening of the Loader, by a Robot whose Alliance color matches the Loader.
   

This rule is applied differently for VEX U. See Rule <VUG4>.

This rule has additional Violation notes. See Appendix C.

<SG12> Some rules change during the Endgame period.

1. Vertical expansion is limited to 18” for any Robot that is partially or entirely within the infinite 3D vertical projection of the Midfield.
2. Robots that attempt to end the Match in the Midfield should expect vigorous interactions from opponent Robots. When a Robot is contacting or engaging with the Midfield, or is in proximity to the Midfield, incidental damage that is caused by opponent Robots pushing, tipping, or becoming Entangled with them would not be considered a Violation of <GG14>. Intentional damage or dangerous mechanisms may still be considered a Violation of <S1>, or <G1> at the Head Referee’s discretion.
   

   This rule is applied differently for VEX U. See Rule <VUG7>

Safety Rules

<S1> Be safe out there. 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. The Robot will require re-inspection as described in rule <R2> before it may take the Field again.

<S2> Students must be accompanied by an Adult. Every Student at a VEX Robotics Competition event must be supervised by a responsible Adult. The Adult must obey all rules and be careful to not violate Student-centered policies, but must be present for the full duration of the event in the case of an emergency. Violations of this rule may result in removal from the event and additional penalties.

<S3> Each Student Team member must have a completed participant release form on file for the event and season. A Student Team member cannot participate in an event without a completed release form on file.

<S4> Stay inside the Field. If a Robot is completely outside of the Field during a Match, it will receive a Disablement for the remainder of the Match.

Note: The intent of this rule is not to penalize Robots for having mechanisms that inadvertently cross the Field Perimeter during normal game play.

<S5> Wear safety glasses. Drive Team Members must wear eye protection. All Drive Team Members must wear some form of eye protection while at the Field for Matches. Safety glasses or other eye wear with side shields and non-shattering lenses are recommended. While in the pit and queuing areas, it is highly recommended that all Team members wear eye protection.

General Rules

<G1> Treat everyone with respect. All Teams and other attendees are expected to conduct themselves in a respectful and professional manner while participating in or attending VEX V5 Robotics Competition events. If a Team or any of its members (Students or anyone else associated with the Team or its members) are disrespectful or uncivil to event staff, volunteers, or fellow competitors, they may be Disqualified from a current or upcoming Match. Team conduct pertaining to <G1> may also impact a Team’s eligibility for judged awards. Repeated or extreme Violations of <G1> could result in a Team being Disqualified from an entire event, depending on the severity of the situation.

1. Event attendees are not allowed to record audio or video of Teams’ discussions with Head Referees or other event staff/volunteers.

This rule has additional Violation notes. See Appendix C.

<G2> V5RC is a Student-centered program. Adults should not make decisions about the Team’s /Robot’s build, design, coding, documentation, or gameplay, and should not provide an unfair advantage by providing ‘help’ that is beyond the Students’ independent abilities. Students must be prepared to demonstrate an active understanding of their design, Robot construction, programming, notebook, and strategies to judges or event staff. Students should build, design, and code the Robot with minimal Adult involvement. If a Team has an engineering notebook, the format, layout, and contents should be created and maintained by Students with minimal Adult involvement; Adults should not transcribe or type notebook entries or code for Students.

Some amount of Adult mentorship, teaching, and/or guidance is an expected and encouraged facet of VEX competitions. No one is born an expert in robotics! However, obstacles should always be viewed as teaching opportunities, not problems for an Adult to solve for the Team.

This rule has additional Violation notes. See Appendix C.

<G3> Use common sense. When reading and applying the various rules in this document, please remember that common sense always applies in the VEX V5 Robotics Competition.

<G4> All work must represent the skill level of the Students on the Team. All work must represent the skill level of the Students currently on the Team. Teachers, coaches, mentors, and peers can teach concepts, skills, and processes; demonstrate techniques; ask guiding questions; review/critique the Team’s work; and otherwise advise Team members. All final solutions used in competition (including the Team’s design, Robot, code, strategies, documentation, and ongoing work) must be the work of the Student Team members. Organizations should develop a plan that encourages and empowers Students to make their own decisions (see <G2> ).

1. Designs and code provided by VEX Robotics:
   1. Teams may use Robot plans and code (e.g., Hero Bots, VEXcode configurations, etc.) provided by VEX Robotics, but are encouraged to use these Robots, mechanisms, and code only as a starting point that Students modify, improve, or replace as their skills increase.
   2. Plans provided by VEX Robotics are the only legal plans available for use in competition.
2. Robot design and construction:
   1. Teams must avoid academic dishonesty and should not directly copy a Robot or mechanism other than those included in clause A. This includes, but is not limited to, the use of instructions, pictures, videos, notebooks, CAD designs, and/or any other documentation useful to the design process.
   2. Teams may be inspired by designs created by other Teams, and can use an idea from someone else to spark innovation, but are expected to clearly document and give credit to all ideas that are used for inspiration. The Team must describe how they made meaningful changes to the original idea to arrive at a design that is uniquely their own. It should be clear that this final implementation is not an exact copy of ANY other original design.
   3. Teams should demonstrate their design process in their engineering notebook, and provide it if asked to do so by event staff. Failure to demonstrate evidence of iteration, innovation, and/or modification will result in a Violation.
   4. Teams may only use custom parts (e.g., cut/shaped non-shattering plastic, or heavily modified legal VEX components) that were designed and created by the Students on that Team.
3. Robot code:
   1. Teams may use publicly available example code and/or custom libraries from outside sources. However, Student Team members must understand the resulting code, be able to explain all facets of their competition code, and be capable of independently creating code on a level equivalent to the code used on their Robot if asked to do so.
   2. Teams may not use Large Language Models, or similar forms of artificial intelligence (AI), to create or improve the code used in competition, as the resulting code does not reflect the skill level of the Students on the Team.
4. Engineering notebook:
   1. The Team’s engineering notebook must be the work of the Students on the Team, and cannot be edited, formatted, or revised by anyone other than the Students on the Team.
   2. Teams may not use Large Language Models, or similar forms of AI, to create or improve the content of their engineering notebook.
   3. Teams can be inspired by engineering notebooks and formats from other Teams and/or seasons, but must ensure that all content is original and created by the members of the Team.
5. Collaboration with other Teams :
   1. Teams can collaborate on game analysis, brainstorming, strategy, and other steps of the engineering design process, but the final solutions used/presented at competitions must be the independent work of the Students on each Team.
   2. Robots, code, and/or engineering notebooks that are identical or substantially similar to one another across Teams, whether they’re within the same school/organization/club or from separate organizations, are in Violation of this rule, regardless of whether they compete in the same or different events. Every Team is expected to put in the time, effort, and resources needed to undergo an independent design process and develop their own Robots and code.

This rule has additional Violation notes. See Appendix C.

<G5> Each Student can only belong to one Team. Each Team must include Drive Team Members, Coder (s), Designer (s), and Builder (s). Many also include Strategists and Notebooker (s). No Student may fulfill any of these roles for more than one VEX V5 Robotics Competition Team in a given competition season. Students may have more than one role on the Team (e.g., the Designer may also be the Builder, the Coder, and a Drive Team Member ).

1. Team members may only move from one Team to another for non-strategic reasons outside of the Team’s control.
   1. Examples of permissible moves may include, but are not limited to, changing schools, conflicts within a Team, or combining/splitting Teams.
   2. Examples of strategic moves in Violation of this rule may include, but are not limited to, one Coder “switching” Teams in order to program multiple Robots, one Student designing multiple Teams’ Robots, or one Student writing the engineering notebook for multiple Teams.
   3. If a Student leaves a Team to join another Team, <G4> still applies to the Students remaining on the previous Team. For example, if a Coder leaves a Team, then that Team’s Robot must still represent the skill level of the Team without that Coder. One way to accomplish this would be to ensure that the Coder teaches or trains a “replacement” Coder in their absence.
   4. Points ii and iii are intended to represent real-world situations that are found in industry engineering. If a vital member of a professional engineering team were to suddenly leave, the remaining members of the team should still be capable of working on / maintaining their project.
2. When a Team qualifies for a Championship event (e.g., States, Nationals, Worlds, etc.) the Students on the Team attending the Championship event are expected to be the same Students on the Team that was awarded the spot. Students can be added as support to the Team, but may not be added as Builders, Drive Team Members, Coders, or Notebookers for the Team.
   1. An exception is allowed if only one (1) member of the Team is able to attend the event. The Team can make a single substitution of a Drive Team Member or Coder for the Championship event with another Student, even if that Student has competed on a different Team. This Student will now be a member of this new Team and may not substitute back to the original Team during the season.

Note: Teams cannot “borrow” Students from other Teams to serve as Drive Team Members, Coders, Designers, Builders, or Notebookers. However, Teams can add permanent members throughout the season under the guidelines of this rule.

<G6> There is a difference between accidentally and willfully violating a Robot rule. Any Violation of Robot rules, accidental or intentional, will result in a Team being unable to play until they pass inspection (per <R2d>).

However, Teams who intentionally and/or knowingly circumvent or violate rules to gain an advantage over their fellow competitors are in Violation of the spirit and ethos of the competition.

This rule has additional Violation notes. See Appendix C.

General Game Rules

<GG1> Only Drive Team Members, and only in the Alliance Station. During a Match, Robots may be operated only by that Team’s Drive Team Members and/or by software running on the Robot’s control system in accordance with <R9> and <GG11>. A Team may send up to (3) Drive Team Members to their Alliance Station for each Robot, and those Drive Team Members must remain in their Alliance Station for the duration of the Match.

Drive Team Members are the only Team members that are allowed to be in the Alliance Station during a Match. Adults (other than event staff) are not permitted to be in the Alliance Station during a Match.

1. Drive Team Members are prohibited from any of the following actions during a Match :
   1. Using any sort of communication device in the Alliance Station. Non-headphone devices with communication features turned off (e.g., a phone in airplane mode, a walkie talkie turned off, smart glasses with communication features disabled) are allowed. Communication features can be enabled for translation apps during post-Match discussions.
   2. Standing or sitting on any sort of object during a Match, regardless of whether the Field is on the floor or elevated, except as required by an officially approved accommodation request.
   3. Bringing/using additional materials to simplify the game challenge during a Match (e.g., device to align or add Scoring Objects to a Loader.
   4. To ensure that Drive Team Members are aware of verbal calls during a Match (as an application of rules <T1>, <G1>, <S1>, and <G3> ), powered headphones, earbuds, passive earpieces connected to electronic devices, or other personal accessories/devices that transmit audio cannot be worn/used in the Alliance Station except as required by an officially approved accommodation request.
2. Individuals who are not Drive Team Members for a Match cannot provide directions, commands, or advice to the Drive Team Members during that Match. They’re welcome to provide cheerful, positive encouragement, but should not affect Match play or strategy.

This rule has additional Violation notes. See Appendix C.

<GG2> A Team’s Robot should attend every Match. The Team’s Robot must be in the Alliance Station or on the Field for the Team’s assigned Match, even if the Robot is not functional. If the Robot is not at the Field for the entire duration of the Match, the Team will be considered a “no-show” and receive zero (0) Win Points, Autonomous Win Points, Autonomous Points, and Strength of Schedule Points.

1. Teams are expected to participate in all scheduled Qualification Matches, Alliance Selection, and Elimination Matches (if they’re an Alliance Captain or were selected to join an Alliance for Elimination Matches ). Failure to attend scheduled Matches or Alliance Selection may be considered a Violation of <G1>. Teams that participate in zero Qualification Matches cannot be considered for judged awards.

<GG3> Robots on the Field must be ready to play. When a Team puts their Robot on the Field, it must be prepared to play (e.g., battery charged, sized within the starting size constraint, includes only the correct Alliance -color license plates, etc.).

1. Robots must be placed on the Field promptly. Repeated failure to do so could result in a Violation of <G1> and/or removal of the Robot from the current Match at the Head Referee’s discretion.
2. If a Robot is delaying the scheduled start of a Match, it may be removed from the Field at the discretion of the Head Referee and Event Partner. The Robot may remain at the Field so that the Team does not get assessed a “no-show” (per <GG2> ).
3. If a Robot is not placed on the Field prior to the start of a Match, it cannot be placed on the Field during that Match.
4. Teams who use VEX pneumatics must have their systems charged before they place the Robot on the Field.
5. If an event is using Smart Field Control and a Robot is unable to successfully connect to Smart Field Control prior to the scheduled start of a Match, the Head Referee may ask the Team to remove their Robot from the Field in accordance with clause B.
   1. A Robot that connects to Smart Field Control but displays a ‘Legacy Field Control’ error on the field monitor is NOT considered successfully connected to Smart Field Control, and may be removed from the Field if it is delaying the scheduled start of a Match.

<GG4> Hands out of the Field. During a Match, Drive Team Members are prohibited from making intentional contact with any Field Element, Robot, or Scoring Object that has been introduced to the Field, except for the contact specified in <GG4a> or while introducing Match Loads as described in rule <SG11>.

1. Drive Team Members are not permitted to reach into the 3-dimensional volume of the Field Perimeter at any time during the Match, apart from the actions described above. Rule <S1> applies.
2. Any concerns regarding Field Element or Scoring Object starting positions should be raised with the Head Referee prior to the Match. Team members may never adjust Scoring Objects or Field Elements themselves.
3. Transitive contact, such as contact with the Field Perimeter that causes the Field Perimeter to contact Field Elements or objects inside of the Field, could be considered a Violation of this rule.
4. During the Driver Controlled Period, Drive Team Members may only touch their own Robot if the Robot has not moved at all during the Match. Movement caused by an external force, such as another Robot, should not prevent a Drive Team Member from interacting with their Robot under this rule. Touching the Robot in this case is permitted only for the following reasons:
   1. Turning the Robot on or off.
   2. Plugging in a battery.
   3. Plugging in a V5 Robot Radio.
   4. Touching the V5 Robot Brain screen, such as to start a program.

<GG5> Match replays are allowed, but rare. Match replays (i.e., playing a Match over again from its start) must be agreed upon by both the Event Partner and Head Referee, and will only be issued in the most extreme circumstances. Some example situations that may warrant a Match replay are as follows (note that this is not an exhaustive list):

1. Match Affecting “Field fault” issues.
   1. One or more Field Elements and/or Scoring Objects starting in incorrect positions, and out of the allowed tolerances (see <T5> ).
   2. Tape lines lifting.
   3. Field Elements detaching or moving beyond normal tolerances (not as a result of Robot interactions).
   4. The Autonomous Period or Driver Controlled Period ending early.
   5. Field control disconnecting or Disabling multiple Robots. Note, this is sometimes confused with a Robot whose motors have overheated, or bent pins on a controller’s competition port causing intermittent drop-outs. In general, any true Field fault will impact both Alliances simultaneously, not one Robot at a time.
2. Match Affecting game rule issues.
   1. Head Referee Disables a Robot for a misinterpretation of a rule Violation.
   2. Head Referee starts the Driver Controlled Period of the Match without determining the outcome of the Autonomous Period winner.
3. The Field is reset before a score is determined.
4. A Match is run before its scheduled time without a Team.

<GG6> Disqualifications. When a Team receives a Disqualification in a Qualification Match, they receive a score of zero (0) for the Match, as well as zero (0) Win Points, Autonomous Win Points, Autonomous Points, and Strength of Schedule Points.

1. If the Team receiving the Disqualification is on the winning Alliance, then Teams on the opposing Alliance who are not also Disqualified will receive the win for the Match and two (2) Win Points.
   1. The Team’s non-Disqualified Alliance Partner is unaffected, i.e., they will also receive the win for the Match and two (2) Win Points.
2. If the Match was a tie, then each Team on the opposing Alliance (the Alliance that did not receive the Disqualification ) will receive the win for the Match and two (2) Win Points. If both Alliances have a Team receiving a Disqualification, then all non-Disqualified Teams will receive a tie for the Match and one (1) Win Point.
3. Autonomous Win Points are not given to Teams that receive a Disqualification, and are not automatically awarded to the opposing Alliance.

When a Team is Disqualified in an Elimination Match, the entire Alliance is Disqualified ; they receive a loss for the Match, and the opposing Alliance is awarded the win. If both Alliances receive a Disqualification in an Elimination Match, both Alliances receive a loss and will play another Match to determine a winner.

Note: If a Team is Disqualified in a Robot Skills Match, a score of zero (0) will be recorded for that Match.

<GG7> Time-outs. Each Elimination Alliance gets one three-minute Time-out, which they may request during the Elimination Bracket. The Time-out will be served at the time of the Alliance’s next upcoming Match. Alliances must request their Time-out between Elimination Matches ; they may not use their Time-out during a Match, for another Alliance’s Match, or after they have been eliminated. There are no Time-outs during the Qualification Match schedule.

1. A Time-out can be ended early, but only if agreed to by both Alliances and the Head Referee.
2. An Alliance’s Time-out request should never be denied if the Alliance legitimately needs extra time.

<GG8> Keep your Robots together. Robots may not intentionally detach parts during the Match or leave mechanisms on the Field.

Note: Parts which become detached unintentionally are a Minor Violation, are no longer considered “part of a Robot,” and should be ignored for the purpose of any rules which involve Robot contact or location (e.g., scoring) or Robot size.

This rule has additional Violation notes. See Appendix C.

<GG9> Don’t hook your Robot to the Field, and don’t get Entangled. Robots may not intentionally grasp, grapple, hook, attach to or otherwise Entangled with any Field Elements. Strategies with mechanisms that react against multiple sides of a Field Element in an effort to latch or hook onto said Field Element are prohibited. The intent of this rule is to prevent Teams from unintentionally damaging the Field and/or from anchoring to or otherwise Entangling themselves with the Field.

Whenever possible, Head Referees should alert Teams to potential Violations before they happen to prevent actual Violations. If a Robot takes immediate action to avoid or resolve the issue, and if the Head Referee determines that the issue had no effect on the Match, no Violation should be recorded.

<GG10> The red Alliance may choose to place last. The red Alliance has the right to place its Robots on the Field last in Qualification Matches and Elimination Matches. Once a Team has placed its Robot on the Field, in order to avoid schedule delays its position should not be adjusted prior to the Match. <GG3> applies. If a Team chooses to reposition their Robot after it has already been placed, the opposing Alliance will also be given the opportunity to reposition their Robots promptly.

This rule is applied differently for VEX U. See Rule <VUG2>

<GG11> Controllers must stay connected to the Field. Prior to the beginning of each Match, Drive Team Members must plug their V5 Controller into the Field’s control system. This cable must remain plugged in for the duration of the Match, and may not be removed until the “all-clear” has been given for Drive Team Members to retrieve their Robots. See <T8> for more information regarding Field control system options.

This rule has additional Violation notes. See Appendix C.

<GG12> Autonomous means “no humans.” During the Autonomous Period, Drive Team Members are not permitted to interact with the Robots in any way, directly or indirectly. This could include, but is not limited to:

• Activating any controls on their V5 Controllers
• Unplugging or otherwise manually interfering with the Field connection in any way
• Manually triggering sensors (including the Vision Sensor) in any way, even without touching them
  

Note: In extreme cases, with permission from the Head Referee, Teams may Disable their Robot during the Autonomous Period by holding the power button on their V5 Controller. This exception is only intended for egregious safety- or damage-related circumstances; Disabling an autonomous routine for strategic purposes would still be considered a Violation of <GG12>.

This rule has additional Violation notes. See Appendix C.

<GG13> All rules still apply in the Autonomous Period. Teams are responsible for the actions of their Robots at all times, including during the Autonomous Period. Any Violations, Major or Minor, committed during the Autonomous Period will result in the Autonomous Bonus being automatically awarded to the opposing Alliance and make the violating Team’s Alliance ineligible for the Autonomous Win Point.

If both Alliances commit Violations during the Autonomous Period, then no Autonomous Bonus will be awarded.

This rule has additional Violation notes. See Appendix C.

<GG14> Don’t destroy other Robots. But, be prepared to encounter defense. Strategies aimed solely at the destruction, damage, tipping over, or Entanglement of opposing Robots are not part of the ethos of the VEX V5 Robotics Competition and are not allowed.

1. V5RC Override is intended to be an Offensive game. Teams that partake in solely Defensive or destructive strategies will not have the protections implied by this rule (see <GG15> ). However, Defensive play which does not involve destructive or illegal strategies is still within the spirit of this rule.
2. V5RC Override is also intended to be an interactive game. Some incidental tipping, Entanglement, and damage may occur as a part of normal gameplay without Violation. It will be up to the Head Referee’s discretion whether the interaction was incidental or intentional.
3. A Team is responsible for the actions of its Robot at all times, including the Autonomous Period. This applies both to Teams that are driving recklessly or potentially causing damage, and to Teams whose Robots have small and/or unstable wheel bases. A Team should design its Robot such that it is not easily tipped over or damaged by minor contact.
4. <GG14> may be applied differently in the Midfield during the Endgame. See <SG12>.

This rule has additional Violation notes. See Appendix C.

<GG15> Offensive Robots get the “benefit of the doubt” when judgment calls are required. In a case where a Head Referee is forced to make a judgment call regarding a destructive interaction between a Defensive and Offensive Robot, or an interaction which results in a questionable Violation, referees will decide in favor of the Offensive Robot. This also applies during the Autonomous Period (see <SG7a>).

<GG16> You can’t force an opponent into a penalty. Intentional strategies that cause an opponent to break a rule are not permitted, and will not result in a Violation for the opposing Alliance.

This rule has additional Violation notes. See Appendix C.

<GG17> No Holding for more than a 3-count. A Robot may not Hold an opposing Robot for more than a 3-count during the Driver Controlled Period.

For the purposes of this rule, a “count” is defined as an interval of time that is approximately one second in duration, and “counted out” by Head Referees verbally. A Holding count should begin immediately once the Head Referee observes a suspected Holding interaction.

The Holding count should pause when at least one of the following conditions is met:

1. The two Robots are separated by at least two (2) feet (approximately one foam tile).
2. Either Robot has moved at least two (2) feet away (approximately one tile) from the location where the Trapping or Pinning count began.
   1. In the case of Lifting, this location is measured from where the Lifted Robot is released, not from where the Lifting began.
3. The Holding Robot becomes Trapped or Pinned by a different Robot.
   1. In this case, the original count would end, and a new count would begin for the newly Trapped or Pinned Robot.
4. In the case of Trapping, if an avenue of escape becomes available due to changing circumstances in the Match.

After a Holding count ends, a Robot may not resume Holding the same Robot again for a 5-count. If a Team resumes Holding the same Robot within that 5-count, the original Holding count will resume from where it ended. A Head Referee should use fingers to display the 5-count that occurs after the end of a Holding count, and “wave it off” after the Holding interaction has been cleared.

If two Robots are working together to Trap an opponent simultaneously, the Holding count can be applied to both Robots ; it’s possible for them to legally take turns Trapping, but it’s risky.

This rule has additional Violation notes. See Appendix C.

<GG18> Use Scoring Objects to play the game. Scoring Objects may not be used to accomplish actions that would be otherwise illegal if they were attempted by Robot mechanisms. If a rule is Violated through the use of a Scoring Objects instead of a Robot mechanism, it should be evaluated as though the rule in question had been Violated by a Robot mechanism. Examples include, but are not limited to:

• Interfering with an opponent’s Autonomous routine per <SG7>
• Using a Scoring Objects to intentionally tip or Entangle an opponent Robot

The intent of this rule is to prohibit Teams from using Scoring Objects as “gloves” to loophole any rule that states “a Robot may not [do some action].” This rule is not intended to be taken in its most extreme literal interpretation, where any interaction between a Scoring Object and a Robot needs to be scrutinized with the same intensity as if it were a Robot.

Section 3 - Robot Skills

Overview

In Robot Skills Matches, Teams have one minute to score as many points as possible. There are two types of Robot Skills Matches : Driving Skills Matches, which are entirely Driver controlled, and Autonomous Coding Skills Matches, which are autonomous with limited human interaction. Teams are ranked based on their combined score in the two types of Robot Skills Matches.

Robot Skills Matches are optional for all Teams. Teams who do not compete in Robot Skills Matches will not be penalized in Teamwork Matches. However, participation in Robot Skills Matches may impact eligibility for judged awards at the event.

At events that include Teamwork Matches, Teams may only participate in Robot Skills Matches if they also participate in the Qualification Matches. See rule <T20>.

Robot Skills Challenge Rules

<RSC1> Standard rules apply in most cases. All rules from previous sections apply to Robot Skills Matches, unless otherwise specified in this section.

1. Removing Scoring Objects from the Field in a Robot Skills Match is not a Violation. Scoring Objects that leave the Field cannot be returned.
2. In the Robot Skills Challenge, the standard definition of Match Affecting does not apply, because there is no winner or loser. When evaluating whether a rule Violation should be classified as a Major Violation or Minor Violation in the context of this criteria, the term “score affecting” can be substituted for “Match Affecting.” A Violation is considered “score affecting” if it results in a net increase of that Team’s score at the end of the Match.
3. Violations of <GG>, <SG>, and <RSC> rules that occur during a Robot Skills Match should only affect the outcome of that Match and should not be considered when determining whether a Violation has been repeated during the event.

<RSC2> Match play is different in Robot Skills Matches.

1. The Robot must start the Robot Skills Match in a legal starting position in the Quadrant adjacent to the red Alliance Station.
2. All Drive Team Members must remain in the red Alliance Station for the duration of the Match.
3. One red/yellow Pin must be used as a Preload in accordance with <SG5>.
4. Teams may only introduce Match Load Scoring Objects through red Alliance Loaders.
5. Robots can add or remove Pins or Cups on all Goals.
6. Robots may move freely about the Field after the start of the Match.

This rule is applied differently for VEX U. See Rule <VURS3>.

<RSC3> Scoring Robot Skills Matches. For each Robot Skills Match, Teams are awarded a score based on the following rules and scoring table:

1. Teams can earn points for Pins of any color.
   1. Red Pins can only be Scored if they are Placed in a red Quadrant or in the Midfield.
   2. Blue Pins can only be Scored if they are Placed in a blue Quadrant or in the Midfield.
   3. Yellow Pins can only be Scored if they are Owned.
      1. Toggles only confer Ownership of Pins when the Toggle matches the color of its Quadrant (i.e., yellow Pins Placed in a red Quadrant with a Toggle that is set to blue are not Owned and will not earn any points).
      2. Yellow Pins Placed in the Midfield are Owned if a Robot ends the Match in the Midfield. (See <SC6>.)
   4. A Pin in contact with a Robot at the end of the Match does not score points.
2. The Team will earn points for a Robot in the Midfield if the Robot meets the conditions of rule <SC6> at the end of the Match.

<RSC4> Field setup for Skills Matches. The Field is set up differently than a Head-to-Head Match, with the following modifications:

1. In Autonomous Coding Skills Matches, the VEX GPS code strip must be installed on the Field.
2. Revised Match Loads. Three (3) red/yellow Pins, four (4) blue/yellow Pins, and seven (7) Cups begin off the Field as Match Loads.
3. All Goals start the Match empty with no Placed Pins.

This rule is applied differently for VEX U. See Rule <VURS1>.

<RSC5> Skills Stop Time. If a Team wishes to end their Robot Skills Match early, they may elect to record a Skills Stop Time. This is used as a tiebreaker for Robot Skills Challenge rankings. A Skills Stop Time does not affect a Team’s score for a given Robot Skills Match. Drive Team Members and field staff must agree prior to the Match on the signal that will be used to end the Match early.

1. Teams who intend to attempt a Skills Stop Time must “opt-in” by verbally confirming with the Scorekeeper Referee prior to the Robot Skills Match. If no notification is given prior to the start of the Match, then the Team forfeits their option to record a Skills Stop Time for that Match and they will receive a default Skills Stop Time of 0.
   1. This conversation should include informing the Scorekeeper Referee which Drive Team Member will signal the stop. The Match may only be ended early by a Drive Team Member for that Match.
   2. If a Team runs multiple Robot Skills Matches in a row, they must reconfirm their Skills Stop Time choice with the Scorekeeper Referee prior to each Match.
   3. Any questions regarding a Skills Stop Time should be reviewed and settled immediately following the Match. <T1> and <T3> apply to Robot Skills Matches.
2. If the event is utilizing a V5 Robot Brain or the TM Mobile app for Robot Skills Challenge field control, a Drive Team Member may elect to start and stop their own Robot Skills Matches.
   1. This V5 Robot Brain or other device running the TM Mobile app will be used to start the Robot Skills Matches (i.e., “enable” the Robot ), end the Robot Skills Match (i.e., “Disable ” the Robot ), and display the official Skills Stop Time to be recorded.
   2. This V5 Robot Brain must be running the official field control user program.
   3. For more information regarding the use of a V5 Robot Brain for Robot Skills Challenge field control, and to download the official field control user program, visit this VEX Knowledge Base article.
   4. For more information regarding the use of TM Mobile for field control, see the Tournament Manager documentation.
3. At events which do not have a V5 Robot Brain or the TM Mobile App available for Robot Skills Challenge field control, Drive Team Members and field staff must agree prior to the Match on the signal that will be used to end the Match early. A manual timer must be used in conjunction with a VEXnet Competition Switch.
   1. The moment when the Match ends early is defined as the moment when the Robot is “Disabled ” by the field control system. The time shown on the timer should be rounded up to the nearest second. For example, if the Robot is Disabled and the timer shows 25.2 seconds, then the Skills Stop Time should be recorded as 26.
   2. The agreed-upon signal must be both verbal and visual, such as Drive Team Members crossing their arms in an “X” or placing their V5 Controller(s) on the ground.
   3. The signal must be given by a Drive Team Member who is standing in the Alliance Station.
   4. It is recommended that Drive Team Members also provide verbal notice that they are approaching their Skills Stop Time, such as by counting out “3-2-1-stop.”
4. It is at the Event Partner’s discretion which method will be used to record Skills Stop Times at a given event. The chosen method must be communicated prior to the start of Matches (such as during an event meeting), and made equally available to all Teams.
   1. If an event intends to use a manual timekeeping method, a Team cannot bring their own V5 Robot Brain just for use during their own Robot Skills Match.
   2. If an event intends to utilize a V5 Robot Brain, all Teams must use the same V5 Robot Brain for all Robot Skills Matches on a given Field.
   3. If an event is using multiple Fields for Robot Skills Matches, the same method must be used at all Fields, as described in rule <T21>. Multiple V5 Robot Brains may be used as needed (e.g., a “Field 1 Brain” and a “Field 2 Brain”).
   4. The default timed “Drive” program accessed from a V5 Controller is intended for practice only, and cannot be used for an official Robot Skills Match.
5. If a Team chooses to utilize/record a Skills Stop Time, the 5-second grace period described in rule <SC1> does not apply.

Section 4 - The Robot

Overview

All Robots must pass inspection before competing in the VEX V5 Robotics Competition to ensure compliance with all Robot rules. Inspections typically occur during Team check-in or practice time. Teams should use the rules below to pre-inspect their Robot and confirm it meets all requirements.

Most rules are hard limits (e.g., motor quantity), while others are subject to inspector discretion (e.g., safety concerns). At many events, the lead inspector and Head Referee are the same person; if not, inspectors should consult the Head Referee for judgment calls. Per <R2d> and <R2e>, the Head Referee has final authority on all Robot rules and whether a Robot may compete.

Inspection Rules

<R1> One Robot per Team. Each Team can only bring one Robot to a given event in the VEX V5 Robotics Competition. Though it is expected that Teams will make changes to their Robot at the competition, a Team is limited to only one Robot at a given event, and a given Robot may only be used by one Team. A VEX Robot, for the purposes of the VEX V5 Robotics Competition, has the following subsystems:

• Subsystem 1: Mobile robotic base including wheels, tracks, legs, or any other mechanism that allows the Robot to navigate the majority of the flat playing Field surface. For a stationary Robot, the robotic base without wheels would be considered Subsystem 1.
• Subsystem 2: Power and control system that includes a legal VEX battery, a legal VEX control system, and associated motors for the mobile robotic base.
• Subsystem 3: Additional mechanisms (and associated motors) that allow manipulation of Scoring Objects and interactions with Field Elements and other Robots.

Given the above definitions, a minimum Robot for use in any VEX V5 Robotics Competition event (including Robot Skills Matches ) must consist of subsystems 1 and 2 above. Thus, if you swap out an entire subsystem 1 or 2, you have created a second Robot and are in Violation this rule.

1. Teams may not compete with one Robot while a second is being modified or assembled at a competition.
2. Teams may not have an assembled second Robot on hand at a competition that is used to repair or swap parts with the first Robot.
3. Teams may not switch back and forth between multiple Robots during a competition. This includes using different Robots for Robot Skills Matches, Qualification Matches, and/or Elimination Matches.
4. Multiple Teams may not use the same Robot. Once a Robot has competed under a given Team number at an event, it is “their” Robot ; no other Team may EVER compete with it.

This rule is applied differently for VEX U. See Rule <VUR1>.

<R2> Robots must pass inspection. Every Robot will be required to pass a full inspection before being cleared to compete. This inspection will ensure that all Robot rules and regulations are met. Noncompliance with any Robot design or construction rule will result in removal from Matches or Disqualification of the Robot at an event until the Robot is brought back into compliance, as described in the following subclauses.

1. Significant changes to a Robot, such as a partial or full swap of Subsystem 3, must be re-inspected before the Robot may compete again.
2. All possible functional Robot configurations must be inspected before being used in competition. This especially pertains to modular or swappable mechanisms (per <R1> ) and Match starting configurations/sizes (per <R3> ).
3. Teams may be requested to submit to spot inspections by Head Referees. Refusal to submit will result in Disqualification.
   1. If a Robot is determined to be in Violation of a Robot rule before a Match begins, the Robot will be removed from the Field. The Robot may remain at the Field so that the Team does not get assessed a “no-show” (per <GG2> ).
4. Robots which have not passed inspection (i.e., that are in Violation of one or more Robot rules) will not be permitted to play in any Matches until they have passed inspection. <GG2> will apply to any Matches that occur until the Robot has passed inspection.
5. If a Robot has passed inspection, but is later confirmed to be in Violation of a Robot rule during or immediately following a Match by a Head Referee, they will be Disqualified from that Match. This is the only Match that will be affected; any prior Matches that have already been completed will not be revisited. <R3d> will apply until the Violation is remedied and the Team is re-inspected.
6. All inspection rules are to be enforced within the discretion of the Head Referee within a given event. Robot legality at one event does not automatically imply legality at future events. Robots which rely on “edge-case” interpretations of subjective rules, such as whether a decoration is “non-functional” or not, should expect additional scrutiny during inspection.
7. Events may wish to use “inspection markers” (e.g., zip tie or sticker) to identify Robots that have passed inspection at that event. Inspection markers are functional components and are subject to all Robot rules, including legal materials and Robot size/expansion limits.

Event staff and volunteers are allowed to contact and/or photograph Robots during inspection and/or at other times as needed.

<R3> Robots must fit within an 18” x 18” x 18” volume.

1. Compliance with this rule may be checked using the official VEX Robotics On-Field Robot Expansion Sizing Tool.
2. Event Partners may construct and/or provide any sizing tool that measures the correct dimensions.
3. Any restraints used to maintain starting size (i.e., zip ties, rubber bands, etc.) must remain attached to the Robot for the duration of the Match, per <GG8>.
4. For the purposes of this rule, it can be assumed that Robots will be inspected and begin each Match on a flat standard foam field tile.

This rule is applied differently for VEX U. See Rule <VUR1>.

<R4> Officially registered Team numbers must be displayed on Robot license plates. To participate in an official VEX V5 Robotics Competition event, a Team must first register on events.vex.com and receive a V5RC Team number. This Team number must be displayed on the Robot using license plates. Teams may choose to use the official V5RC License Plate Kit, or may create their own using legal materials.

1. License plates must be placed in fixed locations on exactly two (2) horizontally opposing sides of the Robot and must remain visible, legible, and attached for the entirety of the Match. The top of a Robot is not considered a “side” for these two license plates.
   1. License plates should be mounted in locations that remain stationary on the Robot during a Match (e.g., not on a rotating intake or flipping manipulator). The function of license plates is to identify Robots for referees, spectators, and other Teams. Identification is harder when a license plate on a Robot moves during a Match.
2. License plates must be securely attached to the Robot using materials that are legal for Robot construction. VEX IQ pins are not legal for mounting license plates on Robots.
3. Robots may only include license plates that match their Alliance color for the current Match (i.e., red Alliance Robots must have only red plates installed for the Match ).
4. License plates are considered functional components, and must meet the requirements of all Robot rules.
5. Additional license plates cannot be used on the Robot for any purpose.
6. Team numbers must be in white font, and clearly legible. Number/letter stickers are legal for use on license plates instead of or in addition to those in the V5RC License Plate Kit.
7. Custom license plates used to meet the requirements of <R4a> and <R4f> must be within the following size limits:
   1. Height: between 2.0 (50.8mm) and 2.5 inches (63.5mm)
   2. Width: between 4.0 (101.6mm) and 4.5 inches (114.3mm)
   3. Thickness: up to 0.25” (6.35mm)

<R5> Let go of Scoring Objects after the Match. Robots must be designed to permit easy removal of Scoring Objects from any mechanism without requiring the Robot to have power after a Match.

<R6> Robots have one Brain. Robots must ONLY use one (1) VEX V5 Robot Brain (276-4810). Any other microcontrollers or processing devices are not allowed, even as non-functional decorations.

1. This includes microcontrollers that are part of other VEX product lines, such as VEX Cortex, VEX EXP, VEXpro, VEX CTE, VEX RCR, VEX IQ, VEX GO, VEX AIR, or VEX Robotics by HEXBUG. This also includes devices that are unrelated to VEX, such as Raspberry Pi or Arduino devices.
2. V5 Robot Brain accessories (short flanges, long flanges, and the magnetic screen protector) are part of the V5 Robot Brain and are only legal for use on Robots as part of the V5 Robot Brain.
3. At events using a V5 Smart Field Control System, the “Team Number” field in the Robot Brain must be set as the Team’s registered number and letter (with no spaces).

This rule is applied differently for VEX U. See Rules <VUR10> and <VUR12>.

<R7> Keep the power button or battery connection accessible. The on/off button on the V5 Robot Brain and/or the Battery Cable connection on either the V5 Robot Brain or V5 Robot Battery must be accessible without moving or lifting the Robot. The V5 Brain screen should be easily visible during Robot inspection. Keeping the V5 Brain screen visible throughout a Match is recommended but not required.

<R8> Firmware. Teams must use VEXos version 1.1.5 or newer, found at https://link.vex.com/firmware. Custom firmware modifications are not permitted.

1. The minimum version requirement is subject to change over the course of the season.
2. When the minimum version is updated, Teams have a one week (7 calendar day) grace period from the time the minimum version is changed to update their firmware to the latest minimum version.
3. VEX reserves the right to deem any firmware update critical, and remove the allowable grace period.
4. Beta firmware, which includes any firmware version that ends with the letter ‘b’, is not legal for use in competition.

<R9> Use a “Competition Template” for programming. The Robot must be programmed to follow control directions provided by the VEXnet Field Controllers or Smart Field Control system.

During the Autonomous Period, Drive Team Members will not be allowed to use their V5 Controllers. As such, Teams are responsible for programming their Robot with custom software if they want to perform in the Autonomous Period.

This may be tested in inspection, where Robots may be required to pass a functional “enable/disable” test. For more information on this, Teams should consult the help guides produced by the developers of their chosen programming software.

<R10> Motors are limited for Subsystem 2 (see <R1>). Robots may use any combination of V5 Smart Motors, 11W (276-4840) and/or 5.5W (276-4842), within the following criteria:

1. The combined power of all motors (11W & 5.5W) must not exceed 88W. This limit applies to all motors on the Robot, even those which are not plugged in.
2. V5 Smart Motors connected to Smart Ports are the only motors that may be used with a V5 Robot Brain. The 3-wire ports may not be used to control motors of any kind.

This rule is applied differently for VEX U. See Rule <VUR11>.

<R11> Motors are limited for Subsystem 2 (see <R1>) Robots may use any combination of V5 Smart Motors, 11W (276-4840) and/or 5.5W (276-4842), in Subsystem 2 within the following criteria:

1. The combined power of all motors in Subsystem 2 must not exceed 55W.
2. Motors used in Subsystem 2 cannot provide power to any mechanism that is not a part of Subsystem 1.
   1. Motors in Subsystem 2 cannot be toggled, engaged, or configured such that they are capable of providing power to any part of the Robot that is not a part of Subsystem 1
3. Teams may be required to demonstrate what each motor is capable of powering on their Robot during inspection in order to satisfy this requirement.

This rule does not apply to VEX U. See <VUR11>

<R12> Electrical power comes from VEX batteries only. Robots may use one (1) V5 Robot Battery (276-4811) to power the V5 Robot Brain.

1. No other sources of electrical power are permitted, unless used as part of a non-functional decoration per <R23e>.
2. There are no legal power expanders for the V5 Robot Battery.
3. V5 Robot Batteries may only be charged by a V5 Robot Battery Charger (276-4812 or 276-4841).
4. V5 Controllers (276-4820) may only be powered by their internal rechargeable battery.
   1. Teams are permitted to have an external power source (such as a rechargeable battery pack) plugged into their V5 Controller during a Match, provided that this power source is connected safely and does not violate any other rules, such as <R28>.
   2. Some events may choose to provide Field power for V5 Controllers. If this is provided for all Teams at the event, then this is a legal power source for the V5 Controllers.

This rule is applied differently for VEX U. See Rule <VUR12>.

<R13> Robots use VEXnet. Robots must ONLY utilize VEXnet for all wireless Robot communication.

1. Electronics from the Cortex, VEX EXP, VEX CTE. VEXpro, VEX RCR, VEXplorer, VEX IQ, VEX GO, or VEX Robotics by HEXBUG product line are prohibited unless otherwise noted in <R16>.
2. Teams are permitted to use the Bluetooth® capabilities of the V5 Robot Brain and/or V5 Controller in Team pits, practice Fields, and Robot Skills Matches. However, VEXnet must be used for wireless communication during Head-to-Head Matches.
3. Teams are permitted to use the Wi-Fi capabilities of the Vision Sensor in Team pits or outside of Matches. However, the Vision Sensor must have its wireless transmitting functionality disabled during Matches.

This rule is applied differently for VEX U. See Rules <VUR2>, <VUR10> and <VUR12>.

<R14> Give the radio some space. The V5 Radio should be mounted such that no metal surrounds the radio symbol on the V5 Radio. While failure to do so will affect Robot performance, it will not prevent the Robot from passing inspection.

It is fine to loosely encapsulate the V5 Radio within Robot structure. The intent of this rule is to minimize radio connection issues by minimizing obstructions between VEXnet devices. Burying a radio deep within a Robot may result in Robot communication issues. It is also recommended that the LEDs on the radio be visible to aid in troubleshooting.

<R15> One or two Controllers per Robot. No more than two (2) VEX V5 Controllers may control a single Robot.

1. No physical or electrical modification of these Controllers is allowed under any circumstances.
   1. Attachments which assist the Drive Team Member in holding or manipulating buttons/joysticks on the V5 Controller are permitted, provided that they do not involve direct physical or electrical modification of the Controller itself.
2. No other methods of controlling the Robot (light, sound, etc.) are permissible.
   1. Using sensor feedback to augment driver control (such as motor encoders or the Vision Sensor) is permitted.

<R16> Robots are built from the VEX V5 system. Robots may be built ONLY using official VEX

V5 components, unless otherwise specifically noted within these rules.

1. All legal parts for the V5 system are listed in the V5 Competition Legal Parts List.
2. Any questions or concerns about legal parts should be directed to the official Q&A System on events.vex.com.

This rule is applied differently for VEX U. See Rule <VUR2>.

<R17> New VEX parts are legal. Additional VEX components released during the competition season on www.vexrobotics.com are considered legal for use unless otherwise noted.

Some “new” components may have certain restrictions placed on them upon their release. These restrictions will be documented in the official Q&A, in a Game Manual update, or in the VEX V5 Legal Parts List.

<R18> Prohibited Items. The following types of mechanisms and components are NOT allowed.

1. Those that could potentially damage Field Elements or Scoring Objects.
2. Those that could potentially damage other competing Robots.
3. Those that pose an unnecessary risk of Entanglement with other Robots or Field Elements.
4. Those that could pose a potential safety hazard to Drive Team Members, event staff, or other humans.
5. Products from the VEXpro, VEX EXP, VEX IQ, VEX GO, VEX 123, VEX CTE, VEX AIM, VEX AIR, VEX Robotics by HEXBUG*, or any other VEX product lines, unless specifically allowed by a clause of <R16> or listed in the VEX V5 Legal Parts List (See <R16> ).
6. Components obtained from the V5 beta program. All V5 beta hardware can be identified by its lighter gray pre-production color. Robot Brains, Robot Batteries, Controllers, and Vision Sensors from the V5 beta have a “BETA TEST” stamp on them. Smart Motors and Radios do not have this stamp, but can still be identified by color.
7. Standalone VEX Smart Field Controller Brains (SKU 276-7577).
8. VEX apparel, competition support materials, packaging, or other non-Robot products.
9. Field Elements or components of Field Elements that are not otherwise explicitly legal materials (e.g., screws, standoffs, nuts, or non-shattering plastic within the limitations of <R24> ).
10. 3D printed Robot parts for any purpose, including non-functional decorations and license plates.
11. Speakers and other audio devices that create sound.

3D printed Controller attachments, 3D printed Robot alignment tools, and/or other custom 3D printed tools that do not go onto the Robot or into the Field during a Match are not considered Robot parts, and may be legal for use if they meet the requirements of other pertinent rules.

This rule is applied differently for VEX U. See Rules <VUR2>, <VUR5>, <VUR6>, & <VUR13>.

<R19> Certain non-VEX components are allowed. Robots are allowed the following additional components from sources other than VEX Robotics:

1. Any non-aerosol-based grease or lubricating compound, when used in extreme moderation on surfaces and locations that do NOT contact the playing Field walls, foam Field tiles, Scoring Objects, or other Robots. Grease or lubricant applied directly to V5 Smart Motors or Smart Motor cartridges is prohibited.
2. Anti-static compound, when used in extreme moderation (i.e., such that it does not leave residue on Field Elements, Scoring Objects, or other Robots ).
3. Hot glue when used to secure cable connections.
4. An unlimited amount of non-elastic rope/string, no thicker than 1/4” (6.35mm).
5. Commercially available items used solely for bundling or wrapping of 2-wire, 3-wire, 4-wire, or V5 Smart Cables, and/or pneumatic tubing are allowed. These items must solely be used for the purposes of cable/tubing protection, organization, or management. This includes but is not limited to electrical tape, cable carrier, cable track, etc. It is up to inspectors to determine whether a component is serving a function beyond protecting and managing cables and tubing.
6. Rubber bands no larger than 7.5” long and 0.25” wide.
7. Anti-slip drawer liner with similar nominal dimensions to VEX Anti-Slip Mat (275-0120 or 275-0121). The pattern of the matting should be similar to VEX Anti-Slip Mat, and there should be no additional performance gained by using non-VEX anti-slip drawer liner (i.e., no additional elasticity, adhesive backing, etc.). No piece of anti-slip drawer liner can be larger than 12” x 15” and all anti-slip drawer liner must be black in color.
8. Plastic zip ties no larger than 12” long and 0.25” wide.
9. A Micro SD card installed in the V5 Robot Brain.
10. Aerosol-based cooling/freeze spray may be used to assist in cooling motors. Teams using freeze spray or similar products in ways that may reasonably be deemed unsafe could be subject to <S1> Violations.
11. Cleaners, disinfectants, and/or sanitizers may be used to assist in cleaning Robots, parts, components, etc.
12. See rules <R21> through <R25> for additional legal non-VEX components.

This rule is applied differently for VEX U. See Rules <VUR3>, <VUR4>, <VUR7>, <VUR8>, <VUR9>, <VUR12>, <VUR14>& <VUR15>.

<R20> Custom V5 Smart Cables are allowed. Teams who create custom cables acknowledge that incorrect wiring may have undesired results.

1. Official V5 Smart Cable Stock must be used.
2. Use of non-VEX 4P4C connectors and 4P4C crimping tools is permissible.
3. V5 Smart Cables may only be used for connecting legal electronic devices to the V5 Robot Brain.

<R21> A limited amount of tape is allowed. Robots may use a small amount of tape for the following purposes:

1. To secure any connection between the ends of two (2) VEX cables.
2. To label wires, motors, Robot Brains, and/or controllers.
3. To prevent leaks on the threaded portions of pneumatic fittings. This is the only acceptable use of Teflon tape.
4. In any other application that would be considered a “decoration” per <R23>.
5. As an aglet at the end of rope/string to prevent fraying.

<R22> Certain non-VEX fasteners are allowed. Robots may use the following commercially available hardware:

1. #4, #6, #8, M3, M3.5, or M4 screws up to 2.5” (63.5 mm) long, and M2.5 x 8mm screws.
2. Shoulder screws with a shoulder length no longer than 0.20” and a diameter no larger than 0.176”.
3. Any commercially available nut, washer, threaded standoff up to 6” (152.4mm) long, and/or non-threaded spacer up to 2.5” (63.5mm) long which fits these screws.

This rule is applied differently for VEX U. See Rule <VUR9>.

<R23> Visual decorations are allowed. Teams may add non-functional decorations, provided that they do not affect Robot performance in any significant way or affect the outcome of the Match. These decorations must be in the spirit of the competition. Inspectors and Head Referees will have final say in what is considered “non-functional.” Unless otherwise specified below, non-functional decorations are governed by all standard Robot rules.

To be considered “non-functional,” decorations must be backed by legal materials that provide the same functionality. For example, if a Robot has a giant decal that prevents Scoring Objects from falling out of the Robot, the decal must be backed by VEX material that would also prevent the Scoring Objects from falling out. A simple way to check this is to determine if removing the decoration would impact the performance of the Robot in any way.

1. Anodizing, painting, dyeing, or otherwise changing the color of any legal VEX part is considered a legal nonfunctional decoration.

   Note: For official events held in mainland China, anodizing, painting, dyeing, or otherwise changing the color of any legal VEX part is prohibited.

2. Small cameras are permitted as non-functional decorations, provided that any transmitting functions or wireless communications are disabled. Unusually large cameras used as ballast are not permitted.
3. VEX electronics may not be used as non-functional decorations.
4. Decorations that visually mimic Field Elements or Scoring Objects are not permitted. The inspector and Head Referee will make the final decision on whether a given decoration or mechanism violates this rule.
   1. Decorations cannot be designed to intentionally interfere with opponent Vision or Color Sensors. Teams will be asked to remove these decorations if the inspector or Head Referee determines that it interferes with opponent systems.
5. Decorations which provide feedback to a Robot (e.g., by influencing legal sensors) would be considered “functional,” and are not permitted.
6. Decorations that cover or obscure identifying features of electronics and/or pneumatics parts are not legal.
   1. Teams will be asked to either replace the electronics and/or pneumatics part entirely, or remove the decoration if possible.
   2. Identifying features include, but are not limited to, VEX logos, part numbers, and other distinctive colors or features of the part that allow an inspector to easily confirm it is a legal part.

<R24> A limited amount of custom plastic is allowed. Robots may use custom-made pieces cut from certain types of non-shattering plastic, up to 0.070” (1.78mm) thick.

1. Each Robot is limited to a maximum of 12 individual pieces cut from non-shattering plastic. This includes non-shattering plastic used in non-functional decorations.
2. Each individual piece of non-shattering plastic cannot be larger than 4” x 8” x 0.070”.
3. Teams must present and display ALL non-shattering plastic parts during inspection.
   1. Inspectors will verify the total number of plastic pieces. They may use dry-erase markers or other forms of temporary marking to aid in counting.
   2. Inspectors will verify that no non-shattering piece exceeds the size limitation.
4. Plastic may be mechanically altered by cutting, drilling, bending, etc. It cannot be chemically treated, melted, cast, or bonded to another part. Heating non-shattering plastic to aid in bending is acceptable.
5. Legal plastic types are polycarbonate (Lexan), acetal monopolymer (Delrin), acetal copolymer (Acetron GP), POM (acetal), ABS, PEEK, PET, HDPE, LDPE, nylon (all grades), polypropylene, PTFE, and FEP.
6. Shattering plastic, such as PMMA (also called plexiglass, acrylic, or perspex), is prohibited.
7. Plastic sheets sold by VEX (such as the 276-8340 PET Sheets) are considered custom plastic in the context of this rule, and are subject to the same limitations as other plastic parts.
8. This rule does not apply to 3D printed plastic parts. 3D printed Robot parts are not permitted in the VEX V5 Robotics Competition for any purpose, including non-functional decorations.

Note: Teams are strongly encouraged to provide inspectors with 1:1 scale drawings, identical spares, or 1:1 scale tracings of their non-shattering plastic pieces to aid in inspection. Drawings and tracings should accurately reflect ALL shapes and dimensions of each piece. Complex bent/cut parts, and parts that are cut diagonally across a 4”x8” sheet to gain length may require more evidence.

This rule is applied differently for VEX U. See Rules <VUR3> & <VUR4>.

This rule has additional Violation notes. See Appendix C.

<R25> Pneumatics are limited. A Robot’s pneumatic subsystem must satisfy all of the following criteria:

1. Teams may use a maximum of two (2) VEX Air Tanks (276-8749) on a Robot.
2. Pneumatic devices may be charged to a maximum of 100 psi.
3. The compressed air contained inside a pneumatic subsystem can only be used to actuate legal pneumatic devices (e.g., cylinders).

This rule is applied differently for VEX U. See Rule <VUR14>.

<R26> The VEX Pressure Gauge (276-8748) is a required part if a Robot includes pneumatics.

1. The gauge must be plumbed to the high pressure side of the system if the Team is using a regulator.
2. The pressure gauge must be visible and readable by referees and inspectors without moving or removing other Robot components or mechanisms.
3. The pressure gauge will be used to verify that the pneumatics system is charged to no more than 100psi, per <R25>.
   1. The VEX Pressure Gauge on the Robot will take precedence over any off-board measurement.

<R27> Most modifications to non-electrical components are allowed. Physical modifications, such as bending or cutting, of legal metal structure or plastic components are permitted.

1. Modifying the arm of limit switches (by bending or trimming) or removing the rubber cap of bumper switches is permitted.
2. Metallurgical modifications that change fundamental material properties, such as heat treating or melting, are not permitted.
3. Pneumatic tubing may be cut to desired lengths.
4. Fusing/melting the end of legal nylon rope/string (see <R19d>) to prevent fraying is permitted.
5. Welding, soldering, brazing, gluing, or attaching parts to each other in any way that is not provided within the VEX platform is not permitted. Rule <R19c> is an exception to this rule.
6. Mechanical fasteners may be secured using Loctite or a similar thread-locking product. This may ONLY be used for securing hardware, such as screws and nuts.

This rule is applied differently for VEX U. See Rules <VUR3>, <VUR12>& <VUR13>.

<R28> No modifications to electronic or pneumatic components are allowed. Motors (including the V5 Smart Motor firmware), microcontrollers (including V5 Robot Brain firmware), cables, sensors, controllers, battery packs, reservoirs, solenoids, pneumatic cylinders, and any other electrical or pneumatics component of the VEX platform may NOT be altered from their original state in ANY way.

1. Teams may make the following modifications to the V5 Smart Motor (11W)’s user-serviceable features. This list is all-inclusive; no other modifications are permitted. Where applicable, the components listed below (in the specific applications listed below) are permissible exceptions to <R19>.
   1. Replacing the gear cartridge with other official cartridges.
   2. Removing or replacing the screws from the V5 Smart Motor Cap (276-6780).
   3. Removing or replacing the threaded mounting inserts (276-6781).
   4. Aesthetic/non-functional labeling (e.g., markers, stickers, paint, etc.).
2. V5 Smart Motors (11W) must use an official VEX V5 gear cartridge. For the purposes of this rule, the gear cartridges found within the V5 Smart Motor are considered “part of the motor.” Therefore, any physical or functional modifications to official gear cartridges is not permitted. V5 Smart Motors (11W) may only use official VEX motor cartridges
3. For the purposes of this rule, the V5 Smart Motor Cap is not considered “part of the motor.” Therefore, <R27> applies.
4. External wires on VEX 2-wire or 3-wire electrical components may be repaired by soldering or using twist/crimp connectors, electrical tape, or shrink tubing such that the original functionality and length are not modified in any way.
   1. Wire used in repairs must be identical to VEX wire.
   2. Teams make these repairs at their own risk; incorrect wiring may have undesired results.
5. V5 Robot Brain accessories (short flanges, long flanges, and the magnetic screen protector) are considered “part of the V5 Robot Brain” and cannot be modified.

Section 5 - The Tournament

Overview

The VEX V5 Robotics Competition consists of Head-to-Head Matches, Robot Skills Matches, and optional judging. This section describes how Head-to-Head Matches and Robot Skills Matches are to be played at a given event.

Awards may be given to top Teams in each format, as applicable. Awards may also be given for overall performance in the judged criteria.

Tournament Rules

<T1> Head Referees have ultimate and final authority on all gameplay and Robot ruling decisions during the competition.

1. Scorekeeper Referees score the Match, and may serve as observers or advisers for Head Referees, but may not determine any Violations directly.
2. When issuing a Major Violation or Minor Violation to a Team, Head Referees must provide the rule number of the specific rule that has been Violated, and must record the Violation on the Match Anomaly Log.
3. Event Partners may not overrule a Head Referee’s gameplay or Robot decisions.
4. Every Qualification Match and Elimination Match must be watched by a certified Head Referee. A Head Referee may only watch one Match at a time; if multiple Matches are happening simultaneously on separate Fields, each Field must have its own Head Referee. Head Referees must follow the rules in this game manual and the Q&A, and must make rulings consistent with the intent of the game manual and Q&A.
5. At a minimum, every Robot Skills Match must be watched by a trained Scorekeeper Referee, who may only watch one Match at a time. If multiple Robot Skills Matches are happening simultaneously on separate Fields, each Field must have its own Scorekeeper Referee. A certified Head Referee must be available at the event to explain a rule, Disqualification, Violation, or other penalty to Teams in Robot Skills Matches as needed in support of the Scorekeeper Referees at skills Fields.

<T2> Head Referees must be qualified. V5RC Head Referees must have all of the following qualifications:

1. Be at least 20 years of age.
2. Be approved by the Event Partner.
3. Be a certified V5RC Head Referee for the current season.
4. Cannot be the Event Partner or a Judge Advisor for the event.
   

Note: Scorekeeper Referees must be at least 15 years of age, and must be approved by the Event Partner.

<T3> Drive Team Members are permitted to immediately appeal a Head Referee’s ruling. If Drive Team Members wish to dispute a score or ruling, they must stay in the Alliance Station until the Head Referee from the Match talks with them. The Head Referee may then choose to meet with the Drive Team Members at another location and/or at a later time so that the Head Referee has time to reference materials or resources to help with the decision. Once the Head Referee announces that their decision has been made final, the issue is over and no more appeals may be made (See rule <T1> ); failure to accept this final decision may be considered a <G1> Violation. There is no system or opportunity for an appeal of the Head Referee’s final decision, either at or after the event.

1. Referees are not permitted to review any photo or video Match recordings when determining a score or ruling. Some events may also prohibit Drive Team Members from reviewing photo or video Match recordings while in the Alliance Station ; this should be announced to all Teams before Matches start.
2. Head Referees are the only individuals permitted to explain a rule, Disqualification, Violation, or other penalty to the Teams in a Head-to-Head Match. Teams should never consult other field personnel, including Scorekeeper Referees, regarding a ruling clarification.

Communication and conflict resolution skills are an important life skill for Students to practice and learn. In the VEX V5 Robotics Competition, we expect Students to practice proper conflict resolution using the proper chain of command. Violations of this rule may be considered a Violation of <G1>.

<T4> The Event Partner has ultimate authority regarding all non-gameplay decisions during an event. The Game Manual is intended to provide a set of rules for successfully playing V5RC Override; it is not intended to be an exhaustive compilation of guidelines for running a VEX V5 Robotics Competition event. Rules such as, but not limited to, the following examples are at the discretion of the Event Partner and should be treated with the same respect as the Game Manual.

• Venue access
• Pit spaces
• Health and safety
• Team registration and/or competition eligibility
• Team conduct away from competition Fields

This rule exists alongside <G1>, <S1>, and <G3>. Even though there isn’t a rule that says “do not steal from the concession stand,” it would still be within an Event Partner’s authority to remove a thief from the competition.

<T5> Be prepared for minor Field variance. Field Element tolerances and Scoring Objects may vary from specified locations/dimensions; Teams are encouraged to design their Robots accordingly. Please make sure to check Appendix A for more specific nominal dimensions and tolerances.

1. Field Element tolerances may vary from nominal by up to ±1.0”.
2. Scoring Object placement at the beginning of the Match may vary from nominal by up to ±1” (25.4mm). If a Scoring Object is within tolerance, it should not be adjusted before the Match.
3. The rotation of Scoring Objects is not specified. If a Scoring Object is within tolerance, either on the Field or within a Loader, it should not be adjusted before the Match.

The Field Perimeter and Field Elements are designed to be assembled and disassembled multiple times each year. Event Partners store and transport Fields between events, and the individuals setting up the Field at one event may differ from those at the next. While every effort will be made to ensure minimal variance, Teams should expect that any Field may be slightly different than another, and prepare accordingly. Just because something works on one Field does not fully guarantee it will work on the next, and is not enough evidence alone to determine if a Field is out of tolerance.

<T6> Fields may be repaired at the Event Partner’s discretion. All competition Fields at an event must be set up in accordance with the specifications in Appendix A and/or other applicable Sections. Minor aesthetic customizations or repairs are permitted, provided that they do not impact gameplay (see <T4> ).

Examples of permissible modifications include, but are not limited to:

• Applying threadlocker to Field Element mounting hardware
• Using non-VEX electrical tape to add required lines to the Field
• Anchoring Field Elements directly to Field risers instead of the metal plates
• Anchoring the metal plates to the underlying surface with hardware or tape
• Utilizing a non-VEX Strap under the Field to tie walls together
• Parts added to the exterior of the Portable Field Perimeter to assist in assembly, transportation, and rigidity during Matches
• Using white tape in place of red/blue tape for the Load Zones.

  Note: In the event that rules are added to utilize the Load Zones, the red and blue tape lines may become required for these zones.

Modifications that may impact Robot functionality and/or how the game is played are generally not allowed. Examples of prohibited modifications include, but are not limited to:

• Unofficial Field Perimeter walls, additional structural elements inside of the Field Perimeter, or unofficial/replica Field Elements
• Additional VEX structural parts attached to a Field Element
• Replacing the opaque Field walls on the VEX Portable Competition Field Perimeter with transparent panels
• Assembling a VEX Portable Competition Field Perimeter without including the securing straps
• Affixing stickers to the foam Field Tiles or otherwise marking object placements for Field reset

Any specific repairs and/or modifications which pertain to the current season’s game will be documented in this rule and Appendix A, as needed.

<T7> Fields at an event must be consistent with each other. There are many types of permissible aesthetic and/or logistical modifications that may be made to competition Fields at the Event Partner’s discretion (see <T6> ). If an event has multiple Head-to-Head competition Fields, they must all incorporate the same permissible/applicable modifications. If an event has multiple Robot Skills Challenge Fields, they must all incorporate the same permissible modifications. For example, if one Head-to-Head competition Field is elevated, then all Head-to-Head competition Fields must be elevated to the same height.

Examples of these modifications may include, but are not limited to:

• Elevating the playing Field off of the floor (common heights are 12” to 24” [30.5cm to 61cm])
• Field control systems (see <T8> )
• Field display monitors
• Field Perimeter decorations (e.g., LED lights, sponsor decals on polycarbonate panels)
• Field Perimeter type (see <T9> )
• Utilizing the VEX GPS Field Code Strips
• Utilizing non-VEX Straps to hold the Field walls together
  

Note: If an event has dedicated Fields for Robot Skills Matches, there is no requirement for them to have the same consistent modifications as the Head-to-Head Fields. See <T21> for more details.

<T8> There are three types of Field control that may be used.

1. A VEXnet Field Controller controlled by Tournament Manager, which connects to a Controller’s competition port via ethernet cable.
2. A V5 Event Brain controlled by Tournament Manager, which connects to a Controller via Smart Cable.
3. A VEXnet Competition Switch, which connects to a Controller’s competition port via Cat-5 cable, may only be used in Practice Matches, Robot Skills Matches, and Leagues, and only under extreme circumstances.

If an event has multiple Fields, then all Fields of the same game type must use the same control system, in accordance with <T7> and <T21>. For example, it would be permissible for Head-to-Head competition Fields to use V5 Event Brains, and for Skills Challenge Fields to use VEXnet Field Controllers. However, it would not be permissible for one Head-to-Head Field to use a V5 Event Brain while another Head-to-Head Field uses a VEXnet Field Controller.

Note: Official Qualifying Events may only use the official, unmodified version of Tournament Manager for field control, along with approved hardware and networking solutions. Add-ons that abide by the TM Public API guidelines are permitted. Once add-ons are enabled, the software is no longer supported by VEX Robotics, or DWAB Technologies; any necessary troubleshooting will be done at the user’s own risk.

<T9> There are two types of Field Perimeter that may be used.

1. VEX Metal Competition Field Perimeter (SKU 278-1501).
2. VEX Portable Competition Field Perimeter (SKU 276-8242).

See Appendix A for more details.

If an event has multiple Fields, then all Fields of the same game type must use the same Field Perimeter type, in accordance with <T7> and <T21>. For example, it would be permissible for Head-to-Head competition Fields to use metal Field Perimeters, and for Skills Challenge Fields to use Portable Field Perimeters.

However, it would not be permissible for one Head-to-Head Field to use a metal Field Perimeter, while other Head-to-Head Fields use Portable Field Perimeters.

<T10> Qualification Matches follow the Match Schedule. A Qualification Match Schedule will be available on the day of competition. The Match Schedule will indicate Alliance partners, Match pairings, and Alliance colors for each Match. For Tournaments with multiple Fields, the schedule will indicate which Field each Match will take place on.

1. Practice Matches may be included in the Match Schedule at some events, but are not required. If Practice Matches are run, every effort will be made to equalize practice time for all Teams.
2. A Qualification Match can only start before its scheduled time if all Teams, Robots, and assigned volunteers are at the Field and ready to play.
3. Any multi-division event must be approved by VEX Robotics prior to the event, and divisions must be assigned in sequential order by Team number.
4. The Match Schedule is subject to change at the Event Partner’s discretion. Events should generally wait to generate the Match Schedule until all Teams have checked in and passed Robot Inspection, or when it has been confirmed that Teams will not be participating.
5. If it is determined by both the Event Partner and VEX Robotics that a Team should be removed from further Matches at the event based on the outcome of a serious Violation, the Event Partner can use the full-event Disqualification feature in TM to remove that Team from all further Matches at the event. Their spots in later Qualification Matches will be replaced automatically by Teams from the end of the Match Schedule, and Matches will be removed from the end of the schedule as appropriate. The Event Partner cannot do this without permission from VEX Robotics.

<T11> Each Team will have at least six Qualification Matches.

1. A Tournament must include a minimum of six Qualification Matches per Team at local qualifying events or eight Qualification Matches per Team at a Championship event. The recommended number of Qualification Matches per Team is eight for a standard Tournament, and up to ten for a championship event.
2. A league must include at least three league ranking sessions, with at least one week between sessions. Each session must include a minimum of two Qualification Matches per Team at that session. The suggested number of Qualification Matches per Team for a standard league ranking session is four. Leagues will have a championship session where elimination rounds will be played. Event Partners may also choose to have Qualification Matches as part of their championship session.

<T12> Qualification Matches contribute to a Team’s ranking for Alliance Selection.

1. When in a Tournament, every Team will be ranked based on the same number of Qualification Matches.
2. For Tournaments that have more than one division, Teams will be ranked among all Teams in their specific division.
3. When in a league, every Team will be ranked based on the number of Matches played. Teams that participate in at least 60% of the total Matches available will be ranked above Teams that participate in less than 60% of the total Matches available; e.g., if the league offers 3 ranking sessions with 4 Qualification Matches per Team, Teams that participate in 8 or more Matches will be ranked higher than Teams who participate in 7 or fewer Matches. Being a no-show to a Match that a Team is scheduled in still constitutes participation for these calculations.
4. In some cases, a Team will be asked to play an additional Qualification Match. The extra Match will be identified on the Match Schedule with an asterisk; Win Points, Autonomous Points, and Strength of Schedule Points for that Qualification Match will not impact a Team’s ranking, and will not affect participation percentage for leagues.
   1. Teams are reminded that <G1> is always in effect and Teams are expected to behave as if the additional Qualification Match counted.
   2. In leagues, Teams may have a different number of Qualification Matches. Rankings are determined by the Win Percentage, which is the number of wins divided by the number of Qualification Matches that Teams have played.

<T13> Qualification Match tiebreakers. Team rankings are determined throughout Qualification Matches as follows:

1. Average Win Points (Win Points / number of Matches played)
2. Average Autonomous Points (Autonomous Points / number of Matches played)
3. Average Strength of Schedule Points (Strength of Schedule Points / number of Matches played)
4. Highest Match score
5. Second-highest Match score
6. Random electronic draw

<T14> Small Tournaments have fewer Alliances. The number of Alliances for a given event is determined as follows, except in extraordinary circumstances with the permission of VEX Robotics:

This rule is applied differently for VEX U. See rule <VUT7>.

<T15> Send a Student representative to Alliance Selection. Each Team must send one Student representative to the playing Field (or other designated area) to participate in Alliance Selection. If the Team representative fails to report in for Alliance Selection, their Team will be ineligible for participation in the Alliance Selection process.

Once the Alliance Selection begins, Student representatives cannot use electronic devices unless they have been demonstrated to be in airplane mode. No electronic communication by or with Student representatives is allowed during the Alliance Selection process.

Teams are advised to complete their scouting prior to the beginning of Alliance Selection, and to come to Alliance Selection prepared with a written list of potential Alliance Partners. Non-electronic methods of communication are allowed. Rule <G2> and the Student-centered Policy still apply during Alliance Selection. Any communication about Alliance Selection and specific Teams should be limited to Student Team Members.

<T16> Each Team may only be invited once to join one Alliance. If a Team representative declines an Alliance Captain’s invitation during Alliance Selection, that Team is no longer eligible to be selected by another Alliance Captain. However, they are still eligible to play Elimination Matches as an Alliance Captain. This video includes a full explanation of the Alliance Selection process.

For example:

• Alliance Captain 1 invites Team 000A to join their Alliance.
• Team 000A declines the invitation.
• No other Alliance Captains may invite Team 000A to join their Alliance.
• However, Team 000A may still form their own Alliance if Team 000A is ranked high enough after Qualification Matches to become an Alliance Captain.

Note: Alliances must have two Teams, and there are no “do-overs” during Alliance Selection. If enough Teams decline their invitations such that the full number of Alliances cannot be filled, the event will proceed with a reduced number of Alliances.

<T17> Elimination Matches follow the Elimination Bracket. A sixteen (16) Alliance bracket plays as shown in Figure T17-1, with Matches proceeding in numbered order through each round.

If an event is run with fewer than 16 Alliances, then they will use the bracket shown in Figure T17-1, with Byes awarded when there is no applicable Alliance. For example, in a Tournament with 12 Alliances, Alliances 1, 2, 3, & 4 would automatically advance to the Quarterfinals.

Thus, an eight (8) Alliance bracket would run as shown below:

At events with multiple divisions, each division champion Alliance will advance to the overall event finals. Alliance color assignment for these Matches will be determined by the original Alliance seeding within their respective divisions. The higher seeded Alliance (e.g., 1 is higher than 2) will be designated as the red Alliance, and the lower-seeded Alliance will be designated as the blue Alliance.

If both Alliances hold the same seed number within their divisions, the Event Partner will conduct a coin flip to determine which Alliance is assigned to the red Alliance, with the remaining Alliance assigned to blue.

<T18> Elimination Matches are a blend of “Best of 1” and “Best of 3.” “Best of 1” means that the winning Alliance in each Match advances to the next round of the Elimination Bracket. “Best of 3” means that the first Alliance to reach two wins will advance.

See the flowchart below for more information.

<T19> Ties in Elimination Matches lead to limited rematches. In the case of tied Matches during Elimination Matches, Tournament Manager will apply the following logic to determine which Alliance will progress to the next round.

1. In a “Best of 1” Elimination Round, the higher-seeded Alliance will advance and be declared the winner under the following guidelines.
   1. After two (2) ties in a non-finals Match.
   2. After three (3) ties in a finals Match.
2. For single-division events or within a division: in a ”Best of 3” Elimination Round, the higher-seeded Alliance will advance and be declared the winner under the following guidelines.
   1. After three (3) ties in a round in which neither Alliance has yet won a Match (0-0).
   2. After two (2) ties in a round in which each Alliance has won a single Match (1-1).
3. For single-division events or within a division: after two (2) ties in a “Best of 3” Elimination Round in which one Alliance has won a single Match (1-0), the Alliance with one (1) win will be declared the winner.
4. For a “Best of 3” overall Finals round at a multi-division event, Teams should continue to play tiebreaker Matches until one Alliance has won two (2) Matches.

<T20> Skills Match Schedule. Teams play Robot Skills Matches on a first-come, first-served basis. Each Team will get the opportunity to play exactly three (3) Driving Skills Matches and three (3) Autonomous Coding Skills Matches at each Tournament and/or League Session.

Teams should review the event agenda and their Match Schedule to determine when the best possible time is to complete their Robot Skills Matches. If the Robot Skills Challenge area closes before a Team has completed all six (6) Robot Skills Matches, but it is determined that there was adequate time given, then the Team will automatically forfeit those unused Matches.

<T21> There is no requirement that Skills Challenge Fields have the same consistent modifications as the Head-to-Head Fields. For example, there is no requirement that all Skills Challenge Fields are elevated to the same height as Head-to-Head Fields. However, all Skills Challenge Fields at a single event must use the same type of Field control and Field Perimeter, as described in rules <T8> and <T9>.

It is strongly recommended/preferred that all Skills Challenge Fields are consistent with each other, but this may not be the case in extreme circumstances. In order to use non-conforming Head-to-Head Fields for Skills Challenge runs (e.g. during lunch), the following steps should be taken:

• Teams must be informed that the Head-to-Head Fields may have some differences from the Skills Challenge Fields (e.g., they might not have GPS strips).
• Teams must be given an opportunity to select which type of Field they want to use, i.e. they cannot be required to use a Head-to-Head Field for any Skills Challenge run.

<T22> Skills Rankings at events. Teams will be ranked at an event based on the following scores and tiebreakers:

1. Sum of highest Autonomous Coding Skills Match score and highest Driving Skills Match score.
2. Highest Autonomous Coding Skills Match score.
3. Second-highest Autonomous Coding Skills Match score.
4. Second-highest Driving Skills Match score.
5. Highest sum of Skills Stop Times (see rule <RSC5> ) from a Team’s highest Autonomous Coding Skills Match and highest Driving Skills Match (i.e., the Matches in point 1).
6. Highest Skills Stop Time from a Team’s highest Autonomous Coding Skills Match (i.e., the Match in point 2).
7. Third-highest Autonomous Coding Skills Match score.
8. Third-highest Driving Skills Match score.
9. If a tie cannot be broken after all above criteria, then the following ordered criteria will be used to determine which Team had the “best” Autonomous Coding Skills Match :
   1. Quantity of Scored Pins
   2. Number of Toggles set to a color other than yellow
10. If the tie still isn’t broken, the same process in Step 9 will be applied to each Team’s best Driving Skills Match.
11. If the tie still isn’t broken, events may choose to allow Teams to have one more deciding Driving Skills Match, to be ranked according to the standard criteria above, or declare both Teams the Robot Skills Challenge Winner.

<T23> Skills Rankings Globally. Teams will be ranked globally based on their Robot Skills scores from Tournaments and Leagues that upload results to events.vex.com, according to the following tiebreakers:

1. Highest Robot Skills score (combined Autonomous Coding Skills Match and Driving Skills Match Score from a single event).
2. Highest Autonomous Coding Skills Match score (from any event).
3. Highest sum of Skills Stop Times (see rule <RSC5> ) from the Robot Skills Matches used for point 1.
4. Highest Skills Stop Time from the Autonomous Coding Skills Match used for point 2.
5. Highest Driving Skills Match score (from any event).
6. Highest Skills Stop Time from the Driving Skills Match score used for point 5.
7. Earliest posting of the highest Autonomous Coding Skills Match score. The first Team to post a score ranks ahead of other Teams that post the same score at a later time, all else being equal.
8. Earliest posting of the highest Driving Skills Match score. The first Team to post a score ranks ahead of other Teams that post the same score at a later time, all else being equal.

<T24> Robot Skills at League Events. At league events in which Teams may submit Robot Skills Challenge scores across multiple sessions, the Robot Skills scores (combined highest Autonomous Coding Skills Match and Driving Skills Match scores) used for rankings will be calculated from Matches within the same session.

For example, consider the following scores for a hypothetical Team across two league event sessions:

This Team would have a Robot Skills score of 140 for this event, and their scores from Session 2 would be used for the Event and Global tiebreakers listed in <T22> and <T23>.

Section 6 - VEX U

Introduction

While many colleges and universities already use the VEX V5 system in their academic classes, many more have extensive manufacturing capabilities beyond the standard “VEX metal” library. Fabrication techniques like machining and 3D printing are more common than ever in collegiate engineering programs, and we can’t wait to see what VEX U Robotics Competition Teams from around the world are able to create under these more advanced rules.

As in past years, the season will include a culminating VEX U event at the VEX Robotics World Championship, along with regional Tournaments across the world. Participating schools will get the chance to prove their abilities in front of thousands of future engineers and show off what truly makes their school remarkable. The VEX U Robotics Competition is the perfect project-based supplement to many university level engineering programs, and gives Students the unique opportunity to demonstrate their real-world skills to potential employers, such as our event sponsors.

Game, Robot, and Tournament Rules

The VEX U Robotics Competition uses the VEX V5 Robotics Competition Override Field with some minor modifications. Anyone that has a V5RC Override Field can use it for a VEX U event or Team. Please consult earlier sections of this game manual for the basic set of competition rules and details. All of the standard rules apply, except for the modifications listed in this section. In the event of a conflict between rules, the rules listed in this Section of the game manual and any rulings on the official VEX U Q&A take precedence.

VURC Definitions

Additional Electronics - Any Sensor, processor, or other electronic component used in Robot construction, and connected to the V5 Robot Brain, that is not sold by VEX Robotics. Examples include commercially-available devices (e.g., Raspberry Pi) or custom devices designed and fabricated by the Team. See <VUR12> and <VUR13> for more details.

Alliance - A grouping of two (2) Robots from the same Team that have been chosen by the Students to play together during a given Match.

Electromechanical Assembly - A complex system composed of multiple off-the-shelf components, which may include Sensors, mechanical parts, and actuators.

External Processor - A computing device or microcontroller that independently processes Sensor data before sending it to the VEX V5 Brain.

Fabricated Part - Any component used in Robot construction that is fabricated by Team members. See <VUR3> through <VUR7> for more details.

Raw Stock - Stock materials purchased from third-party vendors that may be used to create Fabricated Parts. See <VUR4> and <VUR5>.

Sensor - A device that detects and responds to changes in the environment, providing data to the Robot’s control system.

VEX U Student - A Team member that meets all criteria listed in rule <VUT6>.

Rule Modifications: Field Setup

The VURC playing Field is set up differently than a Head-to-Head VEX V5 Robotics Competition Override Match, with the following modifications:

• The VEX GPS code strip must be installed on the Field.
• Modified Field layout. Only the Midfield Goal should begin the Match with a yellow/yellow Pin Placed in it.
• Modified Match Loads. Each Alliance gains an additional two yellow/yellow Pins that begin off the Field as Match Loads.
  • Red Alliance Match Loads : 10 Cups, 10 red/yellow Pins, and 3 yellow/yellow Pins
  • Blue Alliance Match Loads : 10 Cups, 10 blue/yellow Pins, and 3 yellow/yellow Pins

Rule Modifications: Game

<VUG1> Different Robot starting sizes. See <VUR1>.

<VUG2> Different Robot placement than rule <GG10>. The red Team has the right to place one Robot on the Field first, followed by both blue Robots, and ending with the 2nd red Robot. This applies in Qualification Matches and Elimination Matches. If this right is used, once a Team has placed a Robot on the Field, its position cannot be readjusted prior to the Match.

<VUG3> Some electronic devices may be in motion or moving at the beginning of the Match. This includes active cooling fans, spinning LIDAR modules, and/or other similar sensors or Additional Electronics. These electronic devices should not initiate any form of motion for the entire Robot or any of its subsystems, and may not directly interact with Scoring Objects and/or other Robots.

<VUG4> Different availability of Loaders. Drive Team Members may introduce Match Load Scoring Objects into the Loaders adjacent to their Alliance Station during the Autonomous Period and Driver Controlled Period of the Match.

<VUG5> Different scoring during the Autonomous Period. The following are included in the calculation of an Alliance’s score for the purposes of determining the Autonomous Bonus :

1. A yellow Pin that is Placed in the Midfield is Owned by the Alliance that ends the Autonomous Period with a greater number of Robots in the Midfield.
2. Points for ending the Autonomous Period in the Midfield.

<VUG6> Different Autonomous Win Point criteria. An Autonomous Win Point is awarded to any Alliance that ends the Autonomous Period with all of the following tasks completed, and that has committed no Violations during the Autonomous Period :

1. At least twelve (12) Pins Scored for your Alliance. (Does not include Pins Placed in Quadrants on the opposing side of the Autonomous Line ).
2. At least four (4) Goals each contain at least two (2) Pins Scored for your Alliance. (Does not include Goals in Quadrants on the opposing side of the Autonomous Line ).
3. Neither Robot is contacting the Field Perimeter.
4. At least one (1) Robot is within the Midfield.

<VUG7> Different expansion in the Midfield during the Endgame period. Vertical expansion is limited to 24” for any Robot that is partially or entirely within the infinite 3D vertical projection of the Midfield during the Endgame period.

Rule Modifications: Robot Skills Challenge

All rules apply from V5RC Section 3: Robot Skills Challenge, with no modifications other than those noted below.

<VURS1> VEX U Robot Skills Matches are set up differently than VEX V5 Robotics Competition Robot Skills Matches, with the following modification:

1. Modified Match Loads. Four (4) red/yellow Pins, six (6) blue/yellow Pins, and ten (10) Cups begin off the Field as Match Loads. See figure VURS1.

<VURS2> Teams are permitted to use both Robots in their VEX U Robot Skills Matches, per <VUT1> and <VUR1>.

<VURS3> Both Robots must start the Robot Skills Match in legal starting positions for the red Alliance. All other portions of rule <SG1> apply. Each Robot must use one red/yellow Pin as a Preload in accordance with <SG5>.

Rule Modifications: Tournament

<VUT1> Instead of a 2-Team Alliance format, VURC Head-to-Head Matches will be played 1-Team vs. 1-Team. Each Team will use two (2) Robots in each Match.

1. Teams are allowed to build and bring as many Robots as they would like, but only two (2)—one of each size as described in <VUR1> —may be brought from the pit to the playing Field for any Match.
2. All Robots must pass inspection before they are allowed to compete.

<VUT2> Qualification Matches will be conducted in the same manner as in a V5RC tournament, but in the revised 1v1 format described in <VUT1>.

<VUT3> Elimination Matches will be conducted in the same manner as in a V5RC tournament, but without an Alliance Selection. At the end of the competition, one Team will emerge as the Tournament champion.

<VUT4> The Autonomous Period at the beginning of each Head-to-Head Match will be 30 seconds.

1. Human interaction with Robots during the Autonomous Period is strictly prohibited.
2. If both Teams complete their routines before 30 seconds have elapsed, they have the option to signal that they wish to end the Autonomous Period early. Both Teams and the Head Referee must all agree on the “early stop.” This is not a requirement, and the option must have been established for all Teams at the event, such as during the event meeting.
   
   

<VUT5> The Driver Controlled Period is shortened to 90 seconds and immediately follows the Autonomous Period.

<VUT6> VEX U Student eligibility.

1. All VEX U Team members MUST be matriculated in a post-secondary school OR have earned a post-secondary education diploma, certificate, or other equivalent during the six (6) months preceding the VEX Robotics World Championship. The intent of this rule is to permit VEX U Students graduating mid-year to still be able to finish their competition season.
2. Professionals not enrolled in post-secondary education are not eligible to participate on a VEX U Team.
3. Students who are dual-enrolled in both a secondary school and in post-secondary courses are not eligible to participate on a VEX U Team.
4. VEX U Students may only be on exactly one (1) VEX U Team for the season. See <G5>.
5. If at least one member of a VEX U Robotics Team is aged 18 or older, rule <S2> does not apply.