The Game

VEX V5 Robotics Competition Override: A Primer

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

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

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

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

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

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

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

Field Overview

The VEX V5 Override Field consists of the following:

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

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

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

Figure FO-1: An overhead view of the VEX V5 Override Field, with Alliance Stations (orange), Loaders (white), Toggles (pink), and Goals (green) highlighted.

Figure FO-2: An overhead view of the VEX V5 Override Field in its starting configuration, with icons representing orientation of Scoring Objects.

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

Game Design Philosophy - A Letter from the GDC

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

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

What This Game is About & Scoring

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

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

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

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

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

• Building stacks
• Flipping Toggles
• Positioning your Robot effectively

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

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

Large Point Swings with Toggles and Yellow Pins

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

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

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

The Endgame: Final 10 Seconds

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

• Positioning and timing become critical
• Robot durability matters more

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

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

Using Sensors in the Game

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

• Identify objects
• Interact with Toggles
• Navigate the Field

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

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

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

Have a great season!

• The VEX V5 Robotics Competition Game Design Committee

Scoring

Autonomous Bonus	12 Points
Each Scored Alliance-colored Pin	5 Points
Each Scored yellow Pin	10 Points
Each Robot in the Midfield	8 Points

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

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

<SC2> Placed Scoring Object criteria.

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

Caution

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

Figure SC2-1: The Scoring Objects stacked in the Goal all count as Placed, as they are all at least partially nested with the Goal and/or other Placed Scoring Objects.

Figure SC2-2: The Pin resting on top is partially nested with the Cup, but the Pin is not considered Placed since that half of the Cup contains more than one Pin half.

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

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

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

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

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

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

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

Figure SC5-1: This Quadrant’s Toggle is set to red, so yellow Pins Placed in this Quadrant’s Goals are Owned by the red Alliance.

Figure SC5-2: The blue Alliance has more Robots in the Midfield at the end of the Match, so yellow Pins Placed in the Midfield Goal are Owned by the blue Alliance.

A stack of pins and cups on the field. Behind the stack is a toggle set to yellow. Each pin has a point value listed on the image that is color coded to the alliance. From top to bottom those points are, red plus 5, red plus 5, blue plus 5, plus 0, plus 0, red plus 5, plus 0.	A stack of pins and cups on the field. Behind the stack is a toggle set to blue. Each pin has a point value listed on the image that is color coded to the alliance. From top to bottom those points are, red plus 5, red plus 5, blue plus 5, blue plus 10, blue plus 10, red plus 5, blue plus 10.	A stack of pins and cups on the field. Behind the stack is a toggle set to red. Each pin has a point value listed on the image that is color coded to the alliance. From top to bottom those points are, red plus 5, red plus 5, blue plus 5, red plus 10, red plus 10, red plus 5, red plus 10.
Toggle: Yellow	Toggle: Blue	Toggle: Red
Red Pins: 15 points	Red Pins: 15 Points	Red Pins: 15 Points
Blue Pins: 5 Points	Blue Pins: 5 Points	Blue Pins: 5 Points
Yellow Pins: 0 Points	Yellow Pins: 30 Points (Scored for Blue)	Yellow Pins: 30 Points (Scored for Red)
Total Red : 15 Points / Blue : 5 Points	Total Red : 15 Points / Blue : 35 Points	Total Red : 45 Points / Blue : 5 Points

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

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

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

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

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

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

Caution

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

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

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

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

Specific Game Rules

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

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

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

Caution

This rule has additional Violation notes. See Appendix C.

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

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 starting size limit within the following criteria:

1. The Robot can never be larger than 24” wide or 24” long at any point during the Match (must fit within a 24”x24” square horizontal footprint).

Caution

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

Caution

This rule has additional Violation notes. See Appendix C.

Figure SG-2: A demonstration of how the size of the Robot may change horizontally through the course of a vertical expansion.

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

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

1. A Scoring Object that comes to rest on top of the Field Perimeter is considered to have left the Field.

Caution

This rule has additional Violation notes. See Appendix C.

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

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

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

Caution

This rule has additional Violation notes. See Appendix C.

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

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

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

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

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

Caution

This rule has additional Violation notes. See Appendix C.

Figure SG-7: These Scoring Objects (circled in red) would be considered to be on the Autonomous Line.

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

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

Caution

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

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

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

<SG9> Alliance Goals are protected. Robots may not directly or indirectly interact with opposing Alliance-colored Goals. Examples of interactions include, but are not limited to:

1. Making contact with the Goal
2. Making contact with Scoring Objects stacked on the Goal
3. Adding or removing Scoring Objects (Placed or otherwise)
4. Strategically covering the Goal in a manner that prevents additional Scoring Objects from being Placed

Caution

This rule has additional Violation notes. See Appendix C.

<SG10> Placed Scoring Objects cannot be removed from neutral Goals.

Caution

This rule has additional Violation notes. See Appendix C.

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

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

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

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

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

Caution

This rule has additional Violation notes. See Appendix C.

Figure SG11-1: Scoring Objects can be introduced through the top opening of the Loader.

Figure SG11-2: Scoring Objects may also be introduced through the back of the Loader while it is raised.

<SG12> Some rules change during the Endgame period.

1. Robots that are partially or entirely within the infinite 3D vertical projection of the Midfield must make an effort to limit vertical expansion to the approximate starting height of the Robot. If a Head Referee sees a Robot within the Midfield that is clearly expanded past its approximate starting height, that Robot should receive a verbal warning and must either return to approximate starting height or exit the Midfield.
   1. A Robot should receive a Violation if it takes no action to either return to approximate starting height or exit the Midfield after a brief period of time. The length of this period of time is subject to Head Referee judgement within the context of the Match and the warned Robot’s actions (or lack thereof).
2. Robots that attempt to end the Match in the Midfield should expect vigorous interactions from opposing Robots. When a Robot is contacting or engaging with the Midfield, or is in proximity to the Midfield, incidental damage that is caused by opposing Robots pushing, tipping, or becoming Entangled with them would not be considered a Violation of GG14. Intentional damage or dangerous mechanisms may still be considered a Violation of S1 or G1 at the Head Referee’s discretion.

The intent behind the Endgame vertical expansion limit is to reduce the likelihood of tipped Robots due to expected Endgame interactions. Vigorous interactions involving taller Robots are much more likely to result in tipping compared to those involving shorter Robots.

Enforcement of this rule should focus on vertically expanded Robot lifts, rather than small pop-up mechanisms that are typically set to expand at the start of the Match.

<SG13> Load Zones are protected during the Driver Controlled Period of the Match.

• A Robot is protected while it is at least partially within one of its Alliance Load Zones. Robots may not directly or indirectly contact a protected opposing Alliance Robot.
• Robots may only enter an opposing Alliance Load Zone momentarily (e.g., while passing through or to retrieve a Scoring Object); Robots may not remain within an opposing Alliance Load Zone.
• Robots may not cause Scoring Objects to accumulate within an opposing Alliance Load Zone.

The intent of this rule is to protect Load Zones from intentional interference by the opposing Alliance (i.e., obstructing the Load Zone in an effort to inhibit Loader access).

This rule does not apply during the Autonomous Period.

This rule is applied differently for VEXU. See Rule VUG7.

Safety Rules

<S1> Be safe out there. If at any time the Robot operation or Team actions are deemed unsafe or have damaged a Field Element, Scoring Object, or the Field, the offending Team may receive a Disablement and/or Disqualification at the discretion of the Head Referee. The Robot will require re-inspection as described in rule R2 before it may take the Field again.

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

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

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

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

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

General Rules

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

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

Caution

We all can contribute to creating a fun and inclusive event experience for all event attendees. Some examples include:

When dealing with difficult and stressful situations, it is…

• Okay for Teams to be gracious and supportive when your Alliance partner makes a mistake.
• Not okay for Teams to harass, tease, or be disrespectful to your Alliance partner when a Match does not go your way.

When a Team does not understand a Match ruling or score, it is…

• Okay for Drive Team Members to consult with a Head Referee to discuss a ruling per the process outlined in T3 in a calm and respectful manner.
• Not okay for Drive Team Members to continue arguing with the Head Referee after a decision has been finalized, or for Adults to approach a Head Referee with ruling/scoring concerns.

When Teams are getting ready for an upcoming Match, it is…

• Okay for Teams in an Alliance to develop a game strategy that utilizes the strengths of both Robots to cooperatively solve the game.
• Not okay for one Team in an Alliance to ask another Team to sit in a corner during the Match or to intentionally play beneath their abilities.

Caution

This rule has additional Violation notes. See Appendix C.

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

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

Caution

When building or designing the Robot, it is…

• Okay for an Adult to help a Student consider why something failed, so it can be improved.
• Not okay for an Adult to provide step by step instructions or photos for the Student to copy.

When a mechanism falls off, it is…

• Okay for an Adult to help a Student consider why it failed, so it can be improved.
• Not okay for an Adult to investigate or put the Robot back together.

When a Team encounters a complex programming concept, it is…

• Okay for an Adult to guide a Student through a flowchart to understand its logic.
• Not okay for an Adult to write a premade command for that Student to copy/paste.

During Match play, it is…

• Okay for an Adult to provide cheerful, positive encouragement as a spectator.
• Not okay for an Adult to shout step-by-step commands from the audience.

Caution

This rule has additional Violation notes. See Appendix C.

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

Caution

Some examples include:

• If there is an obvious typographical error (such as “per T5” instead of “per GG5”), this does not mean that the error should be taken literally until corrected in a future update.
• Understand the realities of the VEX V5 Robot construction system. For example, if a Robot could hover above the Field for a whole Match, that would create loopholes in many of the rules. But… they can’t. So… don’t worry about it.
• When in doubt, if there is no rule prohibiting an action, it is generally legal. However, if you have to ask whether a given action would violate S1, G1, or T1 then that’s probably a good indication that it is outside the spirit of the competition. On the other hand, if there’s not a rule that makes a Robot part legal, it’s not allowed.
• In general, Teams will be given the “benefit of the doubt” in the case of accidental or edge-case rules infractions. However, there is a limit to this allowance, and repeated or strategic infractions will still be penalized.
• This rule also applies to Robot rules. If a component’s legality cannot be easily/intuitively discerned by the Robot rules as written, then Teams should expect additional scrutiny during inspection. This especially applies to those rules which govern non-VEX components (e.g. R18, R19, R22, etc). There is a difference between “creativity” and “lawyering.” Basically, if there’s not a rule that makes a Robot part legal, it’s not allowed.

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

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

Caution

Teams that use outside designs, instructions, code, and/or other materials instead of doing their own work undermine the core mission of the program: to provide Students with ownership of their work through hands-on opportunities to learn, design, and innovate.

While it is never our desire to punish Students, we must preserve the fairness, educational value, and integrity of the competition. Each Team must be able to explain and defend the design, construction, and programming of their Robot if questioned by event staff.

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 (in conversation and through their engineering notebook if the Team has one), and Students should be prepared to describe their design process, justify design decisions, and demonstrate a full understanding of how their Robot and code function. 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. If a Team is unable to provide reasonable evidence that their Robot, code, and documentation are the result of their own work, it is appropriate to assume that the Team is in Violation of G2 and/or G4.

Consequences may include Disqualification from Matches, removal from events, and/or escalation of the investigation to VEX Robotics 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 investigation. Misuse of this rule is considered a serious Violation.

Caution

This rule has additional Violation notes. See Appendix C.

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

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

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

Caution

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 prevent any instance of loaning or sharing Team members for the sole purpose of gaining a competitive advantage.

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

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

Caution

This rule has additional Violation notes. See Appendix C.

General Game Rules

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

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

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

Caution

Point iii is intended to refer to non-Robot-related items that directly influence gameplay, such as a speaker that plays a buzzer sound to distract your opponent. Provided no other rules are violated, and the items do not pose any safety or Field damage risks, the following examples are not considered Violations of GG1:

• Materials used before or after a Match, such as a pre-Match alignment aid
• Strategic aids, such as a whiteboard or clipboard
• Earplugs, gloves, or other personal accessories

Caution

This rule has additional Violation notes. See Appendix C.

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

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

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

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

Caution

The definition of the word “promptly” as used in clause A is at the discretion of the Event Partner and Head Referee, who will consider event schedule, previous Violations or delays, etc. As a general guideline, five seconds to check Robot alignment would be acceptable, but five minutes to assemble multiple parts together would not.

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

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

Caution

If a Drive Team Member’s hands extend over the Field and/or Field Perimeter in a way that is safe and doesn’t contact anything in the Field, it’s unlikely to be a Violation. However, Head Referees may still ask Drive Team Members to step back and remain completely outside the Field when necessary (e.g., for safety reasons or to reduce the chances of gameplay interference).

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

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

Caution

Communication or control issues affecting a single Robot are not considered eligible grounds for a replay.

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

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

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

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

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

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

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

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

Caution

This rule has additional Violation notes. See Appendix C.

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

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

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

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

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

Caution

This rule has additional Violation notes. See Appendix C.

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

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

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

Caution

This rule has additional Violation notes. See Appendix C.

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

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

Caution

This rule has additional Violation notes. See Appendix C.

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

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

Caution

This rule has additional Violation notes. See Appendix C.

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

Caution

This rule is intended to be a “logical tiebreaker” for use only when referees cannot make a clear and definitive ruling without it. It should not be used or applied in every situation. Most Violations should be resolved without considering this rule.

Head Referees must apply judgment when determining whether each Robot in a GG15 interaction was Defensive or Offensive, and in some cases may need to consider which Robot was more Defensive or Offensive than another within the larger context of the Match. In these cases, the Head Referee should decide in favor of the less Defensive and/or more Offensive Robot based on the definitions and guidance in this game manual.

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

Caution

This rule has additional Violation notes. See Appendix C.

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

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

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

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

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

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

Caution

If the Head Referee determines that a Robot is not attempting to escape, then it is not considered Pinned or Trapped. This commonly occurs when the Robot has malfunctioned and lost the ability to move, or when the Robot is defending a Field Element.

This criteria is not required for Lifting; the Holding status begins as soon as the opponent becomes Lifted.

Holding is a standard and legal part of Head-to-Head game play, and only becomes a Violation if it exceeds the guidelines in this rule. By beginning a Holding count immediately after noticing a Holding interaction, and providing a visual signal when a Holding interaction has been cleared, Head Referees can help Teams avoid penalties.

Starting a Holding count is not, in and of itself, a declaration that Holding is occurring. Ending a Holding count early and waving it off is also not, in and of itself, an indication that Holding has occurred. There is no harm in a Head Referee reacting quickly with a Holding count, realizing that no Holding is occurring, and then ending and waving off the count.

During a Holding count, the Head Referee should continually verify that the interaction meets the definition of Holding. If it becomes clear that the interaction doesn’t meet the definition of Holding, the Head Referee should end the count early and wave off the Holding count. Holding only becomes a Violation if a referee exceeds a three-count before the Robots separate as described in rule GG17.

Caution

This rule has additional Violation notes. See Appendix C.

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

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

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