Quick Reference Guide

Section 1 - Introduction

Overview

This section provides an introduction to the VEX V5 Robotics Competition (V5RC) and V5RC Push Back.

The VEX V5 Robotics Competition

The world around us is constantly changing, and so are the ways we learn. Traditional classroom methods don’t always capture the hands-on problem solving and collaboration that are essential in STEM fields. Competitive robotics provides an alternative approach—one that engages students in real-world applications of engineering, coding, and design. Instead of just reading about these concepts, you get to experience them firsthand as you test ideas, refine solutions, and work as part of a team to overcome challenges. By combining creativity with technical skills, the VEX V5 Robotics Competition helps make STEM learning more dynamic, practical, and inspiring.

Competitive robotics isn’t just about building a robot—it’s about learning to approach challenges with confidence, resilience, and teamwork. The same problem-solving mindset that helps you design and refine a VEX robot is the foundation for tackling real-world engineering problems, scientific breakthroughs, and technological innovations. Push Back is more than just a game—it’s an opportunity to develop skills that will shape the problem solvers and innovators of tomorrow.

Working together with other people—whether it be your own teammates or someone from another organization—can be challenging, but it’s just as much a part of the VEX V5 Robotics Competition as building a robot.

Within this manual, you’ll find the rules that define Push Back. These rules are designed to create a competitive yet fair environment that rewards creativity, strategy, and collaboration. Just like in the real world, constraints exist to challenge you—not to limit your potential, but to inspire innovative solutions.

As you embark on this season, remember that every challenge is an opportunity to grow. Whether you’re fine-tuning your design, refining your strategy, or working through unexpected setbacks, the lessons you learn here will stay with you far beyond the competition field.

Good luck, and we look forward to seeing your creativity and innovation in action!

Sincerely,

The VEX Robotics Game Design Committee, composed of members from VEX Robotics, the Robotics Education & Competition Foundation, and DWAB Technology

V5RC Push Back: A Primer

VEX V5 Robotics Competition Push Back is played on a 12’x12’ square Field, set up as illustrated in the figures throughout.

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 (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 Scoring Blocks in Goals, Controlling zones within Goals, clearing Loaders, and Parking in defined zones at the end of the Match.

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 4 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.

About the Game Manual - A Note from the GDC

This Game Manual contains everything there is to know about this season’s game, V5RC Push Back. It is intended to be a resource for all Teams, Head Referees, Event Partners, and other members of the V5RC community.

The rules contained in the following pages can be thought of as “constraints” that define this game, just as engineers begin any design project by defining their constraints. At the beginning of a season, “constraints” are all we have. We don’t know what the winning Robot, best strategy, or most-frequently violated rule will be any more than you do. Isn’t that exciting?

When exploring a new game, please approach this Game Manual with that mentality of looking at rules as constraints. The Game Manual and its appendices—and the official Q&A on RobotEvents.com— contain the full and complete list of constraints that are available for competitors to strategize, design, and build their Robots.

Obviously, all Teams must adhere to these rules, and any stated intents of these rules. However, beyond that, there is no “right” way to play. There are no hidden restrictions, assumptions, or intended interpretations beyond what is written here. So, it is up to you, the competitor, to find the path through these constraints that best suits your Team’s goals and ambitions.

Our Intent - How We Want the Game Played

The Game Design Committee (GDC) carefully designs each VEX Robotics Competition game with a clear vision of how we believe it should be played. The GDC envisions Push Back as a fast-paced game driven by constant back-and-forth action, where Teams must balance strategies to maintain control of Goals around the Field. Teams are encouraged to actively manipulate both their own and their opponents’ game pieces, creating dynamic shifts in scoring opportunities throughout the Match. Due to this continuous interaction, Offensive strategies should naturally be more effective than purely Defensive ones. At all times, there should be an open lane for a Robot to score into a Goal, ensuring that gameplay remains fluid and engaging. With a large quantity of Blocks available in both colors, no Team should ever be without access to their own game pieces. This design ensures that Teams remain focused on strategic decision-making, adaptability, and active gameplay rather than passive blocking or hoarding.

As the season progresses and Teams develop new strategies, certain aspects of gameplay may evolve in ways that were not initially anticipated. To ensure that the game remains fair, competitive, and aligned with its original intent, the GDC has identified key areas that may be subject to clarification or adjustment throughout the season. While updates are not limited to these areas, the GDC believes these are some of the most critical for maintaining the integrity of gameplay:

• No Possession Limit: The GDC has intentionally designed this game without a possession limit, as we believe such a restriction would hinder strategic play. However, we are mindful of potential exploitation, such as excessive hoarding of game objects. If it becomes clear that this is negatively impacting gameplay, we will consider implementing a possession limit. If a possession limit is implemented, the limited quantity could also be subject to future updates. Any updates to this quantity should not be more than 3-5 Blocks per update.
• Size of the Control Zone for Long Goals: The GDC may adjust the size of this zone if it is determined to be disproportionate to the flow of gameplay. Any change to this zone should be limited to no more than one Block size per update to ensure gradual, controlled adjustments.
• Goal Defense: The GDC intends for Matches to remain dynamic and offense-driven. While Defensive strategies are a natural part of gameplay, excessive Goal-tending or prolonged stalemates are not in the spirit of the game. If Defensive play becomes too dominant, the GDC will consider rule adjustments to incentivize more Offensive engagement.

Any potential adjustments would be made with the goal of ensuring that the game plays as intended for the duration of the season. While we will try our best to adhere to the self-imposed limits on change per update, we may make larger/broader changes if it is deemed absolutely necessary. Any updates will be communicated through official rule updates.

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/25-26/v5rc-pushback-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 GDC.

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 V5RC Hub app, and shared via VEX Robotics / REC Foundation social media & email marketing channels. Once announced, the new version of the Game Manual will be immediately available at the link above.

Generally, Push Back 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 should 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.

During the 7-day grace period, the previous manual version will be available at https://link.vex.com/docs/25-26/v5rc-pushback-manual-obsolete. This link will be only be active during the grace period following each manual update, and will be disabled once it ends.

The GDC 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 RobotEvents 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 27th.

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

1. Read and search the manual before posting.
2. Read and search existing Q&As before posting.
3. Quote the applicable rule from the latest version of the manual in your question.
4. Make a separate post for each question.
5. Use specific and appropriate question titles.
6. Questions will (mostly) be answered in the order they were received.
7. This system is the only source for official rules clarifications.

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.

Additional Policies

The rules and guidelines in these official documents and policies apply to Teams and events in the VEX Robotics Competitions alongside the rules in this Game Manual.

• Code of Conduct - Outlines the expectations of behavior and ethical standards for all attendees at REC Foundation-sanctioned events.
• Student-Centered Policy - Communicates the REC Foundation’s goal of maximizing learning opportunities for Students, and the mandate that Students use designs, code, and game strategies that are consistent with their abilities and knowledge. The related Important Behavior Guidelines for Team Adults provides guidelines for Adults to promote Student-centeredness when interacting with Teams.
• Commitment to Coach Excellence - Communicates the partnership and expectations between the REC Foundation and Coaches. Must be agreed to during Team registration.
• Commitment to Event Excellence - Communicates the partnership and expectations between the REC Foundation and Event Partners, with the goal of providing Teams with quality and uniform competition experiences throughout our programs.
• Guide to Judging - Provides policies and procedures for the judging process, and guidelines for Teams’ engineering notebooks.
• Organizational Policy - Provides guidelines for organization and Team numbers that are assigned during Team registration.
• Qualifying Criteria - Provides the criteria that Teams and events must meet to qualify for Event Region Championships and the VEX Robotics World Championship.
• Youth Protection Policy - Provides information, guidelines, and procedures to create safe environments for participants in our range of programs.

Field Overview

The V5RC Push Back Field consists of the following:

• 88 Blocks
  
  
  • 44 blue Blocks
    
    
    • 2 Preloads
    • 12 Match Loads
    • 18 that start the Match in predetermined locations on the Field
    • 12 that start the Match in Loaders
  • 44 red Blocks
    
    
    • 2 Preloads
    • 12 Match Loads
    • 18 that start the Match in predetermined locations on the Field
    • 12 that start the Match in Loaders
• Four Loaders, two adjacent to each Alliance Station
• Four Goals
  
  
  • 2 Long Goals
  • 2 Center Goals, one Upper and one Lower
• 2 Park Zones, one blue and one red

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 and Scoring Elements 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.

Figure FO-1: An overhead view of the V5RC Push Back Field, with Alliance Stations (orange), Loaders (yellow), Park Zones (pink), and Goals (green) highlighted.

Figure FO-2: An overhead view of the V5RC Push Back Field in its starting configuration, with highlighted Blocks (Red / Blue).

Figure FO-3: The recommended locations of the Field Monitor (green), Head Referee (black & white stripes), and Scorekeeper Referees (black & white checkerboard).

General Definitions

Adult - Anyone who is not a Student or another defined term (e.g., Head Referee).

Alliance - A pre-assigned grouping of two (2) Robots that are paired together during a given Match.

Alliance Station - The designated regions where the Drive Team Members must remain for the duration of the Match.

Autonomous Bonus - A point bonus awarded to the Alliance that has earned the most points at the end of the Autonomous Period. See <SC5> for more information.

Autonomous Win Point (AWP) - An additional Win Point awarded to any Alliance that has completed a defined set of tasks at the end of the Autonomous Period of a Qualification Match. Both Alliances can earn an Autonomous Win Point if both Alliances accomplish these tasks. See <SC6> for more information.

Defensive - A category of strategies, Robot actions, and/or Robot statuses that can be employed by a Team during a Match; see rules <GG14> and <GG15> for more information. A Robot is Defensive while it is engaged in actions that cannot increase its Alliance's score for the current Match, and instead limits an opponent’s ability to score or play the game. A Robot can be in possession of a scoring object and capable of scoring, but still be Defensive based on its actions. Examples include, but are not limited to:

• De-scoring in a way that doesn't increase points for the Robot's own Alliance
• Limiting access to a portion of the Field while not attempting to score
• Holding, blocking, impeding, or otherwise restricting or controlling an opponent’s movements
• Goalkeeping

Disablement - A penalty applied to a Team for a safety Violation. A Team that receives a Disablement is not allowed to operate their Robot for the remainder of the Match, and the Drive Team Member(s) will be asked to place their controller(s) on the ground or another safe location outside of the Field, as directed by the Head Referee.

Disqualification - A penalty applied to a Team for a Major Violation. A Team that receives a Disqualification in a Qualification Match receives zero (0) Win Points, (0) Autonomous Win Points, (0) Autonomous Points, and (0) Strength of Schedule Points. When a Team receives a Disqualification in an Elimination Match, the entire Alliance is Disqualified and they receive a loss for the Match. At the Head Referee’s discretion, repeated Violations and/or Disqualifications for a single Team may lead to its Disqualification for the entire tournament (see <GG6>). A Team that receives a Disqualification in a Driving Skills Match or Autonomous Coding Skills Match receives a score of zero (0) for that Robot Skills Match.

Drive Team Member - A Student who stands in the Alliance Station during a Match. Adults are not allowed to be Drive Team Members. See rule <GG1>.

Entanglement - A Robot status. A Robot is Entangled if it has grabbed, hooked, or attached to an opposing Robot or a Field Element. See rule <GG14>.

Field - The entire playing Field, comprising of the Floor and the Field Perimeter.

Field Element - The Field, white tape, Loaders, Goals, Park Zones, and all supporting structures and accessories (such as field monitors, etc.).

Field Perimeter - The outer part of the Field, made up of 12 straight sections.

Floor - The interior flat part of the playing Field, made up of an array of six (6) gray foam field tiles wide by six (6) gray foam field tiles long (totaling 36 field tiles) that are within the Field Perimeter.

Game Design Committee (GDC) - The creators of Push Back, and authors of this Game Manual. The GDC is the only official source for rules clarifications and Q&A responses; see Section 1.

Holding - A Robot status; see rule <GG17> for more information. Holding is legal until it exceeds the limits in <GG17>. A Robot is considered to be Holding if it meets any of the following criteria during a Match:

• Trapping - Limiting the movement of an opponent Robot to a small or confined area of the Field, approximately the size of one foam field tile or less, without an avenue for escape. Note that if a Robot is not attempting to escape, it is not considered Trapped.
• Pinning - Preventing the movement of an opponent Robot through contact with the Field Perimeter, a Field Element, or another Robot.
• Lifting - Controlling an opponent’s movements by raising or tilting the opponent’s Robot off of the foam tiles. Preventing a Robot that is already off of the Floor from returning to the Floor may also be considered Lifting or Trapping.

Match - A set time period, consisting of a Autonomous Period and/or Driver Controlled Periods, during which Teams play a defined version of Push Back to earn points.

• Autonomous Period - A time period during which Robots operate and react only to sensor inputs and pre-programmed commands.
• Driver Controlled Period - A time period during which Drive Team Members operate their Robot via remote control.

*Note: The time periods in VAIRC are referred to as the Isolation Period and the Interaction Period.

Offensive - A category of strategies, Robot actions, and/or Robot statuses that can be employed by a Team during a Match; see rules <GG14> and <GG15> for more information. A Robot is Offensive while it is engaged in actions that could directly increase its Alliance's score for the current Match. Examples include, but are not limited to:

• Adding an object to a Goal to score points
• Moving toward a Goal with an object that could earn points for their Alliance
• Changing the status of a Field Element or scoring object that acts as a multiplier or scoring bonus for their Alliance
• Achieving (or attempting to achieve) any Robot status that adds points to their Alliance's score
• Obtaining (or attempting to obtain) scoring objects

Robot - A machine that has passed inspection, designed by Student Team members to execute one or more tasks autonomously and/or by remote control from a Drive Team Member.

Student - A person is considered a Student if they meet both of the following criteria:

1. Anyone who is earning or has earned credit toward a secondary school (i.e., high school) diploma, certificate, or other equivalent during the six (6) months preceding the VEX Robotics World Championship. Courses earning credits leading up to high school would satisfy this requirement.
2. Anyone born after May 1, 2006 (i.e., who will be 19 or younger at VEX Worlds 2026). Eligibility may also be granted based on a disability that has delayed education by at least one year.
   
   
   • Middle School Student - A Student born after May 1, 2010 (i.e., who will be 15 or younger at VEX Worlds 2026). Any Students who meet this criteria may also compete as High School Students.
   • High School Student - Any eligible Student that is not a Middle School Student.

Team - One or more Students make up a Team. To participate in an official VEX V5 Robotics Competition event, a Team must first register on RobotEvents.com and receive a VEX V5 Robotics Competition Team number. A Team's unique number identifies their organization and their Team within that organization. Each Team must build their own Robot, create their own code, and maintain their own Engineering Notebook if they choose to use one.

• A Team is classified as a Middle School Team if all members are Middle School Students.
• A Team is classified as a High School Team if any of its members are High School Students, or if the Team is made up of Middle School Students who declare themselves “playing up” as High School Students by registering their Team as a High School Team.
• Once a Team has competed in an event as a High School Team, that Team may not change back to a Middle School Team for the remainder of the season. If a Team mistakenly registers as a Middle School Team but is ineligible for that age group, their registration may be revised mid-season with RSM assistance; all prior qualifications for the season will be lost.
• Teams may be associated with schools, community/youth organizations, or groups of neighborhood Students.

In the context of this Game Manual, Teams include three types of Student roles related to Robot build, design, and coding. See <G2> and <G5> for more information. Adults may not fulfill any of these roles.

• Builder - The Student(s) on the Team who assemble(s) and repair(s) the Robot. Adults are permitted to teach the Builder(s) how to use concepts or tools associated with Robot construction, but should never work on the Robot.
• Coder - The Student(s) on the Team who write(s) the computer code that is downloaded onto the Robot. Adults are permitted to teach the Coder(s) how to use concepts or tools associated with programming, but should never work on the code that goes on the Robot.
• Designer - The Student(s) on the Team who design(s) the Robot. Adults are permitted to teach the Designer(s) how to use concepts or tools associated with design, but should never work on the design of the Robot.

Time Out - A single break period no greater than three minutes (3:00) allotted for each Alliance during the Elimination Bracket. See <GG7>.

Violation - The act of breaking a rule in the Game Manual.

• Minor Violation - A Violation which does not result in a Disqualification.
  
  
  • Accidental, momentary, or otherwise non Match Affecting Violations are usually Minor Violations.
  • Minor Violations usually result in a verbal notification from the Head Referee during the Match, which should serve to inform the Team that a rule is being Violated before it escalates to a Major Violation.
• Major Violation - A Violation which results in a Disqualification.
  
  
  • Unless otherwise noted in a rule, all Match Affecting Violations are Major Violations.
  • If noted in the rule, egregious or strategic Violations or intentional actions that result in Violations may also be Major Violations.
  • Multiple Minor Violations within a Match or tournament may escalate to a Major Violation at the Head Referee’s discretion or as specified in a rule. Minor Violations carry over into Eliminations unless otherwise specified within a rule.
• Match Affecting - A Violation which changes the winning and losing Alliance in the Match.
  
  
  • Multiple Violations within a Match can cumulatively become Match Affecting.
  • When evaluating if a Violation was Match Affecting, Head Referees will focus primarily on any Robot actions that were directly related to the Violation.
  • Determining whether a Violation was Match Affecting can only be done once the Match is complete and the scores have been calculated.
• CoC-related Violation - A Violation of a rule that relates to the RECF Code of Conduct and related processes. For V5RC, VURC, and VAIRC, the included rules are: <S2>, <G1>,<G2>, <G4>, <G5>, <R1> through <R4>, and Major Violations of <S1>.
  
  
  • Potential CoC-related Violations should be brought to the attention of the Event Partner, and resolved through the Code of Conduct Reporting Process in coordination with the Head Referee, Judge Advisor, and RECF Regional Support Manager. Follow-up investigations are conducted by the RECF Rules & Conduct Committee (RCC). Penalties for confirmed CoC-related Violations can range from single-Match Disqualifications to removal from the program.

Some rules include Violation Notes in red italicized text to denote special circumstances or provide additional clarifications. If no Violation Notes are found in a given rule, then it should be assumed that the above “default” definitions apply.

To determine whether a Violation may have been Match Affecting, check whether the Team who committed the Violation won or lost the Match. If they did not win the Match, then the Violation could not have been Match Affecting, and it was very likely a Minor Violation.

See the flowcharts in figures V-1, V-2, and V-3 for more information, and this article for full details of the event CoC process.

Figure V-1: The process for determining Violations during Robot inspection.

Figure V-2: The process for determining whether or not an infraction should result in a Major Violation or Minor Violation

Figure V-3: The process for determining CoC-related Violations

Game-Specific Definitions

Autonomous Line - The pair of white tape lines that run across the Field, and the space between those lines. See <SG7> for more information.

Block - A blue or red 18-sided hollow plastic polygonal object with flat faces and a weight of approximately 40 grams. Each cross-section measures approximately 3.25” (82mm) between pairs of opposing flat faces, and 3.85” (98mm) between pairs of opposing corners.

Figure B-1: A Block

Control Zone - A defined section of a Goal that can be Controlled by an Alliance at the end of a Match.

• Long Goal - The Control Zone for a Long Goal consists of the space between (but not including) the white tape lines (highlighted in green in Figure CZ-1), and holds up to three (3) Blocks.
• Center Goal, Upper and Lower - The Control Zone for a Center Goal includes the entire Goal.

Figure CZ-1: The Control Zone (highlighted green) of a Long Goal consists of the volume between the white tape lines, as shown.

Controlled - A Control Zone status that is assessed at the end of the Autonomous Period and the end of the Match. A Control Zone is Controlled by an Alliance if a majority of the Blocks in that Control Zone are that Alliance’s color. See rule <SC3> for details.

Goal - A Field Element that is constructed out of plastic and metal components into which Blocks can be Scored. Each Long Goal has a completely enclosed center section between two open sections. Each Goal includes a defined Control Zone.

• Long Goal - Each Long Goal is 48.8” (1239mm) in length, with a 13.33” (339mm) enclosed center section.
• Center Goal, Upper and Lower – Each Center Goal is 22.6” (574mm) in length.

Figure G-1: A Long Goal

Figure G-2: A Center Goal

Goalkeeping - A Robot status and/or Robot action. In Push Back, a Robot is Goalkeeping while it is reaching into any open portion of a Goal while not attempting to change the score of the Match through legal means. A Robot can be in possession of a Block and capable of scoring, but still be Goalkeeping based on its actions. See <SG10> for more information.

Loader - One of four 21.34” (542mm) tall plastic and rubber structures that are attached to the Field Perimeter. Robots may remove Blocks from Loaders during a Match, and Drive Team Members may add Match Load Blocks to Loaders during the Match (see <SG9> for details). Each Loader begins the Match containing (6) Blocks.

Figure L-1:A Loader

Match Load - One of the 24 Blocks, 12 per Alliance, that begin the Match in an Alliance Station and which may be introduced during the Match. See <SG9> for more information.

Parked - A Robot status at the end of the Match. See <SC4>.

Park Zone - A Field Element and enclosed section of the Floor that mark a location where Blocks begin a Match and Robots can be Parked at the end of the Match. Park Zones are made of red or blue plastic extrusions and black plastic connectors, and include the enclosed portions of the Field Tiles. Each Park Zone is 18.87“ (479mm) wide x 16.86” (428mm) deep.

Figure PZ-1:A Park Zone

Scored - A Block status. See <SC2>.

Scoring

<SC1> All Scoring statuses are evaluated after the Match ends. Scores are calculated five (5) seconds after the Match ends, or once all Blocks, 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. For example:
   
   
   1. A Robot which has Parked in a Park Zone but slowly droops down and is in contact with the top of the Field Perimeter at five (5) seconds would not be considered Parked.
   2. A Block which slowly falls out of a Goal at five (5) seconds would not be considered Scored.
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 (5) 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 Blocks 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 Blocks, 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> A Block is considered Scored if it meets all of the following criteria:

1. The Block is in contact with the inside surface(s) of the clear plastic part of a Goal.
• The edge faces of the clear plastic parts are not considered inside surfaces.
2. The Block is not in contact with a Robot of the same color as that Block.
3. The Block is not in contact with the Floor.

Figure SC2-1:This Block is touching the Floor, and would not be considered Scored.

Figure SC2-2: The left (red) Block is not contacting the inside surface of the Goal, so it would not be considered Scored. The right (green) Block is contacting the inside surface of the Goal and is not touching a Robot of the same color, so it is considered Scored.

<SC3> A Control Zone is considered Controlled by an Alliance if a majority of the Blocks Scored in that Control Zone are the same color as the Alliance.

1. For Long Goals, a Scored Block is considered Scored in the Control Zone if it is entirely contained within that Control Zone.
2. A Block must be considered Scored in a Goal (see <SC2>) to also be considered Scored in a Control Zone.

Figure SC3-1: The left-most (red) Block is not fully within the tape lines marking the boundaries of the Control Zone, and therefore would not be considered in determining which Alliance is in control of the Goal. The three other (green) Blocks are fully within the tape lines, and would be considered.

Figure SC3-2:The (green) Block on the right is fully within the tape boundaries, and would be considered as scored.

<SC4> A Robot is considered Parked if it meets all of the following criteria:

1. The Robot is not contacting the Floor outside of its Alliance-colored Park Zone.
2. The Robot is not contacting any Field Elements other than the inside face of the Field Perimeter, the Floor inside of its Alliance-colored Park Zone, and/or the plastic extrusions and connectors that are part of the Park Zone. Contact with these allowed elements is not required.
3. The Robot is at least partially within the vertical projection of its Alliance-colored Park Zone.

Figure SC4-1: This Robot is at least partially within the vertical projection of their Alliance-colored Park Zone, and would be considered as Parked.

Figure SC4-2: Both of these Robots would be considered as Parked, as they satisfy all the criteria listed above.

<SC5> Scoring of the Autonomous Bonus is evaluated immediately after the Autonomous Period ends (i.e., once all Blocks, Field Elements, and Robots on the Field come to rest).

1. Points for Parked Robots 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 five (5) 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.

<SC6> 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) Blocks of the Alliance’s color are Scored.
2. At least three (3) different Goals include at least one (1) Scored Block of the Alliance’s color.
3. At least three (3) Blocks of the Alliance’s color have been removed from Loaders adjacent to the Alliance’s Alliance Station.
4. Neither Robot is contacting the Park Zone barrier.

For events which qualify directly to the World Championship (e.g., Event Region Championships and Signature Events), the following tasks must be completed for an Alliance to receive an Autonomous Win Point. The standard criteria above still apply to all other events.

1. At least ten (10) Blocks of the Alliance’s color are Scored.
2. At least three (3) different Goals include at least two (2) Scored Blocks of the Alliance’s color.
3. At least three (3) Blocks of the Alliance’s color have been removed from Loaders adjacent to the Alliance’s Alliance Station.
4. Neither Robot is contacting the Park Zone barrier.

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, Block, 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 <R3> before it may take the Field again.

Violation Notes: Major Violations should be reported to and/or discussed with the Event Partner during the event, and should be reported to the REC Foundation Rules and Conduct Committee following the event.

<S2> Students must be accompanied by an Adult. No Student may attend a V5RC event without a responsible Adult supervising them. 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.

Violation Notes: Violations should be reported to the Event Partner during the event, and should be reported to the REC Foundation Rules and Conduct Committee following the event.

<S3> 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.

<S4> Wear safety glasses. All Drive Team Members must wear safety glasses or glasses with side shields while at the Field for Matches. While in the pit and queuing areas, it is highly recommended that all Team members wear safety glasses.

<S5> 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.

General Rules

<G1> Treat everyone with respect. All Teams are expected to conduct themselves in a respectful and professional manner while competing in VEX V5 Robotics Competition events. If a Team or any of its members (Students or any Adults associated with the Team) are disrespectful or uncivil to event staff, volunteers, or fellow competitors, they may receive a Disqualification 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.

This rule exists alongside the REC Foundation Code of Conduct. Violation of the Code of Conduct can be considered a Major Violation of <G1> and can result in Disqualification from a current Match, an upcoming Match, an entire event, or (in extreme cases) an entire competition season. The Code of Conduct can be found here.

More information regarding the event Code of Conduct process can be found here.

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

Violation Notes: Any Violations of <G1> may be considered Major Violations and should be addressed on a case-by-case basis. Teams at risk of a Major Violation of <G1> due to multiple disrespectful or uncivil behaviors will usually receive a “final warning,” although the Head Referee is not required to provide one. All Major <G1> Violations/Disqualifications should be reported to and/or discussed with the Event Partner during the event, and should be reported to the REC Foundation Rules and Conduct Committee following the event.

<G2> V5RC is a student-centered program. Adults should not make decisions about the Robot’s build, design, or gameplay, and should not provide an unfair advantage by providing ‘help’ that is beyond the Student’s independent abilities. Students must be prepared to demonstrate an active understanding of their Robot’s design, construction, and programming to judges or event staff. Students should build, design, and code the Robot with minimal Adult involvement.

This rule operates in tandem with the REC Foundation Student Centered Policy, which is available in the REC Library for Teams to reference throughout the season.

Violation Notes: Potential Violations of this rule will be reviewed on a case-by-case basis. By definition, all Violations of this rule become Match Affecting as soon as a Robot which was built or coded by an Adult wins a Match. All reported and/or suspected <G2> Violations should be reported to the Event Partner during the event, and should be reported to the REC Foundation Rules and Conduct Committee following the event.

<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. The Team’s design, Robot, coding, strategy, and ongoing work must represent the skill level of the Students currently on the Team.

• Teams must avoid academic dishonesty and should not copy a Robot or mechanism that has been provided for them. 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 provided by anyone that is not a Student on the Team (including Students on another Team).
• Teams may be inspired by designs by other Teams, and use an idea from someone else to spark innovation, but are expected to document and demonstrate this in their engineering notebook alongside evidence of iteration. Teams are required to present this evidence if asked to do so by a Robot inspector, Head Referee, Event Partner, or Judge.
• Using elements of another design as a starting point is acceptable if the Team is capable of demonstrating evidence of iteration, innovation, and/or modification that makes the design uniquely their own. Documentation should clearly demonstrate the idea that was used for inspiration, and how it was changed for the final implementation on the Team’s Robot. It should be clear that this final implementation is not an exact copy of ANY other original design.
• Failure to demonstrate evidence of iteration, innovation, and/or modification will result in a Violation.
• Teams may use Robot plans and code (e.g., the annual Hero Bot, VEXcode configurations, etc.) provided by VEX Robotics or the RECF, 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. Plans provided by VEX Robotics or the RECF are the only legal plans available for use in competition.
• This rule still applies to Teams within the same school, organization, or club. Robots and/or code sets that are identical or substantially similar to one another across Teams within the same school/organization/club will be considered in Violation of this rule, regardless of whether they compete in the same or different events.

For more information, including acceptable and unacceptable examples of mechanical design, construction, coding, and strategy solutions, please refer to the Student Centered Policy in the RECF Library.

The VEX Robotics Competition and the Robotics Education & Competition Foundation (RECF) recognize that many third-party individuals and organizations produce and distribute Robot designs, instructions, and/or other materials that are not under our direct control. We cannot legally regulate or restrict the activities of these external entities. However, when Teams use these resources in ways that violate the spirit and letter of the VEX Robotics Game Manual—particularly Rules <G2> and <G4>—they undermine the core mission of the program: to provide Students with hands-on opportunities to learn, design, and innovate.

While it is never our intent to punish Students, we can legally regulate and restrict the activities of the Teams in our competitions, and we must preserve the fairness, educational value, and integrity of the competition. Therefore, Teams found to be in Violation of these rules will be held accountable to the strictest interpretations of <G2> and <G4>.

It is the responsibility of each Team to be able to explain and defend the design, construction, and programming of their Robot if questioned by referees, inspectors, Event Partners, or judges. Teams should be prepared to describe their design process, justify design decisions, and demonstrate a full understanding of how their Robot and code function.

If a Team is unable, for any reason, to provide reasonable evidence (when requested by event staff) that their Robot and code are the result of their own work, it is appropriate to assume that the Team is in Violation of <G2> and/or <G4>.

Event organizers cannot reasonably know the origins of every design or independently verify whether a Robot was created from scratch, purchased online, or copied from pictures of another Team’s design. When questions of authenticity arise, the only direct and fair approach is to require Students to explain and defend their work. This is not unlike academic honesty concerns in schools, and intellectual property concerns in business. By requiring Students to defend their designs, we ensure that they are developing not only technical skills, but effective communication skills and accountability, as well.

Consequences may include disqualification from matches, removal from events, and/or escalation of the investigation to VEX Robotics and the RECF for further disciplinary action, which may include sanctions up to and including removal from the program.

Event staff should bear in mind <G3>, and use common sense when enforcing this rule. It is not the intent to actively hunt for Violations of this rule, compare every Robot at an event to all other known Robot designs, or closely question every team at an event about their Robot's code. This rule is a set of tools for use if potential Violations are noted by or reported to event staff, and it is expected that most Teams will never be required to defend their Robot design or code.

Teams or individuals who deliberately weaponize, manipulate, or falsely report <G4> Violations for competitive gain or to harass another Team may be subject to a separate RECF Code of Conduct investigation. Misuse of this rule is considered a serious Violation.




Significant Q&As:

• 2677 - Teams may only use custom parts that were designed and created by the Students on that Team
• 2823 - Excerpts from the Student-Centered Policy about code, templates, and libraries
• 2834 - Specific G4 scenarios and clarifications
• 2843 - Ownership of ideas when students legally change teams
• 2850 - Holecounting a design is not the same as being inspired by it



Violation Notes:

• Teams believed to be in Violation of this rule should be reported to the Judge Advisor, Head Referee, or Event Partner for further investigation in coordination with the RSM. Based on the investigation the Team may be removed from further Matches, have their Robot Skills Challenge scores removed, and/or be removed from consideration from judged awards.
• Violations of this rule will be evaluated on a case-by-case basis, in tandem with the RECF Student Centered Policy as noted in <G2>, and the REC Foundation Code of Conduct as noted in <G1>. All reported and/or suspected <G4> Violations should be reported to the Event Partner during the event, and should be reported to the RECF Rules and Conduct Committee following the event.

<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 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.

• Team members may only move from one Team to another for non-strategic reasons outside of the Team's control.
• Examples of permissible moves may include, but are not limited to, changing schools, conflicts within a Team, or combining/splitting Teams.
• 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.
• 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 Robots 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.
• 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.
• 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 Drive Team Members or Coders for the Team.
• 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 and Builders or notebookers. However, Teams can add permanent members throughout the season under the guidelines of this rule.

Violation Notes: Teams believed to be in Violation of this rule should be reported to the Judge Advisor, Head Referee, or Event Partner for further investigation in coordination with the RSM.

Event Partners should bear in mind <G3>, and use common sense when enforcing this rule. It is not the intent to punish a Team who may change Team members over the course of a season due to illness, changing schools, conflicts within a Team, etc.

Event Partners and referees are not expected to keep a roster of any Student who has ever been a Drive Team Member for one day. This rule is intended to block any instance of loaning or sharing Team members for the sole purpose of gaining a competitive advantage.

---

General Game Rules

<GG1> Only Drive Team Members, and only in the Alliance Station. During a Match, Robots may be operated only by the Drive Team Members and/or by software running on the Robot’s control system in accordance with <R11> and <GG11>. A Team may send up to three (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.

• 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 or a walkie talkie turned off) are allowed. If communication features are needed for translation apps during post-Match discussions, it should not be considered a Violation.
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 official accommodation request that has been approved by the REC Foundation.
3. Bringing/using additional materials to simplify the game challenge during a Match.
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, and/or passive earpieces connected to electronic devices cannot be worn/used in the Alliance Station except as required by an official accommodation request that has been approved by the REC Foundation.
• 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.

Violation Notes: Major Violations of this rule are not required to be Match Affecting, and could invoke Violations of other rules, such as <G1>, <G2>, or <G4>.

<GG2> A Team’s Robot should attend every Match. The Team’s Robot must report to 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> and the Code of Conduct. 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., batteries charged, sized within the starting size constraint, includes only the correct Alliance-color license plates, etc.).

1. Teams who use VEX pneumatics must have their systems charged before they place the Robot on the Field.
2. Robots must be placed on the Field promptly. Repeated failure to do so could result in a Violation of <G1>. The exact definition of the term “promptly” is at the discretion of the Head Referee and Event Partner, who will consider event schedule, previous Violations or delays, etc.
3. 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>).
4. 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.
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 C.
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. Drive Team Members are prohibited from making intentional contact with any Blocks, Field Elements, or Robots during a Match, apart from the contact specified in <GG4a> or while introducing Match Loads as described in rule <SG9>.

1. 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. 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.

Note: 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.

2. 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.
3. Transitive contact, such as contact with the Field Perimeter that causes the Field Perimeter to contact Field Elements or Blocks inside of the Field, could be considered a Violation of this rule.
4. Any concerns regarding Field Element or Block starting positions should be raised with the Head Referee prior to the Match. Team members may never adjust Blocks or Field Elements themselves.

<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. Field Elements 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 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.

• A Time Out can be ended early, but only if agreed to by both Alliances and the Head Referee.
• 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.

Violation Notes: Major Violations of this rule should be rare, as Robots should never be designed to intentionally violate it. Minor Violations are usually due to Robots being damaged during gameplay, such as a wheel falling off.

<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 Entangle 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 Violations should be recorded.

Violation Notes:

• If a Robot is reaching inside the open top portion of a Goal, it is that Team's responsibility to ensure that the Robot doesn't become Entangled with the Goal when approached by other Robots. <GG16> will not apply during related interactions, and a Robot that becomes Entangled while reaching into the open top of a Goal will receive a <GG9> Violation no matter how they became Entangled.

<GG10> The red Alliance places 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.

<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.

Violation Notes: The intent of this rule is to ensure that Robots abide by commands sent by the tournament software. Temporarily removing the cable to assist with mid-Match troubleshooting, with an Event Partner or other event technical staff present and assisting, would not be considered a Violation.

<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>.

Violation Notes: See <GG13>.

<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.

Violation Note: In general, Minor Violations of SG rules that occur during the Autonomous Period should only affect the outcome of the Autonomous Period (i.e., the Alliance can’t win the Autonomous Bonus or earn an Autonomous Win Point) and should not be considered when determining whether a Violation has been repeated during the event.

If a Head Referee determines that a Violation of an SG or GG rule during the Autonomous Period was intentional/strategic rather than accidental/situational, it should be recorded as a Minor or Major Violation and considered when determining whether a Violation has been repeated during the event.

<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 Push Back 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 Push Back 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 that drive around with a small wheel base. A Team should design its Robot such that it is not easily tipped over or damaged by minor contact.

Violation Notes:

• Major Violations of this rule are not required to be Match Affecting. Intentional and/or egregious tipping, Entanglement, or damage may be considered a Major Violation at the Head Referee’s discretion.
• Repeated Violations within a Match or tournament could be considered a Violation of <G1> and/or <S1> at the Head Referee’s discretion.

<GG15> Offensive Robots get the “benefit of the doubt” when judgement 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.

Violation Notes: In most cases, if a Team causes their opponent to break a rule, the Head Referee will simply not enforce the penalty on that opponent, and it will be considered a Minor Violation for the Team that was forced into a Violation. However, if the forced situation becomes Match Affecting in favor of the Team that forced the Violation, it will be considered a Major Violation for the Team that forced the Violation.

<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.

A 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.

<GG18> Use Blocks to play the game. Blocks 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 Block 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 Block to intentionally tip or Entangle an opponent Robot

Specific Game Rules

<SG1> Starting a Match. Prior to the start of each Match, the 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 Blocks other than a maximum of one (1) Preload. See rule <SG5>.
3. Not contacting any Goals or Loaders.
4. Not contacting any other Robots.
5. Completely stationary (i.e., no motors or other mechanisms in motion).
6. Contacting the barrier that defines their Alliance’s Park Zone.

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 <R5> and pass inspection without these influences.

Violation Notes: The Match will not begin with any conditions in this rule unmet. If a Robot cannot meet these conditions in a timely manner, the Robot will be removed from the Field and rules <R3d> and <GG2> will apply until the situation is corrected. They will not receive a Disqualification, but they will not be permitted to play in the Match.

Figure SG-1: An overhead view of the Field, with four Robots in legal starting positions.

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

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

Violation Notes:

• The primary intent of this rule is to limit Defensive horizontal expansion. As such, Robots that expand horizontally in the vicinity of multiple Goals may be subject to rule <GG15>, and will not receive the “benefit of the doubt” in the case of any Head Referee judgment calls.
• Incidental/insignificant infractions that occur during a Match are only considered Minor Violations. Repeated Minor Violations should only escalate to a Major Violation in extreme circumstances. Examples of Minor Violations include, but are not limited to:
  • Loose wires
  • Broken zip ties / rubber bands
  • Bent or broken mechanical components that are not used for strategic gain

<SG3> Vertical expansion is limited. Once the Match begins, Robots may expand vertically beyond the 18” starting size limit within the following criteria:

1. No part of the Robot may exceed an overall height of 22” at any point during the Match (must always be able to fit within a hypothetical 22”x22”x22” cubic sizing box).

<SG4> Keep Blocks in the Field. Teams may not remove Blocks from the Field. A Block that leaves the field during Match play, will be given to a Drive Team Member from the same color Alliance as the Block and may be used as a Match Load in accordance with <SG9>.

• If a Block 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 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.

Violation Notes:

• After a Team’s third Match with any Violation of this rule (either Major or Minor), all subsequent Violations of this rule will immediately escalate to a Major Violation.
• Any Team that removes three (3) or more Blocks from the Field in a single Match will receive a Major Violation.
• If it is not clear which Robot was the last to contact the Block, all involved Teams with a color that is opposite to the Block will receive a Violation.
• Due to the difficulty of determining Match Affecting implications of this rule, most Violations should be considered Minor. However, blatantly intentional and/or Match Affecting Violations (especially during Elimination Matches) may still immediately escalate to a Major Violation at the Head Referee’s discretion.

<SG5> Each Robot gets one Block as a Preload. 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 Robot as another Preload.
3. Not contacting or within the volume of a Goal or Loader.

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 <SG9>.

Violation Notes: See <SG1>.

<SG6> A Robot may carry, push, or plow an unlimited number of Blocks. However, horizontal and vertical expansion limits apply to all parts of the Robot for the entire duration of the Match. See rules <SG2> and <SG3>.

<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, Blocks, 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 Blocks 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. While some incidental contact or unintentional interactions may occur with Robots and/or Blocks 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.
3. Teams may interact with the portions of each Goal that are on their Alliance’s side of the Autonomous Line, but may not reach across to interact with the “open” portion of a Goal on their opponents’ side of the Field.
4. Blocks 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 eight Blocks that begin the Match in groups that cross the Autonomous Line are considered to be in contact with the Autonomous Line. See Figure SG-7.
5. Direct 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 either the Autonomous Line or objects that begin the Match positioned above or in contact with the Autonomous Line.
   2. Blocks on the other side of the Autonomous Line.
6. Causing a Block to contact an opponent Robot that is driving at the moment of contact is a Violation; intentional Violations may be subject to Major Violations and Disqualifications at the discretion of the Head Referee.
   
   
   1. Causing a Block to contact a stationary Robot is not considered a Violation unless the Head Referee determines it was a deliberate Defensive action.
   2. Blocks that move across the Autonomous Line through Goals are not subject to <SG7>.
   

   Figure SG-7: These Blocks (circled in red) would be considered to be in contact with the Autonomous Line.

   Violation Notes:

   • All Violations of this rule (Major or Minor) will result in the Autonomous Bonus being awarded to the opposing Alliance. See <SG8b> for a potential exception caused by Autonomous Line interactions and <SG7e> for specific examples that also award an automatic Autonomous Win Point.
   • Intentional, strategic, or egregious Violations, such as intentional contact with an opposing Robot while contacting the foam tiles on the opposing side of the Autonomous Line, will be considered Major Violations and should result in a Disqualification for the Match.
   • Deliberate Defensive Autonomous strategies, as described in clause <SG8a>, may also be recorded as <G1> Violations at the Head Referee’s discretion.

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

   
   

   Significant Q&As:

   • 2645 - Descoring Blocks from Goals during the Autonomous Period is not a Violation, regardless of what happens to those Blocks afterward
   • 2647 - Intentionally placing Blocks on the opponent’s side of the Autonomous Line is a Violation
   • 2924 - Scenarios and penalties for Robots and/or Blocks that cross the Autonomous Line
   
   
   

   <SG8> Engage with the Autonomous Line at your own risk. Any Robot who engages with Blocks 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.

   During the Autonomous Period, when Robots from opposing Alliances are both engaged with the same Block:

   1. If 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).
   2. Incidental Violations of <SG7> will not be penalized and will not automatically award the Autonomous Bonus to the opponent as described by <GG13>. However, this allowance only applies when opposing Robots are interacting with the same element.
   3. Intentional, strategic, repeated, or egregious offenses, such as negatively impacting Robots that are not engaging with the Autonomous Line, may still be deemed a Violation of <GG13>, <GG14>, <GG15>, <SG7>, <G1>, and / or <S1> at the Head Referee’s discretion.

   These gameplay elements are intended to be utilized by either Alliance 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.

   
   

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

   
   
   

   Violation Notes:

   1. For the purposes of Match Affecting calculations, each illegal Match Load should be considered worth a value of 3 points. These values are not added to the actual score. If subtracting 3 points per illegal Match Load from the the offending Alliance's final score would change the outcome of the Match, then the <SG9> Violation should be considered Match Affecting.
   2. For the purposes of this rule, the following guidelines should be used for escalating repeated Minor Violations to a Major Violation during Qualification Matches:
      
      
      1. Six or more illegal Match Loads in a single Qualification Match.
      2. Three or more Qualification Matches with at least one illegal Match Load (i.e., the third Match and all subsequent Matches with a Violation).
   3. For the purposes of this rule, only Match Affecting Violations should be considered during Elimination Matches (i.e., repeated Minor Violations in Elimination Matches do not compound to Major Violations).
      
      
      1. Point B-1 does not explicitly apply during Elimination Matches, although the risk of illegal Match Load becoming Match Affecting still inherently increases as the quantity of Match Loads increases.
      2. Point B-2 does not apply during Elimination Matches.

   <SG9> 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 Block into a Loader.

   During this action, a Drive Team Members' 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 Blocks by placing them into either of the Loaders adjacent to their Alliance Station.

   1. Blocks may only be added to Loaders during the Driver Controlled Period of a Match.
   2. A Match Load Block may not be contacted by a Robot prior to being placed into a Loader.
   3. Match Load Blocks may only be removed from a Loader by a Robot, and only through the bottom opening of the Loader.
   4. Blocks that incidentally bounce out through the bottom opening of a Loader while being introduced should not be considered Violations.
   5. A Block can only be added to a Loader if there are no Blocks partially or entirely within the orange portion of that Loader.

   Violation Notes:

   1. For the purposes of Match Affecting calculations, each illegal Match Load should be considered worth a value of 3 points. These values are not added to the actual score. If subtracting 3 points per illegal Match Load from the the offending Alliance's final score would change the outcome of the Match, then the <SG9> Violation should be considered Match Affecting.
   2. For the purposes of this rule, the following guidelines should be used for escalating repeated Minor Violations to a Major Violation during Qualification Matches:
      
      
      1. Six or more illegal Match Loads in a single Qualification Match.
      2. Three or more Qualification Matches with at least one illegal Match Load (i.e., the third Match and all subsequent Matches with a Violation).
   3. For the purposes of this rule, only Match Affecting Violations should be considered during Elimination Matches (i.e., repeated Minor Violations in Elimination Matches do not compound to Major Violations).
      
      
      1. Point B-1 does not explicitly apply during Elimination Matches, although the risk of illegal Match Load becoming Match Affecting still inherently increases as the quantity of Match Loads increases.
      2. Point B-2 does not apply during Elimination Matches.

   The primary intent of clauses A & E are to prevent Match Load Blocks from being introduced in a way that overfills the Loaders (e.g., Blocks extending well above the top of the Loader), thereby reducing potential <SG4> and <SG9> Violations resulting from Blocks being removed/ejected from the top of the Loader. If a Head Referee is not certain whether or not a Violation of clause E occurred, they should give the Team the benefit of the doubt and not record it as a Violation. This benefit of the doubt must be applied equally to all Teams and Matches at that event. We don't intend this to be a rule that requires referees to closely watch every Loader. If there's brief overlap in the orange portion of a Goal as Blocks are rapidly added to a Loader, it probably shouldn't be considered a Violation.

   
   
   

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

   

   Figure SC9-1: A Block is partially within the orange portion of the Loader, so it would not be legal to add a Block to this Loader.

   

   Figure SC9-2: There are no Blocks within the orange portion of the Loader, so it is legal to add a Block to this Loader.

   <SG10> Don’t reach inside enclosed sections of Goals, and no Goalkeeping. Robots are not permitted to directly contact Blocks that are fully within enclosed sections of Long Goals, but may add or remove Blocks from open sections of Goals at any time during a Match.

   A Robot can only reach into any open portion of a Goal to legally move Blocks (e.g., into or out of the Control Zone or the entire Goal). If a Head Referee sees a Robot that is Goalkeeping in the Driver Controlled Period of a Head-to-Head Match, that Robot should be verbally warned away and should receive an <SG10> Violation if it remains.

   • Reaching inside the open top portion of a Goal to affect Blocks within that Goal is an inherently Defensive position, and will not get the benefit of the doubt (<GG15>) if judgment calls are required.
   • If a Robot is reaching inside the open top portion of a Goal, it is that Team’s responsibility to ensure that the Robot doesn’t become Entangled with the Goal when approached by other Robots. <GG16> will not apply during related interactions, and a Robot that becomes Entangled while reaching into the open top of a Goal will receive a <GG9> Violation no matter how they became Entangled.

   Violation Note: An <SG10> Violation should be considered Match Affecting if the Team responsible ties or wins the Match by 10 points or less.

   

   Figure SG10-1: A diagram showing the portion at the end of the Goal (highlighted in green) that may pertain to Goalkeeping.

   
   

   Significant Q&As:

   • 2826 - Goalkeeping scenarios, including what should happen if two Goalkeeping Robots are pushing against each other
   • 2837 - Clarifications on “inside a goal”
   • 2845 - More clarification on “inside a goal”
   • 2859 - One a Robot is outside of the Goal, they’re no longer Goalkeeping
   • 2864 - Defensive actions around a Goal might be misinterpreted as Goalkeeping
   • 2923 - If a Head Ref isn’t confident about a possible Violation for reaching into the closed part of a Goal, and it didn’t affect Blocks, they can probably ignore it
   
   

   <SG11> Park Zones are protected during the endgame. During the last 20 seconds of a Match, Robots may not directly or indirectly contact the other Alliance’s Park Zone or opponent Robots that are partially or entirely within the vertical projection of that Park Zone.

   Violation Notes: Intentional, strategic, egregious, or Match Affecting Violations will be considered Major Violations.

   Significant Q&As:

   • 2751 - Examples of Violations through indirect contact
   • 2786 - Guidelines for calculating whether a Violation is Match Affecting
   • 2811 - Example scenarios with suggested rulings
   • 2882 - Clarifications on intentional and Match Affecting Violations
   
   
   

   ---

Inspection Rules

<R1> One Robot per Team. Each Team can only bring one (1) 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 (1) Robot at a given event, and a given Robot may only be used by one (1) 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: Subsystem 3: Additional mechanisms (and associated motors) that allow manipulation of Blocks 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 Skills Challenges) must consist of subsystems 1 and 2 above. Thus, if you are swapping out an entire subsystem 1 or 2, you have now created a second Robot and have Violated 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.

<R2> Robots must represent the Team’s skill level. The Robot must be designed, built, and programmed by members of the Team. Adults are expected to mentor and teach design, building, and programming skills to the Students on the Team, but Adults may not design, build, or program that Team’s Robot. See rules <G2>, <G4>, and <G5>.

<R3> 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. Initial inspections will take place during Team registration/practice time. 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 <R5>).
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 may be in Violation of one or more Robot rules) will not be permitted to play in any Matches until they have done so. <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.
8. Event staff and volunteers are allowed to photograph Robots during inspection and/or at other times as needed.

<R4> 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 <R3d>).

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. Any Violation of this sort should be considered a Violation of <G1> and/or the REC Foundation Code of Conduct. A Team that circumvents a Robot rule for a competitive advantage should receive an immediate Disqualification for the current Match and be reported to the Event Partner for discussion with the REC Foundation Regional Support Manager. As a result of that discussion, the Team may be Disqualified from the event. The Violation should also be reported to the REC Foundation Rules and Conduct Committee following the event.

<R5> 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.

<R6> 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 RobotEvents.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 only 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 attached to the Robot using materials that are legal for Robot construction. VEX IQ pins are no longer 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.
7. Custom license plates used to meet the requirements of <R6a> and <R6f> 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)

Figure R6-1: An example of a license plate made from the V5RC License Plate Kit.

Figure R6-1: An example of a legal custom license plate

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

<R8> 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.

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, or VEX Robotics by HEXBUG. This also includes devices that are unrelated to VEX, such as Raspberry Pi or Arduino devices.

• 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.

<R9> Keep the power button 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 must be easily visible during Robot inspection. Keeping the V5 Brain screen visible throughout a Match is recommended but not required.

<R10> 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 two week (14 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.

<R11> 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.

<R12> Motors are limited. Robots may use any combination of VEX V5 Smart Motors (11W) (276-4840) and Smart Motors (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 and EXP 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.

<R13> 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 <R24e>.
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.

<R14> Robots use VEXnet. Robots must ONLY utilize the VEXnet system 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 <R17>.
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.

<R15> Give the radio some space. The V5 Radio must be mounted such that no metal surrounds the radio symbol on the V5 Radio.

<R16> 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.

<R17> 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. Product pages on the VEX Robotics website should be used as the official definitive source for determining if a product is a “V5 component.”

1. Products from other VEX Robotics product lines that are specifically allowed by a clause of <R20> or “cross-listed” as part of the VEX V5 Product lines are legal for use in the VEX V5 Robotics Competition. For example, Flex Wheels and VersaHubs are VEXpro components that can be found on the VEX “Flex Wheels” page, and specific sizes are thus legal.
2. The following electronics from the VEX Cortex control system are permitted.

3. Legacy/discontinued products are only permitted if they are explicitly listed in this game manual, or still listed as V5RC or VRC legal on the VEX Robotics website: https://www.vexrobotics.com/v5-discontinued.html. Any questions or concerns about discontinued parts should be directed to the official Q&A System on RobotEvents.com.

<R18> 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 on their respective product web pages.

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

1. Those that could potentially damage Field Elements or Blocks.
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, or VEX Robotics by HEXBUG* product lines, unless specifically allowed by a clause of <R17> or “cross-listed” as part of the VEX V5 Product lines (see <R17a>).

* The HEXBUG brand is a registered trademark belonging to Spin Master Corp

6. The following electronics from the VEX Cortex control system.

SKU	Description
276-2192	VEXnet Joystick
276-1891	VEXnet Partner Joystick
276-2194	VEX ARM® Cortex-based Microcontroller
276-2245 / 276-3245	VEXnet Key 1.0 / 2.0
276-2177	2-Wire Motor 393
276-2162	3-Wire Servo
276-2210	VEX Flashlight
276-2193	Motor Controller 29

7. Components that are unique to the V5 Workcell product line. This includes the following.

SKU	Description
276-7151	Robot Arm Metal
276-7152	Robot Brain Mount
276-7153	Input Output Conveyor
276-7720	Disc Feeder
276-7047	V5 Electromagnet

8. Components obtained from the V5 beta program, including V5 beta firmware.
   
   
   1. 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.
9. Components from the VEXplorer kit that are not found in modern VEX V5 kits. These include (but may not be limited to) electronics, wheels, non-standard gears, and plastic connectors.
10. Standalone VEX Smart Field Controller Brains (SKU 276-7577).
11. VEX apparel, competition support materials, packaging, or other non-Robot products.
12. 3D printed Robot parts for any purpose, including non-functional decorations and license plates.
13. Speakers and other audio devices that create sound are not permitted.

<R20> Certain non-VEX components are allowed. Robots are allowed the following additional “non-VEX” components:

1. Any material strictly used as a color filter or a color marker for a legal sensor, such as the VEX Light Sensor or the VEX V5 Vision Sensor.
2. 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, Blocks, or other Robots. Grease or lubricant applied directly to V5 Smart Motors or Smart Motor cartridges is prohibited.
3. Anti-static compound, when used in extreme moderation (i.e., such that it does not leave residue on Field Elements, Blocks, or other Robots).
4. Hot glue when used to secure cable connections.
5. An unlimited amount of rope/string, no thicker than 1/4” (6.35mm).
6. 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.
7. Rubber bands that are identical in length and thickness to those included in the VEX V5 product line (#32, #64, #170, and #117B).
8. Pneumatic components with identical SMC manufacturer part numbers to those listed on the VEX website. For more detail regarding legal pneumatic components, see the Legal VEX Pneumatics Summary document.
9. Zip ties with identical dimensions as those included in the VEX V5 product line, or their metric equivalents. Specific zip tie dimensions listed on the VEX Robotics website are nominal references to hardware sizes found within the VEX V5 product line and/or their metric equivalents. The designated size of the product may differ slightly from the actual measurement.
10. A Micro SD card installed in the V5 Robot Brain.
11. 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.
12. Cleaners, disinfectants, and/or sanitizers may be used to assist in cleaning Robots, parts, components, etc. VEX Robotics recommends the following procedures for cleaning/disinfecting/sanitizing robot parts.
13. See rules <R21> through <R25> for additional legal non-VEX components.

<R21> 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.

<R22> 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 and motors.
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 “non-functional decoration” per <R24>.
5. As an aglet at the end of rope/string to prevent fraying.

<R23> 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, standoff, and/or non-threaded spacer up to 2.5” (63.5mm) long which fits these screws.

<R24> 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,” any guards, decals, or other decorations must be backed by legal materials that provide the same functionality. For example, if a Robot has a giant decal that prevents Blocks from falling out of the Robot, the decal must be backed by VEX material that would also prevent the Blocks 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 and painting of parts is considered a legal nonfunctional decoration.
   

Note: As of October 1, 2024, anodizing or color changing of parts (such as painting, etc., which changes the original appearance of parts) is no longer allowed in events in mainland China.

2. Small cameras are permitted as non-functional decorations, provided that any transmitting functions or wireless communications are disabled. Unusually large cameras being 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 Blocks, or that could otherwise interfere with an opponent’s Vision Sensor, are considered functional and are not permitted. The Inspector and Head Referee will make the final decision on whether a given decoration or mechanism violates this rule.
5. Internal power sources (e.g., for a small blinking light) are permitted, provided that no other rules are violated and this source only provides power to the non-functional decoration (i.e., does not directly or indirectly influence any functional portions of the Robot).
6. Decorations which provide feedback to the Robot (e.g., by influencing legal sensors) would be considered “functional,” and are not permitted.
7. Decorations which provide visual feedback to Drive Team Members (e.g., decorative lighting) are permitted, provided that they do not violate any other rules and serve no other function (e.g., structural support).

<R25> 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” 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 or 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, or cast. 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 are considered “plastic” in the context of this rule, and are subject to the same limitations as “off-the-shelf” plastic sheets. Examples include the 276-8340 PET sheets, and the 217-6626 / 217-6627 polycarbonate sheets.
8. This rule does not apply to 3D printed plastic parts. 3D printed 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.

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

1. Teams may use a maximum of two (2) legal VEX pneumatic air reservoirs on a Robot. The Air Tank 200mL (included in the 276-8750 V5 Pneumatics Kit) and the legacy (pre-2023) reservoir are both considered legal reservoirs.
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).
   

Note: From a rules perspective, parts found in the V5 Pneumatics Kit (276-8750) and legacy (pre-2023) pneumatic parts may be used interchangeably. A Legal Pneumatics summary can be found in the VEX Library, which includes additional pneumatics information.

<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. Internal or external mechanical repairs of VEX Limit and Bumper switches are permitted.
   
   
   1. Modifying the metal arm on the Limit Switch is permitted.
   2. Using components from these devices in other applications is prohibited.
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 <R20e>) 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 <R20d> 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.

<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.

• 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 <R20>.
  
  
  • Replacing the gear cartridge with other official cartridges.
  • Removing or replacing the screws from the V5 Smart Motor Cap (276-6780).
  • Removing or replacing the threaded mounting inserts (276-6781).
  • Aesthetic/non-functional labeling (e.g., markers, stickers, paint, etc.).
• 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
• For the purposes of this rule, the V5 Smart Motor Cap is not considered “part of the motor.” Therefore, <R27> applies.
• 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.
• Wire used in repairs must be identical to VEX wire.
• Teams make these repairs at their own risk; incorrect wiring may have undesired results.
• 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.

Robot Skills Challenge Definitions

All definitions from previous sections of the manual apply to the Robot Skills Challenge, unless otherwise specified.

Driving Skills Match - A Driving Skills Match consists of a sixty-second (one minute) Driver Controlled Period. There is no Autonomous Period. Teams can elect to end their run early if they wish to record a Skills Stop Time.

Autonomous Coding Skills Match - An Autonomous Coding Skills Match consists of a sixty-second )(one minute) Autonomous Period. There is no Driver Controlled Period. Teams can elect to end their run early if they wish to record a Skills Stop Time.

Robot Skills Match - A Driving Skills Match or Autonomous Coding Skills Match.

Skills Stop Time - The time remaining in a Robot Skills Match when a Team ends the Match early.

1. If a Team does not end the Match early, they receive a default Skills Stop Time of 0.
2. The moment when the Match ends early is defined as the moment when the Robot is “Disabled” by the field control system. See the “Skills Stop Time” section for more details.
3. If a V5 Robot Brain or Tournament Manager display is being used for field control, then the Skills Stop Time is the time shown on the display when the Match is ended early (i.e., in 1-second increments).
4. If a VEXnet Competition Switch is being used for field control, in conjunction with a manual timer that counts down to 0 with greater accuracy than 1-second increments, then 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.

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 Blocks from the Field in a Robot Skills Match is not a Violation. Blocks that leave the Field cannot be returned.

Violation Note:

• 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.
• 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> Scoring Robot Skills Matches. For each Robot Skills Match, Teams are awarded a score based on the following rules and scoring table:

1. Teams will receive points for all Scored Blocks, regardless of color.
1. A Block is not considered Scored if it is in contact with a Robot at the end of the Match.
2. A Control Zone is considered filled if it ends the Match containing its maximum number of Scored Blocks, and if all Blocks in that Control Zone are the same color (e.g., all are blue, or all are red).
   
   
   1. In a Robot Skills Match, a Center Goal Control Zone must contain at least seven (7) Blocks to be considered filled.
   2. A Long Goal must include one or more of the following to be considered filled in a Robot Skills Match:
      
      
      1. Three Blocks of the same color fully contained between the inner edges of the Control Zone tape lines.
      2. Four Blocks of the same color fully contained between the outer edges of the Control Zone tape lines.
3. The Team will earn points for a cleared Park Zone if no Blocks are in contact with the Floor inside the Park Zone at the end of the Match.
4. The Team will earn points for a cleared Loader if no Blocks are within that Loader at the end of the Match.
5. The Team will earn points for a Parked Robot if the Robot has moved during the Match, is within the red Alliance Park Zone, and meets all criteria of rule <SC4> at the end of the Match.

<RSC3> Robot and Field setup for Skills Matches. The Robot and Field are set up the same as for a Head-to-Head Match (e.g., the Robot must meet the requirements of <SG1>), with the following modifications:

1. In Autonomous Coding Skills Matches, the VEX GPS code strip must be installed on the Field.
2. The Robot must start the Robot Skills Match in a legal starting position for the red Alliance.
3. All Drive Team Members must remain in the red Alliance Station for the duration of the Match.
4. One red Block must be used as a Preload in accordance with <SG5>.
5. Revised Block layout. 36 Blocks begin the Match in unscored positions on the Field and 24 Blocks begin in the Loaders, as shown in Figure RSC3-1.
6. Robots may move freely about the Field after the start of the Match.
7. Robot Skills Matches do not include Match Load Blocks.

Figure RSC3-1: The field layout for a V5RC Push Back Robot Skills Match.

Figure RSC3-2: An overhead view of a V5RC Push Back Robot Skills Match in its starting configuration, with highlighted Blocks (red / Blue).

<RSC4> 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.

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.
   
   
   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.
   
   
   1. As noted in the definition of Skills Stop Time, the moment when the Match ends early is defined as the moment when the Robot is “Disabled” by the field control system.
   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 may not 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 “Drive” program accessed from a V5 Controller is intended for practice only, and may not 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.

Tournament Definitions

Alliance Captain - One of the Teams with the privilege of inviting another available Team to form an Alliance for the Elimination Matches. See <T16>.

Alliance Selection - The process of choosing the permanent Alliances for the Elimination Matches. Alliance Selection proceeds as follows:

1. The highest-ranked Team at the end of Qualification Matches becomes the first Alliance Captain.
2. The Alliance Captain invites another Team to join their Alliance.
3. The invited Team representative either accepts or declines as outlined in <T16>.
4. The next-highest-ranked Team becomes the next Alliance Captain.
5. Alliance Captains continue to select their Alliances in this order until all Alliances are formed for the Elimination Matches.

Autonomous Points (AP) - The second basis of ranking Teams. An Alliance who wins the Autonomous Bonus during a Qualification Match earns ten (10) Autonomous Points. In the event of a tie, both Alliances will receive five (5) Autonomous Points.

Bye - A situation in which an Alliance automatically advances to the next round of tournament play without competing.

Elimination Bracket - A schedule of Elimination Matches for eight (8) to sixteen (16) Alliances. See <T17>.

Elimination Match - A Match used in the process of determining the champion Alliance. Alliances of two (2) Teams face off according to the Elimination Bracket; the winning Alliance moves on to the next round.

Event Partner - The volunteer VEX V5 Robotics Competition tournament coordinator who serves as an overall manager for the volunteers, venue, event materials, and all other event considerations. Event Partners serve as the official liaison between the REC Foundation, the event volunteers, and event attendees.

Head Referee - A certified impartial volunteer responsible for enforcing the rules in this manual as written. Head Referees are the only individuals who may discuss ruling interpretations or scoring questions with Teams at an event. Large events (e.g., Signature Events, World Championships, etc.) might include multiple Head Referees at the Event Partner’s discretion.

Match Schedule - A list of Matches that is generated at the start of an event. The Match Schedule includes the predetermined, randomly-paired Alliances that will be competing in each Qualification Match, and the expected start times for these Matches. The Match Schedule may be subject to change at the Event Partner’s discretion.

Figure MS-1:An example of a Qualification Match Schedule

Practice Match - A Match used to provide time for Teams and volunteers to get acquainted with the official playing Field and procedures. Practice Matches earn Teams zero (0) Win Points, Autonomous Points, and Strength of Schedule Points. Head Referees should not record or track standard gameplay Violations that occur during Practice Matches. Violations that are egregious, unsportsmanlike and/or unsafe may be recorded and tracked at the discretion of the Head Referee.

Qualification Match - A Match used to determine Team rankings for Alliance Selection. Each Qualification Match consists of two Alliances competing to earn Win Points, Autonomous Points, and Strength of Schedule Points.

Scorekeeper Referee - An impartial volunteer responsible for tallying scores at the end of a Match. Scorekeeper Referees do not make ruling interpretations, and should redirect any Team questions regarding rules or scores to a Head Referee.

Strength of Schedule Points (SP) - The third basis of ranking Teams. Strength of Schedule Points are equivalent to the score of the losing Alliance in a Qualification Match. In the event of a tie, both Alliances receive Strength of Schedule Points equal to the tie score. If both Teams on an Alliance are Disqualified, the Teams on the not Disqualified Alliance will receive their own score as Strength of Schedule Points for that Match.

Win Points (WP) - The first basis of ranking Teams. Teams will receive zero (0), one (1), two (2), or three (3) Win Points for each Qualification Match. Unless a Team is Disqualified, both Teams on an Alliance always earn the same number of Win Points.

• One (1) Win Point is awarded for completing the Autonomous Win Point task(s).
• Two (2) Win Points are awarded for winning a Qualification Match.
• One (1) Win Point is awarded for tying a Qualification Match.
• Zero (0) Win Points are awarded for losing a Qualification Match.

Win Percentage (WP) - Replaces Win Points in a league event. Win Percentage is calculated by the number of wins divided by the number of Qualification Matches the Team plays. In cases of a tie, the Team is given a 0.5 number of “wins” for that Match. The Autonomous Win Point is also considered 0.5 “wins,” added to the total number of wins.

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. CoC-related Violations require additional escalation beyond the Head Referee’s initial ruling, including (but not limited to) investigation by RECF representatives.
4. Event Partners may not overrule a Head Referee’s gameplay or Robot decisions.
5. Every Qualification Match and Elimination Match must be watched by a certified Head Referee. Head Referees 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.
6. 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 an REC Foundation Certified V5RC Head Referee for the current season. Visit the REC Library for more details.
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 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>).

1. Referees are not permitted to review any photo or video Match recordings when determining a score or ruling.
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 VEX V5 Robotics Competitions, 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> and/or the Code of Conduct.

<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 Push Back; 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

<T5> Be prepared for minor Field variance. Field Element tolerances and Blocks 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. Block placement at the beginning of the Match may vary from nominal by up to ±1” (25.4mm). If a Block is within tolerance, either on the Field or within a Loader, it should not be adjusted before the Match.
3. Goal Heights may vary from nominal by up to ±1” (25.4mm).
4. Block weight may vary by up to ± 4g
5. The rotation of Blocks is not specified. If a Block is within tolerance, either on the Field or within a Loader, it should not be adjusted before the Match.
6. Placement of Control Zone tape lines on the Long Goals may vary from nominal by up to ± 0.25".

<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 white electrical tape to add required lines to the Field
• Using standard VEX Field tiles in place of the game-specific graphics tiles, for any reason
• Assembling Loaders without nut blocks to improve alignment of holes
• Anchoring Field Elements directly to Field risers instead of the metal plates
• Anchoring the metal plates to the underlying surface with hardware or tape

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. 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/applicable 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

Note: If an event has dedicated Fields for Skills Challenge 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 found in the REC Library.

Note 2: Add-ons that abide by the TM Public API guidelines are permitted. Once add-ons are enabled, the software is no longer supported by the REC Foundation, 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. The Match Schedule is subject to change at the Event Partner’s discretion.

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 the REC Foundation RSM prior to the event, and divisions must be assigned in sequential order by Team number.

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

1. When in a tournament, the tournament must have a minimum of six (6) Qualification Matches per Team. The suggested number of Qualification Matches per Team for a standard tournament is eight (8) and up to ten (10) for a championship event.
2. When in a league, there must be at least three (3) league ranking sessions, with at least one (1) week between sessions. Each session must have a minimum of two (2) Qualification Matches per Team. The suggested number of Qualification Matches per Team for a standard league ranking session is four (4). Leagues will have a championship session where elimination rounds will be played. Event Partners may 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. When in a league, every Team will be ranked based on the number of Matches played. Teams that participate 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.
3. 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 the location’s RECF Regional Support Manager:

<T15> Send a Student representative to Alliance Selection. Each Team must send one (1) 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.

<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 ABC to join their Alliance.
• Team ABC declines the invitation.
• No other Alliance Captains may invite Team ABC to join their Alliance.
• However, Team ABC may still form their own Alliance if Team ABC 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:

Figure T17-1: A 16-Alliance bracket

Figure T17-2: An 8-Alliance bracket

<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.

Figure T18-1: The process for determining how Elimination Matches should be played.

<T19> Ties in Elimination Matches lead to limited rematches. In the case of tied Matches during Elimination Rounds, 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.

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.

Details regarding logistics of Skills-Only Events can be found in the REC Foundation Qualifying Criteria document.

1. Robot Skills Matches are only available to Teams who participate in Qualification Matches, unless the event is an approved Skills-Only Event or in cases where a VURC or VAIRC team records skills scores in accordance with this REC Library article. Teams who participate in Qualification Matches during a specific League Ranking Session are the only Teams who can participate in Robot Skills Matches at that session.
2. Skills scores recorded by ineligible Teams will be deleted from Tournament Manager before the event is finalized on RobotEvents.com.

<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 <RSC4>) 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. Points earned for filled Control Zones.
   2. Number of Blocks Scored in Goals.
   3. Points earned for Parking
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 RobotEvents.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 <RSC4>) 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.
   
   
   1. 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.
   
   
   1. 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 150 for this event, and their scores from Session 2 would be used for the Event and Global tiebreakers listed in <T22> and <T23>.

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.

Neutral Zone - An area of the Field defined by and including white tape lines, which encompasses the Center Goals and their surrounding space. See VURS-1.

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>.

Game, Robot, and Tournament Rules

The VEX U Robotics Competition uses the VEX V5 Robotics Competition Push Back Field with some minor modifications. Anyone that has a V5RC Push Back 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 document. 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.

Rule Modifications: Field Setup

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

• The VEX GPS code strip must be installed on the Field
• Modified Field layout
• Modified tape lines

Figure VURS-1: The starting Field configuration for VEX U Matches, with the Neutral Zone highlighted green.

Figure VURS-2: The starting Field configuration for VEX U Matches, with Blocks highlighted (Red / Blue).

Rule Modifications: Game

<VUG1> 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.

<VUG2> Different expansion. The designated 24” Robot may expand horizontally and/or vertically up to a maximum size of 24" x 24" x 24" at any time during the Match.

<VUG3> Different availability of Loaders. Drive Team Members may add Match Load Blocks to the Loaders adjacent to their Alliance Station during the Autonomous Period and Driver Controlled Period of the Match.

<VUG4> Different Autonomous Win Point criteria. An Autonomous Win Point is awarded to any VEX U Team that ends the Autonomous Period with all of the following tasks completed:

1. At least 12 Blocks of the Alliance’s color are Scored.
2. At least three (3) different Goals include at least one (1) Scored Block of the Alliance’s color.
3. The six (6) Blocks of the Alliance’s color that begin the Match in the Loaders adjacent to their Alliance Station have been removed.
4. At least one Robot is Parked in the Park Zone.
   

<VUG5> Don’t cross the Autonomous Line, and don’t interfere with your opponents’ actions. In VEX U Matches, <SG7> applies to foam tiles, Blocks, Field Elements, and interactions on the opposing Alliance’s side of the Autonomous Line and on the opponent’s side of the Field beyond the Neutral Zone. Interactions outside of the Neutral Zone should still be primarily Offensive, and must meet the guidelines and limitations in rule <SG7>.

1. Blocks that begin the Match in contact with the Autonomous Line or within the Neutral Zone are not considered to be on either side, and may be utilized by either Alliance during the Autonomous Period.

<VUG6> Engage with the Autonomous Line and Neutral Zone at your own risk. This rule replaces the first paragraph of <SG8>. Any Robot that engages with Blocks or Goals that begin the Match or are located on the Autonomous Line or within the Neutral Zone should be aware that opponent Robots may also choose to do the same.

Robots entering the Neutral Zone should expect contact with other Robots, and should take this into consideration when designing and building. However, Rule <GG14> still applies within the Neutral Zone, and Teams can receive a Disablement or Major Violation for actions that a Head Referee deems intentionally damaging or egregious.

<VUG7> 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 game pieces and/or other Robots.

Rule Modifications: Robot Skills Challenge

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

<VURS1> VEX U Robot Skills Matches use the same Field layout, object placements, and tape lines as VEX U Head-to-Head Matches.

1. If a VURC Team runs Robot Skills Matches at a V5RC event, they may choose from the following options:
   
   
   1. Choose to run their Matches on a Field with the V5RC tape lines.
   2. Work with the Event Partner to replace the tape lines on a Skills Field to match the VURC tape layout. This option may not be available at all events, and the VURC Team should communicate with the Event Partner in advance to discuss options. The VURC Team might need to provide their own tape.

<VURS2> Both Robots must start the Robot Skills Match in legal starting positions for the red Alliance. All other portions of rule <SG1> apply.

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

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.

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.

<VUT7> VURC tournaments have fewer Teams in Eliminations. The number of Teams in Eliminations for a given event is determined as follows, except in extraordinary circumstances with the permission of the RECF Regional Support Manager. A number of Teams below 16 will result in one or more Byes for highest-ranking Teams.

Rule Modifications: Robot

<VUR1> Teams may use two (2) Robots in each Match.

1. Both Robots may only be built from the following materials:
   
   
   1. Official VEX Robotics products (see <VUR2>)
   2. Fabricated Parts made by the Team (see <VUR3> through <VUR7>)
   3. Commercially-available springs, fasteners, and bearings (see <VUR8>, <VUR9>, and <VUR15>)
   4. A legal electronics system (see <VUR10> and <VUR11>)
   5. Any legal Additional Electronics (see <VUR12>)
   6. A legal pneumatics system (see <VUR14>)
   7. Unmodified legal Raw Stock (see <VUR4> and <VUR5>)
2. One Robot must be no larger than 24” (609.6 mm) x 24” (609.6 mm) x 24” (609.6 mm) at the start of the Match.
3. One Robot must be no larger than 15” (381 mm) x 15” (381 mm) x 15” (381 mm) at the start of the Match.

<VUR2> Teams may use any official VEX Robotics products, other than the exceptions listed in the tables below, to construct their Robot. This includes those from the VEXpro, VEX EXP, VEX IQ, VEX GO, VEX 123, VEX CTE, and VEX Robotics by HEXBUG* product lines. Rule <R28> applies, but most modifications to non-electrical components are allowed.

This rule takes precedence over all other rules regarding Raw Stock and/or Fabricated Parts, such as <VUR5>.

<VUR3> Fabricated Parts may be made by applying the following manufacturing processes to legal Raw Stock:

1. Additive manufacturing processes, such as 3D printing.
2. Subtractive manufacturing processes, such as cutting, drilling, routing, or machining.
3. Bending, such as sheet metal braking or thermoforming.
4. Attaching materials to one another, such as welding or chemically bonding (e.g., epoxy).
5. Molding of non-metals, such as injecting polyurethane into a 3D printed mold.

<VUR4> Fabricated Parts must be made from legal Raw Stock. To be considered Raw Stock, the material must be obtained in one of the following forms before undergoing the fabrication processes listed in <VUR3>:

<VUR5> The following material types are not considered Raw Stock, and are therefore not permitted:

Note: <VUR2> takes precedence over this rule. Materials purchased from VEX Robotics that fall under one of these categories (e.g., VersaFrame pre-drilled extrusion) are permitted.

<VUR6> Fabricated Parts cannot be made from Raw Stock which poses a safety or damage risk to the event, other Teams, or Field Elements. Examples of prohibited materials include, but are not limited to:

1. Any material intended to produce flames or pyrotechnic effects.
2. Any material that is liquid at the time of the Match. Examples include hydraulic fluids, oils, greases, liquid mercury, and tire sealant.
   
   
   1. This does not include fabrication processes that involve the use of liquids, such as milling coolant or epoxy.
3. Any matter that shatters or otherwise presents an excessive Field/safety hazard upon failure. Examples include fiberglass, acrylic, and carbon fiber sheet/tube stock.
   
   
   1. This rule refers specifically to material legality itself. Any potentially unsafe mechanisms made from legal Raw Stock may still be addressed by <S1> and <R19>.
   2. 3D printer filaments that include carbon fiber (or similar) additives or carbon fiber (or similar) inlay are exempt from this exception, and are considered legal for use in Fabricated Parts.

<VUR7> Fabricated Parts must be made by Team members. Any Fabricated Parts must be accompanied by documentation that demonstrates the Team’s design and construction process for that Fabricated Part.

1. The minimum acceptable form of documentation is an engineering drawing with multiple views for the part in question. These drawings may be included in a Team’s Engineering Notebook or in a standalone appendix to the Engineering Notebook.
2. Any Fabricated Part must have been entirely designed and produced by Team members. For example, parts ordered by the Team and 3D printed by a third party would be prohibited.
3. Teams will be required to provide this documentation as requested by inspectors, Head Referees, or judges at any time at an event. Failure to provide acceptable documentation will result in the part being deemed illegal for use; therefore, <R3>, <R4>, and/or <G1> will apply.

<VUR8> Teams may use commercially-available springs on their Robots. For the purposes of this rule, a “spring” is any device used for storing and releasing elastic potential energy. Examples include, but are not limited to:

1. Compression, tension, torsion, constant force, or conical springs made from spring steel.
2. Springs made from elastic thread or rubber, such as surgical tubing, bungee cords, or stretchable braided rope.
3. Closed-loop (pneumatic) gas shocks.

Note: Gas shocks are not considered pneumatic devices in the context of <VUR14>. Gas shocks may not be modified in any way.

<VUR9> Teams may use commercially available fastener hardware on their Robot. Examples include (but are not limited to):

• Screws, nuts, rivets, and heatset inserts.
• Hinges, pins, rod ends, threaded rods, and hose clamps.
• Ancillary fastener accessories, such as washers or spacers.
• Adhesives such as epoxy, glue, or tape (only when used to join together two parts).

If the primary function of the part is not “fastening”, then <VUR5>, <VUR6>, and/or <VUR7> take precedence over this rule. Illegal examples include (but are not limited to):

• A prefabricated non-VEX wheel, even though it may technically connect tread to a shaft
• 80/20 extrusion; other items get “fastened to it”, it is not the part doing the “fastening”
• Using grip tape to improve wheel traction
  
  

<VUR10> Each Robot must utilize exactly one (1) V5 Robot Brain and at least one (1) V5 Robot Radio connected to a V5 Controller.

1. Teams must abide by the power rules noted in <R13> and <VUR12d>.
2. Wireless communication between Robots is permitted if using legal V5 Robot Brains and V5 Robot Radios. No other types of wireless communication protocols (e.g., radio, Bluetooth, Wi-Fi) are permitted.

<VUR11> There is no restriction on the number of V5 Smart Motors (11W) [276-4840] and/or Smart Motors (5.5W) [276-4842] that Robots may use. No other motors, servos, or electronic actuators are permitted, including those sold by VEX (e.g., the 2-Wire 393 Motor).

Note 1: Rule <R28> still applies in VEX U. Teams may not modify Smart Motors, and must use official/unmodified gear cartridges.

Note 2: Commercially available pneumatic actuators and pneumatic solenoids are permitted within the guidelines of <VUR14>.

Note 3: Legal Additional Electronics may include their own motor, servo, or actuator, per <VUR12>.

<VUR12> There is no restriction on commercially available Sensors, External Processors, or Additional Electronics that Robots may use for sensing and processing, except as follows:

1. Sensors and External Processors MUST be connected to the V5 Robot Brain via any of the externally accessible ports (i.e., without any modification to the commercially available electronics). A Sensor may be connected to an External Processor which then connects to the V5 Robot Brain.
2. Sensors, External Processors, and Additional Electronics CANNOT directly electrically interface with VEX motors and / or solenoid.
3. Sensors and Additional Electronics may only receive power from any of the following:
   
   
   1. Directly from the V5 Robot Brain via any externally accessible port.
   2. From an additional lithium ion, lithium iron, or nickel metal hydride battery pack (only one (1) additional battery can be used for Sensor/processing power). This additional battery pack must operate at a maximum of 12 volts nominal.
   3. Directly from an External Processor
4. Only the V5 Battery can power the V5 Brain.
5. Sensors, External Processors, and/or Additional Electronics which include a low-powered motor as an integral part of their primary sensing/processing function, such as an External Processor’s cooling fan or a spinning Sensor, are permissible.
   
   
   1. Standalone motors which serve no additional sensing or processing functionality (e.g., using a commercially-available brushless motor in a drivetrain) are not considered legal Additional Electronics, and would be considered a Violation of <VUR11>.
6. Pneumatic solenoids are the only types of solenoids that are permitted as Additional Electronics. Solenoids used for any purpose other than opening and closing a pneumatic valve are considered an actuator and therefore prohibited, per <VUR11>.
7. <R28> still applies in VEX U, Teams may not alter or modify electronic parts from the VEX product lines.