This thread will be used to publish updates to the V5RC Override 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 V5RC Override Q&A.
On June 4th, 2026, Version 0.2 of the V5RC Override Game Manual was released, and the following changes were made:
- Updated a typo in the Game Design Philosophy to clarify that the Endgame is 10 seconds long
- Revised <SC2>, <SC3>, <SC4>, <SC5>, <SC8>, <SG9>, <SG10>, <RSC3>, <VUG6> and their corresponding figures for clarity, in regards to Pins that are Placed / Scored
- Updated <R11> to clarify intent
Motors are limited for Subsystem 2 (see <R1>). Robots may use any combination of V5 Smart Motors, 11W (276-4840) and/or 5.5W (276-4842), in Subsystem 2 within the following criteria:
a. The combined power of all motors in Subsystem 2 must not exceed 55W.
b. Motors used in Subsystem 2 cannot provide power to any mechanism that is not a part of Subsystem 1.
i. Motors in Subsystem 2 cannot be toggled, engaged, or configured such that they are capable of providing power to any part of the Robot that is not a part of Subsystem 1.
c. Teams may be required to demonstrate what each motor is capable of powering on their Robot during inspection in order to satisfy this requirement.
- Updated <R23a> to allow anodizing, painting, dyeing, or otherwise changing the color of any legal VEX parts (other than for official events held in mainland China)
- Updated <T6> to add white tape in place of blue/red tape for Load Zones as a permissible Field modification
- Revised tiebreakers in <T22>
i. Quantity of Scored Pins
ii. Number of Toggles set to a color other than yellow
- Added figures to Section 6 to show the starting configuration of a VEX U Head-to-Head Match
- Updated <VUG4> to clarify that both Cups and Pins may be introduced into the Loaders in VEX U Matches
- Added a note to <R11> and <VUR11> to clarify that the 55W drivetrain motor restriction does not apply to VEX U
- Added new drawings to Appendix A for Toggle starting orientation, and AprilTag numbering locations
- Added new definitions for Plowing, Possession and Scored to Appendix B
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.
Possession β A Robot / Scoring Object status. A Scoring Object is considered Possessed by a Robot if a Robotβs change in direction would result in controlled movement of the Scoring Object. This typically requires at least one of the following to be true:
β’ The Scoring Object is fully supported by the Robot.
β’ The Robot is moving the Scoring Object in a preferred direction with a concave face of the Robot (or inside of a concave angle formed by multiple mechanisms/faces of the Robot).
β’ The Robot is holding the Scoring Object against the Floor or a Field Element.
Scored - A Scoring Object status. See <SC3>.
- Other minor typo / formatting fixes
The next manual update, Version 1.0, will occur on July 2, 2026.
On July 2nd, 2026, Version 1.0 of the V5RC Override Game Manual was released, and the following changes were made:
- Revised <SC4> to provide clarity
- Updated <SG2a> and its red box to clarify that the rule only applies during the Match
The Robot can never be larger than 24β wide or 24β long at any point during the Match (must fit within a 24β x 24β square horizontal footprint).
- Updated <SG3> to clarify Endgame expansion limits
- Updated <SG4> to penalize only intentional remove of Scoring Objects, and to consider Scoring Objects resting on top of the Field Perimeter as being out of the Field
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.
a. A Scoring Object that comes to rest on top of the Field Perimeter is considered to have left the Field.
- Revised the wording of <SG9> to provide better interaction examples
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:
- Making contact with the Goal
- Making contact with Scoring Objects stacked on the Goal
- Adding or removing Scoring Objects (Placed or otherwise)
- Strategically covering the goal in a manner that prevents additional Scoring Objects from being Placed"
- Updated <SG10> to clarify intent
Placed Scoring Objects cannot be removed from neutral Goals.
- Rewrote <SG12> to change the hard limit on vertical expansion during the Endgame, to a soft limit with verbal warnings
- Added rule <SG13> to introduce Load Zone protections
- Revised <R24f> to add structurally non-homogeneous plastics to list of prohibited materials
- Added bullet points to <T6> regarding custom solutions for mounting Toggles on metal Field Perimeters and Alliance Station dimensions / positioning as permissable Field modifications
- Removed existing rule <VUG7> and rewrote it for VEX U Load Zone protections
- Added a new definition for Load Zone
Load Zone - An infinitely tall three-dimensional volume bounded by the inner edges of the Field Perimeter and the outer edges of the red or blue tape lines surrounding each Loader.
- Updated Figure T-1 to properly display the parts considered to be part of the Toggle
- Added a new drawing to Appendix A to show an example of a custom Toggle mount for metal Field Perimeters
- Updated Violation Notes for rules <SG4>, <SG9>, <SG10>, <SG12> and <SG13>
- Other minor typo / formatting fixes
The next manual update, Version 1.1, will occur on August 6, 2026.