V5RC High Stakes Game Manual Updates

This thread will be used to publish updates to the VRC High Stakes Game Manual.

Please start a separate thread in this forum category for unofficial discussion of any of these changes. For any official questions, please post in the official VRC High Stakes Q&A.

9 Likes

On June 4th, 2024, Version 0.2 of the V5RC High Stakes Game Manual was released, and the following changes were made:

  1. Updated Figure SC3-2 to show a different angle that more clearly shows the Scored Rings

  2. Updated SC8 to clarify that at least one Robot must be touching the Ladder

  3. Added a bullet to SG5 to clarify that Preloads may not start in a Scored location

  4. Updated SG6 to clarify Possession limits

Two (2) Rings and/or one (1) Mobile Goal

  1. Deleted SG6a. SG6a-i was moved into the main part of the rule

  2. Updated the Violation Note of SG6 to clarify that an intentional Violation will be
    considered a Major Violation, rather than Match Affecting

Any egregious or clearly intentional Violation by an Alliance who wins the Match will be considered a Major Violation.

  1. Updated R16e to clarify that R8d is an exception

Welding, soldering, brazing, gluing, or attaching parts to each other in any way that is not provided within the VEX platform is not permitted. Rule clause D is an exception to this rule.

  1. Updated T10d and T10e to clarify Ring and Mobile Goal weights

d. Rings have a nominal weight of .25lbs and may vary by +/- .075lbs (113.4g +/- 34g)
e. Mobile Goals have a nominal weight of 2lbs and may vary by +/- .075lbs (907g +/- 34g)

  1. Updated RSC4 to clarify intent, and added a new bullet point

Blue Rings may only be Scored as Top Rings on Stakes.
e. Red Rings may also be Scored as Top Rings on Stakes, but rule applies.

  1. Minor typo / formatting fixes

The next manual update, Version 1.0 will occur on June 25th, 2024.

13 Likes

On June 25th, 2024, Version 1.0 of the V5RC High Stakes Game Manual was released, and the following changes were made:

  1. Changed the Field layout such that Positive Corners and Negative Corners are now on the same side of the Field, rather than cater cornered

  1. Updated Figures throughout the manual to display the new Corner layout

  2. Added a new definition of “Plane”

An imaginary horizontal surface that divides the vertical space between two Levels, and expands infinitely across the Field

  1. Expanded SC3 to clarify that Rings can only be counted for points once, even in situations where it qualifies as Scored on multiple Stakes

Each Ring can only be counted for points once, even in cases where the Ring qualifies as Scored on multiple Stakes. If multiple Stakes are encircled by the same Ring, Top Rings will not be awarded for those Stakes. Intentionally causing a Ring to be Scored on multiple Stakes will, at minimum, receive a Minor Violation.

  1. Updated Figures SC7-1 and SG3-1 to show Planes

  2. Updated SC7di to clarify intent

Each Level corresponds to a vertical section of the Ladder. For example,
a Level 1 Climb represents a Robot whose lowest point is above the Floor tiles, but not higher than the black rung of the Ladder.

  1. Revised SC8 to clarify the Autonomous Win Point requirements
  1. At least three (3) Scored Rings of the Alliance’s color
  2. A minimum of two (2) Stakes on the Alliance’s side of the Autonomous Line with at least one (1) Ring of the Alliance’s color Scored
  1. Added a new rule, SC9, that adds a 2-point bonus per Climb for whichever Alliance has a Ring Scored on the High Stake at the end of a Match

A High Stake bonus is available to an Alliance that ends the Match with a Ring Scored on the High Stake. Each Robot from that Alliance which has earned points for a Climb will receive an additional two (2) points for that Climb.

  1. Updated SG2 to clarify that Robots may expand beyond their starting size and configuration

Once the Match begins, Robots may expand beyond their starting size and configuration within the following criteria:

  1. Added an additional bullet to SG3 and updated the red box to clarify intent

  2. Added an additional Violation Note to SG4 to state that a Team will receive a Major Violation for removing three (3) or more Rings from the Field in a single Match

  3. Rewrote SG5c to clarify that preloads cannot start in a Scored location

Not in a scored location, and not contacting any other Scoring Objects or Stakes.

  1. Updated SG9 to clarify that Team cannot negate an opponent’s Climb by contacting their Robot with a Mobile Goal

Teams cannot negate an opponent’s Climb by contacting their Robot with a Mobile Goal, and an affected Climb will still be Scored. Doing so will result in a Minor Violation for the offending Team, assuming no other rules are broken and no damage is caused to the opponent.

  1. Added a new rule, SG11, to add a 10 second protection to Positive Corners at the end of a Match

Positive corners are “safe” during the endgame. During the last ten (10) seconds of a Match, Robots may not contact Mobile Goals in the positive Corners of the Field, and may not add or remove Mobile Goals or Rings to or from the positive Corners of the Field.

  1. Updated R10bi to clarify intent regarding License Plates showing the wrong color

  2. Added two new bullets to RSC3 to clarify that the blue Alliance Stake may be used in Robot Skills Matches

e. Rule SG10 does not apply, and Teams may freely use the blue Alliance wall Stake.
f. Rule SG11 does not apply.

  1. Updated VUG1c to reflect changes in SG3

Neither Robot may contact or “break the Plane of” three Levels, or two non-sequential Levels, at any time.

  1. Added Section 7, VEX AI Robotics Competition

  2. Minor typo / formatting fixes

The next manual update, Version 1.1 will occur on August 6th, 2024.

24 Likes

On August 6th, 2024, Version 1.1 of the V5RC High Stakes Game Manual was released, and the following changes were made:

  1. Added Grey Boxes throughout the manual to highlight significant Q&As pertaining to individual rules

  2. Rewrote the definition of Plowing

Plowing – A Robot / Scoring Object status. A Robot is considered to be Plowing a Scoring Object if the Robot is intentionally moving it in a preferred direction with a flat or convex face of the Robot, or with another Scoring Object.

  1. Updated SG2 with new verbiage and figures to clarify intent

  2. Updated SG5c to include Scoring Objects

Not contacting or encircling a Stake or any other Scoring Objects.

  1. Updated SG10 to clarify Scoring for Rings that end the Match on the opposing color Alliance Wall Stake

If a Ring of the opposing color ends the Match in a Scored position on an Alliance Wall Stake, that Ring should not be considered as Scored, and will not earn points for either Alliance (it will still, however, count toward the maximum number of 2 rings that can be placed on an Alliance Wall Stake).

  1. Updated SG11 to clarify intent

Positive corners are “safe” during the endgame. During the last ten (10) seconds of a Match, Robots may not contact Mobile Goals that are Placed in the Positive Corners of the Field, may not contact Rings that are Scored on Mobile Goals Placed in the Positive Corners of the Field, and may not Place or Score additional Mobile Goals or Rings in the Positive Corners of the Field.

  1. Minor typo / formatting fixes

The next manual update, Version 2.0 will occur on September 3rd, 2024.

11 Likes

On September 3rd, 2024, Version 2.0 of the V5RC High Stakes Game Manual was released, and the following changes were made:

  1. Changed the Field tape layout so that Corners are now triangular

  2. Changed the starting Ring configuration; the Ring stacks that begin in the right Corner along each Alliance Station wall have been flipped

  3. Added Figure FO-3, to show the recommended locations of referees, and the field monitor

  4. Rewrote the definition of Corner to account for the new tape layout

One of four 12" (304.8 mm) x 12" (304.8 mm) triangular sections of the Field in which Mobile Goals can be Placed. Each Corner is an infinitely tall three-dimensional volume bordered by the inner edges of the Field Perimeter and the outer edge of the associated white tape line.

  1. Added Significant Q&A boxes and bullets throughout the manual

  2. Add Violation notes and clarifications to S1, S2, G1, G2, G4, R28, and T1 to clarify intent

  3. Rewrote SC3 and updated its figures so that Rings can still be Scored while in contact with a foam tile or a Robot of the same color

There is no requirement for a Mobile Goal to be upright in order for its Rings to be considered Scored. Contact with any other Field Elements or Rings is irrelevant.

  1. Rewrote SC5 to provide new criteria for Placed Mobile Goals, and tiebreakers if more than one Mobile Goal ends a Match in the Corner

Placed Mobile Goal Criteria
a. The Mobile Goal base is contacting the Floor or a white tape line.

b. Some portion of the flexible top of the Mobile Goal’s Stake is higher than the top edge of the Field Perimeter.

c. The Mobile Goal base is breaking the plane of the Corner.

Tiebreakers

  1. The Mobile Goal whose base extends farthest into the Corner is Placed. See Figure SC5-1.

  2. The Mobile Goal whose Stake is most vertical (perpendicular to the Floor) is Placed.

  3. The Mobile Goal whose flexible top extends farthest into the Corner is Placed.

  4. If multiple Mobile Goals are still tied for the above criteria, then no Mobile Goal is considered Placed in this Corner."

  1. Updated SC8 to include the Autonomous Win Point tasks for World Championship qualifying events

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

  1. At least four (4) Scored Rings of the Alliance’s color.

  2. A minimum of three (3) Stakes on the Alliance’s side of the Autonomous Line with at least one (1) Ring of the Alliance’s color Scored.

  3. At least one Ring of the Alliance’s color Scored on the Alliance’s Wall Stake.

  4. Neither Robot contacting / breaking the plan of the Starting Line.

  5. At least one (1) Robot contacting the Ladder."

  1. Updated SG2 to clarify intent

Intentionally exploiting a loophole in vertical expansion to get past the horizontal expansion limit is not allowed, and should be considered a Violation of rule . The overall intent of the expansion rules is to prevent wall bots and/or Climbs that skip rungs, and to avoid penalizing Robots that tip or slip slightly while Climbing.

  1. Revised SG3 to clarify that Robots may not break more than two Planes of the Ladder at any time

  2. Rewrote SG4 to only apply to opponent’s Scoring Objects

Teams may not intentionally or strategically remove Mobile Goals or their opponent’s Rings from the field. Rings that leave the Field during Match play will be returned to the Field by a referee such that they satisfy the following conditions:

Note: If a Mobile Goal leaves the Field, a referee should return it to the Field in a position on the Autonomous Line. Any Rings which were scored on this Mobile Goal will be returned to the field as described above.

Any Team that removes three (3) or more of their opponent’s Rings from the Field in a single Match will receive a Major Violation.

If it is not clear which Robot was the last to contact the Ring, the Team with a color that is opposite to the Ring will receive a Violation.

For the purposes of and in interactions where a Robot is attempting to remove Scored Rings from a Neutral Wall Stake and drops one or more of their opponent’s Rings out of the Field due to defensive interactions from that opponent, the Robot that is actively attempting to Score or de-Score Rings will get the benefit of the doubt provided by rule .

  1. Updated SG6 to clarify that Robots may posses two (2) Rings and one (1) Mobile Goal at one time

Possession is limited to two Rings and one Mobile Goal. Robots may not have Possession of more than two (2) Rings at once. Robots may not have Possession of more than one (1) Mobile Goal at once.

  1. Updated SG11 to change the Positive Corner protection period to fifteen (15) seconds

During this protected period, Robots can remove Mobile Goals that are not Placed and Rings that are not Scored from the Positive Corners of the Field, provided that the interaction does not affect the Placed/Scored status of any protected Mobile Goals or Rings.

  1. Changed T10g to state that Mobile Goal orientation should be consistent

Mobile Goals should be positioned with flat edges facing the audience and Head Referee sides of the Field (as shown in figures throughout the game manual), with minor variance in rotation.

  1. Added Elimination Match tiebreaker criteria to T19

a. Any Elimination Match that ends in a tied score with at least one Scored Ring and/or one Robot that has Climbed to a Level will result in a tiebreaker Match.

b. Any Elimination Match that ends in a tied score with no Scored Rings and no Robots that have Climbed to a Level may be decided by the quantity of Mobile Goals that are fully on each side of the Autonomous Line. The Alliance with a higher quantity of Mobile Goals completely on their side of the Autonomous Line, and not in contact with the Autonomous Line, at the end of the Match should be awarded the value of 1 Scored Top Ring for that Match. If the Alliances have an equal number of Mobile Goals on their side of the Autonomous Line, a tiebreaker Match should be played.

  1. Added a new Violation note to RSC1 to clarify that Violations that occur in Robot Skills Matches do not carry over to Head-to-Head Matches

Violation Note: Violations of rules that occur during a Robot Skills Challenge Match should only affect the outcome of that Match and should not be considered when determining whether a Violation has been repeated during the event.

  1. Updated RSC3c to clarify that preloads must be used

  2. Added rule RSC9, stating that there is no penalty for removing Scoring Objects from the field during Robot Skills Matches

  3. Updated VUT7c to clarify intent of Student eligibility

Students who meet the age requirements for V5RC and who are simultaneously earning credits toward a secondary school diploma and enrolled in post-secondary courses are not eligible to participate on a VURC Team.

  1. Minor typo/formatting fixes

Note: Revised specification drawings for this appendix have been delayed, and will be added here as soon as they are ready (likely by end of day on 9/4/24). Effective with the 9/3 update, the field layouts should match the color illustrations throughout this version of the game manual, including the revised tape lines and any ‘flipped’ stacks of rings.

The next manual update, Version 2.1 will occur on October 8th, 2024.

22 Likes

On October 8th, 2024, Version 2.1 of the V5RC High Stakes Game Manual was released, and the following changes were made:

  1. Updated Figures FO-1, FO-2 and FO-3 to specify which side of the Field should be facing the audience

  2. Revised the definition of Climb to clarify intent

A Robot action. A Robot is considered to be Climbing if it has intentionally grasped, grabbed, or attached itself to the bottom/black rung of the Ladder and/or a higher point of the Ladder. In most cases, this means a Robot mechanism will be reacting against multiple sides of a rung or vertical section in an effort to latch, clamp, or hook onto the Ladder. See SC7 for the criteria for a Robot to be considered to have Climbed to a Level.

  1. Updated SC3a to clarify intent of “encircled” Rings

a. The Ring is “encircling” a Stake. In this context, “encircling” means that any part of the Stake is at least partially within the volume defined by the inner edges of the Ring.

i. Each Ring can only be counted for points once, even in cases where the Ring qualifies as Scored on multiple Stakes.
ii. If multiple Stakes are encircled by the same Ring, Top Rings will not be awarded for those Stakes.
iii. If multiple Stakes are encircled by the same Ring and either of those Stakes is on a Mobile Goal that is Placed in a corner, that Ring should earn the points for the Stake that is not Placed in the Corner (i.e., that Ring should be Scored as 1 point, and not modified by the Corner). Intentionally causing a Ring to be Scored on multiple Stakes will, at minimum, receive a Minor Violation."

  1. Updated G9b to reflect September 3rd update

  2. Added a red box and Violation note to SG6 to clarify intent

If your Robot is carrying a Mobile Goal, you can’t manipulate other Mobile Goals until you put down the one you’re carrying. Period.

For the purposes of Match Affecting calculations that don’t fall within the previous note (e.g., tied a Match), each Ring Scored during a Possession violation should be considered worth a value of 2 points. These values are not added or removed from the actual score. As with all Match Affecting calculations, only the winner’s points should be considered. If these points were enough to change the offending Alliance’s score from a loss to either a win or a tie, it is Match Affecting. If they would have won the Match even without these points, it’s not Match Affecting. For example, a Robot is in Possession of three Rings and Scores one; this should be calculated as 2 points when considering whether it was Match Affecting (once the Robot is down to two Rings, they’re no longer in Violation of rule SG6).

  1. Updated R21 to include M2.5 x 8mm screws

  2. Revised R27 to eliminate mandatory enable/disable tests

The Robot must follow control directions provided by the VEXnet Field Controllers or Smart Field Control system. During the Autonomous Period, Drive Team Members will not be allowed to use their V5 Controllers. As such, Teams are responsible for programming their Robot with custom software if they want to perform in the Autonomous Period.

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

  1. Added two new bullet points to T19 to clarify the advancement procedure after the maximum number of ties in Elimination Matches is reached

c. In a "“Best of 1"” Elimination Round, the higher-seeded Alliance will advance and be declared the winner under the following guidelines.

i. After two (2) ties in a non-Finals Match
ii. After three (3) ties in a Finals Match.

d. In a "“Best of 3"” Elimination Round, the higher-seeded Alliance will advance and be declared the winner under the following guidelines.

i. After three (3) ties in a round in which neither Alliance has yet won a Match (0-0).
ii. After two (2) ties in a round in which one Alliance has won a single match (1-0). iii. After two (2) ties in a round in which each Alliance has won a single Match (1-1)."

  1. Updated T23 to include leagues

  2. Updated RSC4 to clarify intent

  3. Updated VUG2a to clarify that SC7a does not apply to all Robots in a VURC Match, and added a bullet point to clarify intent

A Robot that is contacting another Robot from their Team that meets all criteria of SC7 will receive the Climbing protections provided by rule SG9.

  1. Minor typo/formatting fixes

The next manual update, Version 2.2 will occur on December 3rd, 2024.

7 Likes

On December 3rd, 2024, Version 2.2 of the V5RC High Stakes Game Manual was released, and the following changes were made:

  1. Added rule S5 as a new rule, stating that each Student must have a completed participant release form on file

  2. Updated SC3b and removed the red box to clarify intent

The Stake does not exceed its total permitted number of Rings (see definition of Stake). In the event of too many Rings on a Stake, the “highest” Ring(s) will not be considered Scored on the Stake. If the “highest” Ring(s) cannot be determined, neither/none of those Rings will be considered Scored on the Stake.

  1. Expanded SC5a to clarify intent

a. The Mobile Goal base (any part of the Goal that is not the stake or the flexible top) is contacting the Floor or a white tape line.

  1. Updated SG1b and SG5 to clarify intent regarding preloads

Not contacting any Scoring Objects other than one (1) preload. See rule .

Each Robot gets one Ring as a preload. Prior to the start of each Match, each Robot must have a preload placed such that it is:

  1. Updated the note of SG7 to include portions of the Ladder

Note: Scoring Objects, Wall Stakes, and portions of the Ladder that contact or are positioned above the Autonomous Line are not considered to be on either side, and may be utilized by either Alliance during the Autonomous Period.

  1. Updated R9 to include Head Referees having final say in what is considered “non-functional”

  2. Added a note to R9a stating that anodizing / color changing of parts is no longer allowed in mainland China

  3. Added a new bullet point to T2 stating that Head Referees are not permitted to be Event Partners or a Judge Advisor for the same event

  4. Added a new bullet point to T6 clarifying that Robots arriving late to a Match are not allowed to be placed on the Field

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.

  1. Updated T9 to clarify that Time Outs are three minutes, and cannot be rejected by Head Referees or Event Partners

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.

  1. Updated RSC9 to better clarify how Scoring Objects should be returned to the Field

There is no penalty for removing Mobile Goals or Rings from the Field during a Robot Skills Match. A Mobile Goal that leaves the Field should be returned to a position on the Autonomous Line. Any blue Rings encircling the Stake on a Mobile Goal that leaves the Field should remain on that Stake when returned to the Field. All other Rings that leave the Field should be returned such that they satisfy clauses A-E of rule SG4.

  1. Updated VUG2d to clarify that a Robot contacting another Robot from their Team also receives protection

A Robot that is contacting another Robot from their Team that meets the definition of Climbing will receive the Climbing protections provided by rule SG9.

  1. Added new Significant Q&A boxes throughout the manual

  2. Minor typo / formatting fixes

The next manual update, Version 3.0 will occur on January 28th, 2025.

11 Likes

On January 28th, 2025, Version 3.0 of the V5RC High Stakes Game Manual was released, and the following changes were made:

  1. Revised rule <SC5c> to specify that the Mobile Goal Base should be breaking the plane of the Corners

  2. Deleted <SC7c>, allowing Robots to count as Climbed to a Level while in contact with Mobile Goals

  3. Updated <SC9> to give a Ring Scored on the High Stake a three (3) point bonus, in addition to the standard three (3) points earned for a Top Ring

A Ring Scored on the High Stake will also earn a bonus three (3) points in addition to the standard three (3) points earned for a Top Ring, for a total of six (6) points.

  1. Removed the Red Box from <SG3>

  2. Revised rule <SG6a> to specify that Rings Scored on a Stake are not included in a Robot’s Possession count

  3. Updated the Violation Notes of <SG6> to include both the winning and losing Alliances

Any egregious or clearly intentional Violation will be considered a Major Violation. Examples of “clearly intentional” Violations include, but are not limited to:

  1. Updated rule <SG10> to include scoring for the Autonomous Period

  2. Updated rule <SG11> to extend positive Corner protection to thirty (30) seconds

  3. Updated the required firmware version in <R15B> to VEXos 1.1.5

  4. Updated rule <T21> to clarify intent

Small tournaments have fewer Alliances. The number of Alliances for a given event is determined as follows, except in extraordinary circumstances with the permission of the RECF Regional Support Manager.

  1. Revised <VUG2b> and <VUG2d> to reference <SC7>, and clarify intent

A Robot that is contacting another Robot from their Team that meets the definition of Climbing and/or the criteria of will receive the Climbing protections provided by rule .

  1. Added new Significant Q&A boxes throughout the manual

  2. Minor typo / formatting fixes

The next manual update, Version 4.0 will occur on April 2nd, 2025.

15 Likes

On April 2nd, 2025, Version 4.0 of the V5RC High Stakes Game Manual was released, and the following changes were made:

  1. Added Section 8, containing important information for the 2025 VEX Robotics World Championship

  1. Updated the definition of Major Violation to include strategic violations

  1. Revised <SC8> to clarify that Matches at the VEX Robotics World Championship will use the same Autonomous Win Point criteria as Worlds-qualifying events

  1. Updated <G7> to clarify intent of Robots Entangling themselves with Field Elements

Robots may not intentionally grasp, grapple, hook, attach to, or otherwise Entangle with any Field Elements other than the Ladder.

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 in locations other than the Ladder.


  1. Updated <SG7> and added a new bullet point to clarify intent regarding interfering with an opponent’s autonomous routine

Don’t cross the Autonomous Line, and don’t interfere with your opponents’ actions.

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

i. An opponent Robot that isn’t interacting with either the Autonomous Line or objects that begin the Match positioned above or in contact with the Autonomous Line.
ii. Rings or Mobile Goals that begin the Match on the other side of the Autonomous Line.

Intentional, strategic, or egregious violations, such as intentional contact with an opposing Robot while contacting the foam tiles on the opposing side of the Autonomous Line or the interactions described in clause B, will be considered Major Violations and result in a Disqualification for the Match.


  1. Updated <SG9> to include protection for vertical segments of the Ladder, and match previous manual updates

If a Robot is contacting the horizontal rungs or vertical segments of the Ladder facing their Alliance Station, they should generally be considered in a more “offensive” or “safe” position.


  1. Updated <R3ci> and added <R3cii> to clarify intent

If a Robot is determined to be in Violation of a Robot rule before a Match begins, the Robot will be removed from the Field. The Robot may remain at the Field so that the Team does not get assessed a “no-show” (per <T5>).

If a Robot is determined to be in Violation of a Robot rule before Elimination Matches begin in a Division or “the Dome” at the VEX Robotics World Championship, the Team may be removed from their Alliance and be ineligible to participate in Elimination Matches.


  1. Revised <T5> to state that a Robot must report to a Match, or the Team will be considered a “no-show”

A Team’s Robot should attend every Match. The Team’s Robot must report to the Field for the Team’s assigned Match, even if the Robot is not functional. If the Robot is not at the Field at the start of a Match, the Team will be considered a “no-show” and receive zero (0) WPs, AWPs, APs, and SPs.

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


  1. Updated <T6c> to account for changes made to <T5>

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


  1. Updated <T13> to clarify that Qualification Matches may only start early if all Teams Robots and volunteers are present

  1. Added a new bullet to <T18> to provide guidance for a Team that is removed from an Alliance before Division Elimination Matches begin at the VEX Robotics World Championship

If a Team is removed from an Alliance through <R3ci> before Division Elimination Matches begin at the VEX Robotics World Championship, the next-highest-ranked Team that is available and not already part of an Alliance will be assigned to take their place in that Alliance.


  1. Revised <T19> to exempt overall finals from multi-division events

  1. Added two new bullets to <RSC2> stating that Robot Skills Matches are only available to Teams who participate in Qualification Matches

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


  1. Added <VUT8>, clarifying the number of Teams that participate in Elimination Matches in VEX U

  1. Added new Significant Q&A boxes throughout the manual

  1. Minor typo fixes
8 Likes