Section 2 - The Game

VEX IQ Level Up - A Primer

VEX IQ Robotics Competition Level Up is played on a 6’x8’ rectangular Field, set up as illustrated in the figures throughout this game manual.

The primary objective of the game is to score Bean Bags into Goals. Higher Goals earn more points. A Robot can only carry one Bean Bag at a time, and most Bean Bags have to travel across the entire Field to reach their Goals. Teams have to decide whether to drive a long path or design their Robot to fit through the narrow shortcuts on the Field.

In Teamwork Matches, an Alliance composed of two Robots works together to score as many points as possible in a 60-second Match.

Teams may also compete in Robot Skills Matches, where one Robot tries to score as many points as possible with a slightly different set of rules. See Section 3 for more information.

Field Overview

The VEX IQ Robotics Competition Level Up Field consists of the following:

• 38 Bean Bags
  • 16 blue Bean Bags
    • 8 that start in the Field
    • 8 that can be introduced through the blue Load Zone
  • 16 red Bean Bags
    • 8 that start in the Field
    • 8 that can be introduced through the red Load Zone
  • 6 yellow Bean Bags
    • 2 Preloads, one for each Team
    • 4 that start in the Field
• Two Pyramid Goals, one red and one blue
• Two L4 Goals
• Two Floor Goals, one red and one blue
• Two Load Zones, one red and one blue
• Two wall structures
• Two Floor barriers

Caution

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.

Caution

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: Starting configuration of a VEX IQ Level Up Field Teamwork Match with Bean Bags highlighted (Red, Blue, Yellow).

Figure FO-2: A VEX IQ Level Up Field, with Pyramid Goals (green), L4 Goals (purple), Floor Goals (blue) and Load Zones (orange) highlighted.

Figure FO-3: The recommended locations for Drive Team Members and Head Referees during Teamwork Matches.

Game Design Philosophy - A Letter from the GDC

We as the Game Design Committee want to explain how this game was designed and how we expect it to be played. We will also point out parts of the game we will watch during the season in case changes are needed.

This section is not a list of rules. It is here to help you understand what the game is about and what we as designers had in mind.

Level Up is a game where Robots move around the Field again and again to score. You can only move one Bean Bag at a time. Because of this, Teams will need to score often and move quickly. The game rewards Robots that can repeat actions and follow a plan.

*Navigation and Route Choice*

The Field is designed to give Teams choices about how their Robot moves.

Some paths are longer but more open and easier to use. Other paths are shorter but tighter and harder to move through. Teams will need to decide which path works best for their Robot.

*Robot Design Tradeoffs*

The way your Robot is built will affect how it moves on the Field.

Smaller Robots may be able to use shortcuts. Larger Robots may be more stable or easier to control. Teams will need to make choices about what is most important for their design.

There is no one “best” design. Different Robots can succeed in different ways.

*Scoring Strategy*

There are Goals with different heights and point values on the Level Up Field. This gives Teams choices about how they want to work with their partner and score.

Some Teams may try to score higher points each time. Others may focus on scoring faster. The best strategies will balance how many points you score, how quickly you score, and how often your Robot can repeat the action.

Commitment to Teams

The Game Design Committee will watch how Matches are played during the season. We want to make sure the game stays fun, fair, and interesting!

If needed, we may make updates to keep the focus on movement, scoring, and teamwork.

Have a great season!

• The VEX IQ Robotics Competition Game Design Committee

Scoring

Each Bean Bag scored in a Floor Goal	1 Point
Each Bean Bag scored on an L1 Goal	3 Points
Each Bean Bag scored on an L2 Goal	6 Points
Each Bean Bag scored on an L3 Goal	12 Points
Each Bean Bag scored on a L4 Goal	16 Points

<SC1> All scoring statuses are evaluated after the Match ends, once all Scoring Objects, Field Elements, and Robots on the Field come to rest. See rule GG12 for more information and Violation details.

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

<SC2> All scoring statuses are evaluated visually by a Head Referee, to the best of their ability within the context of a given Match/event.

1. Referees and other event staff are not allowed to review any videos or pictures from the Match. See T3.
2. If there is a concern regarding the score of a Match, only the Drive Team Members from that Match, not an Adult, may share their questions with the Head Referee. See T3.

<SC3> A Bean Bag is scored in a Floor Goal if it meets all of the following criteria.

1. No part of the Bean Bag is contacting a Robot.
2. The Bean Bag is entirely within the defined area of the Floor Goal (e.g., no part of the Bean Bag is on top of the Field Perimeter or the VEX IQ parts that define the Floor Goal).
3. The Bean Bag is yellow, or matches the color of the Floor Goal.

Figure SC3-1: Bean Bags in the Floor Goal.

• The red Bean Bag would not be considered scored, as it is resting on top of the VEX IQ parts that make up the Floor Goal, and not entirely within the defined area.
• The blue Bean Bag would not be considered scored, as it does not match the color of the Floor Goal.
• The yellow Bean Bag would be considered as scored, as it can be scored in either color Floor Goal, and is entirely within the defined area.

<SC4> A Bean Bag is scored on an L1, L2, or L3 Goal if it meets all of the following criteria:

1. No part of the Bean Bag is contacting a Robot.
2. The Bean Bag is in contact with the horizontal surfacet that defines the L1, L2, or L3 Goal, or is directly or indirectly supported by another Bean Bag that is in contact with that horizontal surface.
3. The Bean Bag is not in contact with anything outside the Field.
4. The Bean Bag matches the color of the L1, L2, or L3 Goal, or the Bean Bag is yellow.

If a Bean Bag counts as scored on multiple levels (e.g., in contact with L3 while also supported by a stack of Bean Bags in L2), it should only receive points for the higher level.

Figure SC4-1: Bean Bags in the Pyramid Goal.

• The blue Bean Bag would not be considered scored, as it does not match the color of the L1 Goal it is resting on.
• The three (3) red Bean Bags would all be considered as scored on the L2 Goal, as they match the color of the Goal, and are all either in contact with the L2 Goal or supported by another Bean Bag in contact with the L2 Goal.
• The yellow Bean Bag is contacting the L3 Goal and is also supported by a stack of Bean Bags on the L2 Goal. This means the yellow Bean Bag is considered scored on multiple levels (L2 and L3), in which case it should only receive points for the higher level (L3).

<SC5> A Bean Bag is scored on a L4 Goal if it meets all of the following criteria:

1. No part of the Bean Bag is contacting a Robot.
2. The Bean Bag is in contact with the horizontal surface that defines the L4 Goal, or is directly or indirectly supported by another Bean Bag that is in contact with that horizontal surface.
3. The Bean Bag is yellow.

Figure SC5-1: Bean Bags on the L4 Goal.

• Both yellow Bean Bags would be considered as scored on the L4 Goal, as both are either in contact with the L4 Goal or supported by another Bean Bag in contact with the L4 Goal.
• The red Bean Bag is not scored on the L4 Goal, since only yellow Bean Bags can be scored on the L4 Goal.

Specific Game Rules

<SG1> Starting a Match. At the beginning of a Match, the Robot must be placed such that it meets all of the following criteria:

1. Fit within an 11” wide x 20” long x 15” high (279mm x 508mm x 381mm) volume, as checked during inspection per R3.

2. Positioned within one of the starting positions shown in Figure SG-1.

   1. For Teamwork Challenge Matches, the Team listed as Team 1 (printed Match list), listed as red Team (events.vex.com), or listed first (VEXvia) must place their Robot in the starting position that shares a wall with the blue Pyramid Goal.
   2. For Teamwork Challenge Matches, the Team listed as Team 2 (printed Match list), listed as blue Team (events.vex.com), or listed second (VEXvia) must place their Robot in the starting position that shares a wall with the red Pyramid Goal.

3. Completely stationary (i.e., no motors or other mechanisms in motion) until the Match timer starts. Pre-charging a pneumatic system (e.g., having the Pneumatic Pump running prior to the Match) is the only permitted exception to this rule.

4. The starting configuration of the Robot at the beginning of a Match must be the same as a Robot configuration that was checked during Robot inspection.

   This rule has additional Violation notes. See Appendix D.

Figure SG-1: Robots in legal pre-Match starting positions (highlighted in yellow).

<SG2> Horizontal expansion is limited. Once the Match begins, Robots may expand horizontally up to a length of 24”. The Robot can never be larger than 11”x24” at any point during the Match (must fit within an 11”x24” rectangular 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 11” x 24” at any point during a Match due to either physical or programmed limitations, including while any vertical expansion mechanisms are in use.

Figure SG2-1: A demonstration of how the size of the Robot may change horizontally through the course of a vertical expansion. The Robot on the far left is extended beyond 24”, and would be in Violation of SG2.

<SG3> Vertical expansion is unlimited. Once the Match begins, Robots may expand vertically beyond the 15” starting size limit with no limits.

<SG4> Keep Scoring Objects in the Field. Scoring Objects that leave the Field during a Match will not be returned to the Field, and cannot be reintroduced by the Loaders.

1. “Leaving the Field” means that a Scoring Object is outside of the Field Perimeter, no longer in contact with the Floor or Field Elements, and not supported by Robots or Scoring Objects that are still inside the Field.
2. If a Scoring Object is removed from a Robot during a GG10 interaction, it is considered “out of the Field” as soon as it is no longer in contact with any Robots.
3. If a Scoring Object is on its way out of 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, SG4 would still apply. This Scoring Object should be considered “out of the Field” and removed by a Head Referee.
4. A Scoring Object that comes to rest on top of the Field Perimeter is still considered to be inside the Field unless it contacts something outside of the Field (e.g., volunteer, Drive Team Member, field monitor, etc.), and cannot be retrieved by a Drive Team Member or volunteer.
5. A Bean Bag that ends up inside the Pyramid Goal structure should be considered “out of the Field.”

<SG5> Each Robot gets one yellow Bean Bag 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 exactly one Robot.
2. Not contacting any Field Elements (excluding the Floor), Goals, or other Scoring Objects.

If a Robot is not present for a Teamwork Match, its Preload should be placed in that Team’s Load Zone.

<SG6> Possession is limited to one (1) Bean Bag. Possession and Plowing are limited to one (1) Bean Bag. A Robot cannot have greater-than-momentary Possession of and/or Plow more than one Bean Bag at once. Robots that are interacting with multiple Bean Bags must immediately stop all Robot actions except for attempting to remove the excess Bean Bag(s).

Caution

The intent of this rule is that each Robot should only interact with one Bean Bag at a time. Robots should not drive through Bean Bags on the Field while Possessing a Bean Bag, and cannot “Plow” one or more Bean Bags while already in Possession of a Bean Bag.

Momentary, incidental contact with a Bean Bag that results in minimal movement of the Bean Bag would not be considered Plowing. Greater than momentary contact with a Bean Bag that results in more significant movement of the Bean Bag (e.g., pushing a Bean Bag across a distance of 1 tile length or more) would generally be considered Plowing. The final determination of whether a Bean Bag has been Plowed will require some level of judgment from the Head Referee.

<SG7> Using the Load Zone. Bean Bags may be Loaded one at a time through the Load Zone during the Match, and must meet all of the following criteria.

1. Red and blue Bean Bags may only be Loaded into the Load Zone that matches the color of that Bean Bag.
2. The Bean Bag must be placed in contact with the Floor and fully within the Load Zone (i.e., not contacting any VEX IQ pieces that form the border of the Load Zone).
3. The Loader may only put a Bean Bag into a Load Zone if no other Bean Bags are in contact with that Load Zone.
4. A Robot may not contact a Bean Bag in the Load Zone if that Bean Bag is being contacted by a human.
5. Once a Bean Bag is placed into a Load Zone and released, it may no longer be contacted by a Loader unless the Head Referee determines it was misloaded and must be retrieved as described in clause F.
6. If a Bean Bag is Loaded improperly (e.g., while another Bean Bag is in contact with the Load Zone), it must be retrieved by the Loader and reintroduced if the Head Referee instructs the Loader to do so.
7. A Loaded Bean Bag must be placed in a stationary position, and must remain in contact with the Floor after it is released by the Loader until it is contacted by a Robot.
8. Bean Bags that begin the Match outside the Field cannot break the plane of the Field Perimeter until the Match begins.

Caution

Note: Although it is not required, Robots are highly recommended to remain some distance away from the Bean Bag until the Loader’s hand has clearly been removed. This will make clauses D & E abundantly clear to Head Referees.

Caution

This rule has additional Violation notes. See Appendix D.

Safety Rules

<S1> Stay safe, don’t damage the Field. If, at any time, the Robot operation or Team actions are deemed unsafe or have damaged any Field Elements or Scoring Objects, the offending Team may be Disabled and/or Disqualified at the Head Referee’s discretion. The Robot will require re-inspection before it may again take the Field.

Drive Team Members may not step onto the Field at any time, including pre-Match setup.

<S2> Students must be accompanied by an Adult. Every Student at a VEX IQ 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.

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

<G2> VEX IQ 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 D.

<G3> Use common sense. When reading and applying the various rules in this document, please remember that common sense always applies in the VEX IQ 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 IQ 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.

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

<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 IQ 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 Driver).

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, Drivers, 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 Driver 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.

Caution

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

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

General Game Rules

<GG1> Drivers drive your Robot, and stay in the Driver Station. During a Match, Robots may only be operated by that Team’s Drivers and/or software running on the Robot’s control system. Each Team may send up to three (3) Drive Team Members to their Driver Station for a Match: two (2) Drivers, and one (1) Loader. Those Drive Team Members must remain in their Driver Station, except when legally interacting with their Robot per GG10.

Drive Team Members are the only Team members that are allowed to be in the Driver Station during a Match. Adults (other than event staff) are not permitted to be in the Driver 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 Driver 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 the 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 Driver Station except as required by an officially approved accommodation request.
2. In Teamwork Matches, one Team in an Alliance is assigned to the red Driver Station and the other Team is assigned to the blue Driver Station, as follows:
   1. The Team listed as Team 1 on a printed Match list, listed as red Team on events.vex.com, or listed first in VEXvia will use the red Driver Station and participate as the red Team in that Match.
   2. The Team listed as Team 2 on a printed Match list, listed as blue Team on events.vex.com, or listed second in VEXvia will use the blue Driver Station and participate as the blue Team in that Match.
3. 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. 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 D.

<GG2> A Team’s Robot should attend every Match. The Team’s Robot must be in the Driver 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, that Team will be considered a “no show” and will receive zero (0) points. The other Team in the Alliance will still play and receive points for the Match.

1. Teams are expected to participate in all scheduled Qualification Matches and, if they’re ranked high enough to be included in a finals Alliance, Finals Matches. Failure to attend scheduled Matches 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 (i.e., battery charged, sized within the starting size constraint, 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.

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 allowances in GG10, RSC5, and SG7.

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.

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 examples that may warrant a Match replay are as follows (note that this is not an exhaustive list):

1. Score Affecting “Field fault” issues.
   1. Scoring Objects not being reset before the Match starts.
   2. Field Elements detaching or moving beyond normal tolerances, not a result of Robot interactions.
2. Score Affecting game rule issues.
3. A Field is reset before the score is determined.
4. A Match is run before its scheduled time without a Team.

<GG6> Disqualifications. A Team that is issued a Disqualification in a Qualification Match receives zero points for the Match. The other Team on their Alliance will still receive points for the Match.

1. In Finals Matches, Disqualifications apply to the whole Alliance, not just one Team. An Alliance that receives a Disqualification in a Finals Match will receive zero points.
2. A Team that receives a Disqualification in a Robot Skills Match will receive a score of zero.

<GG7> Time-outs. There are no time-outs in VEX IQ Tournaments.

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

1. Parts that become unintentionally detached from the Robot are no longer considered to be part of the Robot and can be either left on the Field or collected by a Drive Team Member during a Robot reset using GG10.

<GG9> Don’t damage the Field. Robot interactions which damage the Field or any Field Elements are prohibited. For the purpose of this rule, “damage” is defined as anything which requires repair in order to begin the next Match, such as causing part of a Goal to detach from the Field.

Caution

Teams are responsible for the actions of their Robots at all times, especially when interacting with the Goals. If a Team chooses to repeatedly ram full-speed into a Field Element, it will be hard to convince a Head Referee that any damage caused was “accidental.

Caution

This rule has additional Violation notes. See Appendix D.

<GG10> Handling the Robot mid-Match is allowed under certain circumstances. If a Robot goes completely outside the playing Field, gets stuck, tips over, or otherwise requires assistance, the Drive Team Members may retrieve & reset their Robot with the Head Referee’s permission. To do so, the Team must do the following:

1. Signal the Referee by placing their VEX IQ Controller on the ground. The Head Referee may ask the Driver to demonstrate the problem using the Robot controller before approving the Robot reset (e.g., confirming that the Robot is broken, undriveable, or stuck on an obstacle) if the issue with the Robot isn’t obvious.
2. Any Scoring Objects being controlled by the Robot while being handled must be removed from the Field, will not be returned to the Field, and cannot be reintroduced by the Loaders. No other Scoring Objects should be adjusted.
   1. In the context of this rule, “controlled” implies that the Robot was manipulating the Scoring Object, and not simply touching it. For example, if the Scoring Object would move with the Robot either vertically or while turning, then the Robot is “controlling” that Scoring Object.
3. The Robot must be placed back into a legal position that meets the criteria listed in clauses a,b, c, & d of SG1. If any Scoring Objects are preventing the Robot from being legally placed, they should be removed from the Field, will not be returned to the Field, and cannot be reintroduced by the Loaders. The Robot does not get a new Preload during this reset.
4. Swapping one set of parts for another, or adding new pieces to a Robot mid-Match during a GG10 or RSC5 interaction is considered a Violation of the intent and spirit of this rule. Repairing a Robot, or reattaching parts of the Robot that unintentionally break off during a Match, is allowed.
5. As described in rule S1, Students cannot step into the Field at any time during a Match. If the Drive Team Members cannot reach the Robot due to the Robot being in the center of the Field, they may ask the Head Referee to pick up the Robot and hand it to the Drive Team Members for placement according to the conditions above.

Caution

This rule has additional Violation notes. See Appendix D.

<GG11> A Team’s two Drivers switch Controllers midway through the Match. In a given Match, up to two (2) Drivers may be in the Driver Station per Team. The two Drivers must switch their controller between thirty-five seconds (0:35 on the Match timer) and twenty-five seconds (0:25 on the Match timer) remaining in the Match.

1. No Driver shall operate a Robot for more than thirty-five (35) seconds.
2. The second Driver may not touch their Team’s controls until the controller is passed to them.
3. Once the controller is passed, the first Driver may no longer touch their Team’s controls.
4. A Driver cannot also be a Loader in the same Teamwork Match.
5. If a drive team for a Match only has two members, one must serve as the Driver until the mid-Match Driver switch. The second Drive Team Member may serve as either the 2nd Driver (after the mid-Match Driver switch) or the Loader for the full Match, but cannot fill both roles. If the 2nd Driver position is unfilled, the Robot’s operation (even prewritten commands) must cease after the first thirty-five (35) seconds of the Match.
6. If only one Drive Team Member is present, the Robot’s operation (even prewritten commands) must cease after the first thirty-five (35) seconds of the Match and the Team will not have a Loader during that Match.

Caution

This rule has additional Violation notes. See Appendix D.

<GG12> Don’t start before the timer, and stop moving at the end of the Match. Driver inputs and Robot may not begin before the Match timer starts, and must cease at the end of the Match, when the timer reaches 0:00.

1. Any scoring that takes place after a Match due to Robots continuing to move will not count toward the score.
2. A pre-programmed routine which causes Robot motion to start before the Match or continue after the end of the Match would violate this rule.
3. Any scoring that takes place after the end of a Teamwork Match is a Violation. Scoring that occurs after the end of a Robot Skills Match is not a Violation.

Caution

It is expected that many Level Up Matches will have last-second “buzzer-beater” moments. The key moment occurs when the timer display shows 0:00. At many events, a buzzer sound will also play at T=0:00; however, the Field timer display takes precedence in the event of any audio discrepancies.

If a Scoring Object is released from a Robot before this moment, it will be allowed to finish its path and the score will be calculated once it comes to rest. However, if it is released after this moment (i.e., the Robot was still moving past T=0:00) it will not count and the Team will receive a Violation as described below.

In cases where a last-second scoring attempt is “too close to call,” Teams will generally be given the “benefit of the doubt” and the score will be counted. Teams are advised to place and release Scoring Objects a second or two before the timer reaches zero to avoid the need for referee judgment calls.

Caution

This rule has additional Violation notes. See Appendix D.

<GG13> Ending a Match early. If an Alliance wants to end a Qualification Match or a Finals Match early, both Teams must signal the referee by ceasing all Robot motion and placing their controllers on the ground. The referee will then signal to the Teams that the Match is over and will begin to tally the score. If the Match is a tiebreaker Finals Match for first place, then the Match Stop Time will also be recorded (see T14B).

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

1. Referees are not permitted to review any photo or video Match recordings when determining a score or ruling. Some events may also prohibit Drive Team Members from reviewing photo or video Match recordings while in the Driver Station; this should be announced to all Teams before Matches start.
2. Head Referees are the only individuals permitted to explain a rule, Disqualification, or Violation to the Teams in a Teamwork 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 IQ 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.

Caution

Some events may choose to utilize a “question box” or other designated location for discussions with Head Referees. Offering a “question box” is within the discretion of the Event Partner and/or Head Referee, and may act as an alternate option for asking Drive Team Members to remain in the Driver Station (although all other aspects of this rule apply).

However, by using this alternate location, Drive Team Members acknowledge that they are forfeiting the opportunity to use any contextual information involving the specific state of the Field at the end of the Match. For example, it is impossible to appeal whether a game element was scored or not if the Field has already been reset. If this information is pertinent to the appeal, Drive Team Members should still remain in the Driver Station, and only relocate to the “question box” once the Head Referee has been made aware of the concern and/or any relevant context.