On June 27th, 2023, Version 1.0 of the VRC Over Under Game Manual was released, and the following changes were made:
- Updated point 1b in the definition of Elevated to state that a Robot must be contacting any portion of the Barrier that is on their Alliance’s side of the Neutral Zone
Any portion of the Barrier that is on their Alliance’s side of the Autonomous Line (i.e. the three black PVC pipes that are attached directly to their Alliance’s Elevation Bars).
- Added point 4 to the definition of Elevated to state that a Robot may not be contacting an Alliance partner Robot that is not considered Elevated
The Robot is not contacting an Alliance partner Robot that is not considered Elevated
- Added a note to SC7 to clarify intent
Note: Point “a” refers specifically to the actions of the Robot who started near the Match Load Zone in question. To continue the example above if Blue Robot 2 were to launch a Triball into the bottom-left Match Load Zone after one was removed by the red Robot, this would not impact the red Alliance’s eligibility to receive the Autonomous Win Point.
- Added a note to SG1 and RSC2e to clarify that the Triballs beginning in Match Load Zones may be repositioned by Teams. The note in G9 was also updated to reflect this change
Note: The Triballs which start in each Match Load Zone must be contacting the Match Load Zone at the start of the Match. However, they may be repositioned during pre-Match setup by the Team whose Robot is using the Starting Tiles adjacent to that Match Load Zone. For example, in Figure 26, Red Robot 1 would be permitted to reposition the Triball in the lower-left red Match Load Zone.
- Revised SG3 to state that any Triballs that leave the field will be returned to the nearest Match Load Zone
Triballs that leave the field during Match play, whether intentionally or unintentionally, will be returned to the field by being placed in a Match Load Zone nearest the point at which they exited.
a. Referees will return Triballs to the field when it is deemed safe to do so, at their discretion.
b. This action is not considered a “Match Load”; i.e., the stipulations in rule SG6 do not apply. For example, the Triball cannot be placed directly onto a Robot.
c. Incidental contact with other Triballs that are already in the Match Load Zone may occur, although referees will make a concerted effort not to do so.
d. The Triball may be placed on top of other Triballs that are already in the Match Load Zone if necessary, e.g., if Triballs are already covering the entire Match Load Zone foam tile region.
e. At their discretion, referees may also direct a nearby Drive Team Member or other volunteer to return the Triball to a specific Match Load Zone. However, this should never be done by Drive Team Members proactively without referee acknowledgment.
- Added a Violation note to SG9 to clarify intent
Intentionally using a Triball to interfere with the Match Load Zone that is used for an opponent’s Autonomous Win Point may be considered an example of exploiting G17 for strategic gain. If the opponent has already successfully retrieved their Triball when the Violation occurs, then this will be considered a Minor Violation of SG9, and the Autonomous Win Point is not affected (per SC7). If the opponent has not retrieved their Triball, then this will be considered a Major Violation. Intentional, strategic, or egregious violations, such as intentional contact with an opposing Robot while contacting the foam tiles past the Neutral Zone, will be considered Major Violations.
-
Added SG11d, stating that Robots may not contact the Short Barriers adjacent to the opposing Alliance’s Elevation Bars during the last thirty (30) seconds of the Match
-
Updated T9 to provide clarity regarding when Time Outs may be used
Each Elimination Alliance gets one Time Out. Each Alliance may request one (1) Time Out during the Elimination Bracket. The Time Out will be served prior to the Alliance’s next upcoming Match. Alliances must request their Time Out between Elimination Matches, as permitted by the Head Referee and Event Partner; they may not use their Time Out during a Match, for another Alliance’s Match, or after they have been eliminated.
- Updated T10 to provide a Goal height tolerance, and to provide further clarity
“Be prepared for minor field variance. Field Elements and Triballs may vary from specified locations / dimensions; Teams are encouraged to design their Robots accordingly. Please
make sure to check Appendix A for more specific nominal dimensions and tolerances.
a. Field Element tolerances may vary from nominal by up to ±1.0”
b. The opening of the Goal between the PVC pipe and the foam field tiles has a dimensional tolerance of +0.25"” / -0.00"“.
c. Triball weights may vary from nominal by up to ±20 grams.
d. Triball placement at the beginning of Matches may vary from nominal by up to ±1” (25.4mm).
e. The rotation of Triballs is not specified.
f. The only placement requirement for the Triballs that begin in each Match Load Zone are that they are contacting the Match Load Zone (i.e. the gray foam tile). See SG1.”
- Added a Violation note to RSC1 to clarify intent
In the Robot Skills Challenge, the standard definition of Match Affecting does not apply, since there is no winner and loser. When evaluating whether a rule Violation should be classified as a Major or Minor Violation in the context of this criteria, the term “score affecting” can be substituted for “Match Affecting”. A Violation is considered “score affecting” if it results in a net increase of that Team’s score at the end of the Match.
- Added Appendix C for VEX U
Note: The remaining VEX U robot rules will be released in a future game manual update. For the purpose of early-season designs, prototyping, and scrimmages, the rules from the 22-23 VEX U Game Manual may be used.
- Minor typo / formatting fixes
The next manual update, Version 2.0, will occur on August 1st, 2023.