VRC Over Under Game Manual Updates

VEX Robotics Competition Discussion VRC > Over Under (23/24)
1

This thread will be used to publish updates to the VRC Over Under Game Manual.

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

9 Likes
2

On June 13th, 2023, Version 0.2 of the VRC Over Under Game Manual was released, and the following changes were made:

  1. Rescheduled the VEX U Appendix release for the June 27th manual update.

  2. Updated the definition of Elevation Tier to clarify that Robots must be ā€œfully above the white lineā€ of the Height Guide to receive credit for that Elevation Tier

A status that represents an Elevated Robotā€™s height off of the field at the end of the Match. A Robotā€™s Elevation Tier is measured by placing the Height Guide vertically next to an Elevated Robot and determining which letter-labeled segment of the Height Guide the lowest point of the Robot falls within. Each white line on the Height Guide is considered to be part of the letter-labeled segment immediately below that line. In other words, the Robot must be visibly ā€œabove the lineā€ in order to move into the next Elevation Tier. See Figure 13.

  1. Added a note to SC3, clarifying that a Triball Scored in a Goal is not also considered Scored in that Goalā€™s Offensive Zone.

  2. Revised the note in SG5 to clarify that the net cannot be lifted to score / de-score

Note: Lifting the net structure in an attempt to add or remove Triballs is considered a Violation of , and may also be considered a Violation of , and/or at the Head Refereeā€™s discretion.

  1. Updated T5 to include Autonomous Win Points

A Robot or a Student member of the Team must report to the field for the Teamā€™s assigned Match, even if the Robot is not functional. If no Student Drive Team Members report to the field, the Team will be considered a ā€œno-showā€ and receive zero (0) WPā€™s, AWPā€™s, APā€™s, and SPā€™s.

  1. Updated T8 to clarify that a Team that receives a Disqualification in a Qualification Match also receives a score of (0) for the Match

  2. Added an REC Library article link to R7 to provide clarity

  3. Updated Robot Skills Challenge Ranking 9a to Number of Triballs Scored in Goals

  4. Minor typo / formatting fixes

Quick note on the VEX U Appendix being moved again. The reason behind the delay is due to some small, impactful changes being made to the Robot and gameplay rules. Be assured that we want to make sure that all these changes are well thought out, and bring the best possible build experience to our VEX U Teams.

The next manual update, Version 1.0, will occur on June 27th, 2023.

13 Likes
5

On June 27th, 2023, Version 1.0 of the VRC Over Under Game Manual was released, and the following changes were made:

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

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

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

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

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

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

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

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

  1. 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.ā€

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

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

  1. Minor typo / formatting fixes

The next manual update, Version 2.0, will occur on August 1st, 2023.

10 Likes
6

On July 11th, 2023, an unscheduled update (Version 1.1) of the VRC Over Under Game Manual was released, and the following changes were made:

  1. Added remaining VEX U Robot rules.

The next manual update, Version 2.0, will occur on August 1st, 2023.

7 Likes
7

On August 1st, 2023, Version 2.0 of the VRC Over Under Game Manual was released, and the following changes were made:

  1. Updated G8 to clarify the legality of items brought to the field by Drive Team Members

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 G8:
-Materials used before or after a Match, such as a pre-Match alignment aid, or a carrying case for
Robots / Controllers
-Strategic aids, such as a whiteboard or clipboard
-Earplugs, gloves, or other personal accessories

  1. Updated R22a and added a note to clarify pneumatic reservoir legality

Teams may use a maximum of two (2) legal VEX pneumatic air reservoirs on a Robot. The Air Tank 200mL (included in the 276-8750 V5 Pneumatics Kit) and the legacy (pre-2023) reservoir are both considered legal reservoirs.

Note: From a rules perspective, parts found in the V5 Pneumatics Kit (276-8750) and legacy (pre-2023) pneumatic parts may be used interchangeably. This rule will be updated shortly with a link to an updated Legal Pneumatics summary in the VEX Library, which includes additional pneumatics information.

  1. Updated T1e to clarify that a Head Referee may only watch one Match at a time

Every Qualification Match and Elimination Match must be watched by a Head Referee. Head Referees may only watch one Match at a time; if multiple Matches are happening simultaneously on separate fields, each field must have its own Head Referee.

  1. Updated T11 to address using PVC to replace a damaged section of a Goal

  2. Updated figure 41 to fix the position of misaligned Triballs

  3. Minor typo / formatting fixes

The next manual update, Version 2.1, will occur on October 3rd, 2023.

9 Likes
8

On October 3rd, 2023, Version 2.1 of the VRC Over Under Game Manual was released, and the following changes were made:

  1. Added a new definition of Plowing

Plowing - A Robot / Triball status. A Robot is considered to be Plowing Triballs if the Robot is intentionally moving them in a preferred direction with a flat or convex face of the Robot.

  1. Updated the definition of Possession to clarify intent and explain relation to Plowing

Possession - A Robot / Triball status. A Robot is considered to be Possessing a Triball if a Robotā€™s change in direction would result in controlled movement of the Triball. This typically requires at least one of the following to be true:

  1. The Triball is fully supported by the Robot.
  2. The Robot is moving the Triball 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).
    [red box]
    The difference between Possession and Plowing is analogous to the difference between the terms ā€œcontrollingā€ and ā€œmovingā€.
  1. Updated SC5 to clarify the criteria of scoring Alliance Triballs

a. To be eligible for points, Alliance Triballs must not be contacting any Robots of the same color Alliance as the Triball. Contact with Robots of the opposing Alliance is irrelevant (i.e., rules SC3a and do not apply to Alliance Triballs).

  1. Updated G1 to include a link to the Code of Conduct process

  2. Updated G5 to clarify that Robots may not use external influences to satisfy starting size limits

Note: Using external field influences, such as Preloads or the field perimeter wall, to maintain a Robotā€™s starting size is only acceptable if the Robot would still satisfy the constraints of R4 and pass inspection without these influences.

  1. Added a red box to SG5 allowing Teams an opportunity at the Head Refereeā€™s discretion to untangle themselves from the net if it occurs during the Autonomous Period

If this (entanglement) occurs during the Autonomous Period, the Head Referee should assess the severity of the Entanglement once the Autonomous Period ends. If they determine that the risk of field damage is low, they have the option to grant a 5-second ā€œgrace periodā€ on this rule at the beginning of the Driver Control Period.
This exception is only permitted at the Head Refereeā€™s discretion, and is only valid if it is verbally communicated to Drive Team Members before the start of the Driver Control Period. If the Team is unable to free their Robot after 5 seconds, this rule will take effect and the Robot must be Disabled.

  1. Updated SG6 with a new bullet point, image, and notes to clarify intent

2b: Momentarily / accidentally losing contact with the Match Load Zone or Match Load Bar is permissible, provided that the Robot is still ā€œbreaking the planeā€ of the inside edge of the Match Load Bar.
[red box]
The intent of part 2b is to provide some ā€œbenefit of the doubtā€ to Teams for incidental Violations that may occur during rapid Match Loads. For the purposes of this rule, ā€œmomentaryā€ refers to a duration of 2 seconds or less.
Part 2a should still be the primary driver of Robot design; part 2b is not intended to permit a design which relies solely on ā€œbreaking the planeā€ with no intent of the Robot ever contacting the Match Load Bar. In other words, it is still the Teamā€™s responsibility to ensure that a Head Referee can clearly determine their legality ā€œat a glanceā€ during a Match.

  1. Updated SG11 to clarify intent of non Match Affecting Violations

Regarding points ā€œaā€ and ā€œdā€: If no opponent Robots are in the process of Elevating, then most incidental or momentary contact is unlikely to be Match Affecting, and should only be considered a Minor Violation.
If a Violation results in opponent Robot damage, or otherwise impedes an opponentā€™s Elevation, then it should be assumed that they would have reached the highest possible Elevation Tier when determining Match Affecting implications.

  1. Updated R7b to clarify that greasing V5 Smart Motor cartridges is prohibited

Any non-aerosol-based grease or lubricating compound, when used in extreme moderation on surfaces and locations that do NOT contact the playing field walls, foam field surface, Triballs, or other Robots. Grease or lubricant applied directly to V5 Smart Motors or Smart Motor cartridges is prohibited.

  1. Updated T11to clarify intent of repairing a broken net

Using tape, zip ties, or string to repair a damaged Net

  1. Updated Appendix A to include allowed field modifications

  2. Updated VUG1 to clarify that Teams may adjust the starting position of Alliance Triballs per SG1

VEX U teams may adjust the starting positions of both of their Alliance Triballs as described in the note following rule SG1 (i.e., the red Team may reposition the red Triballs, and the blue Alliance may reposition the blue Triballs).

  1. Updated VUG5 to clarify that Alliances may only use the Match Load Zone adjacent to the Robot Starting Tiles during the Autonomous Period of a Head-to-Head Match

During the Autonomous Period of a Head-to-Head Match, each Alliance may only use the Match Load Zone that is adjacent to that Allianceā€™s Robot Starting Tiles. This restriction does not apply to Autonomous Coding Skills Matches or Driver-Controlled periods.

  1. Updated VUR3 to allow molding of non-metals

  2. Updated the tables in VUR4 and VUR5 to clarify intent

  3. Added Appendix D (VEX AI Robotics Competition)

  4. Minor typo / formatting fixes

The next manual update, Version 2.2, will occur on December 5th, 2023.

16 Likes
9

On December 5th, 2023, Version 2.2 of the VRC Over Under Game Manual was released, and the following changes were made:

  1. Added a red box to the definition of Holding to clarify intent

If the Head Referee determines that the opponent Robot is not attempting to move or escape, then it is not considered Pinned or Trapped. This commonly occurs when receiving Match Loads, or if the Robot has malfunctioned and lost the ability to move.

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

  1. Updated Figure 16 to provide clarity

  2. Updated SC7 to clarify intent in rewarding the Autonomous Win Point

An Autonomous Win Point is awarded to any Alliance that ends the Autonomous Period with the following tasks completed:

b. Scored at least one of their own Alliance Triballs in the Allianceā€™s own Goal.

  1. Updated to clarify clamping onto Match Load Bars

Robots may not intentionally grasp, grapple, or attach to any Field Elements. Strategies with mechanisms that react against multiple sides of a Field Element in an effort to latch or clamp onto said Field Element are prohibited. The intent of this rule is to prevent Teams from both unintentionally damaging the field and/or from anchoring themselves to the field.
Note: An Allianceā€™s own Elevation Bars and Match Load Bars are exceptions to this rule, i.e. there is no penalty for clamping onto them.

  1. Added a note to G11 to clarify that Robots may be manually disabled during the Autonomous Period

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 . See this Q&A post for more details: <SG5> Net Entanglement in Auton : Robot Events

  1. Updated SG3 to clarify that Triballs may not be intentionally / repeatedly removed from the field

Teams may not intentionally remove Triballs from the field. Although Triballs may accidentally leave the field, doing so intentionally or repeatedly would be a Violation of this rule.
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, when it is deemed safe to do so. "

  1. Updated SG6 to clarify intent, and provide links to official Q&A clarifications
  1. By placing the Match Load gently into / onto a Robot from the Drive Team Memberā€™s Alliance.

Teams are responsible for the actions of their own Robots at all times, including while interacting with Match Load strategies / mechanisms that could be deemed unsafe. A higher ā€œbenefit of the doubtā€ will be granted to Teams who can demonstrate any precautions or considerations that have been taken to minimize this risk, e.g., during inspection or a practice match. See this Q&A post for more information: [Official GDC Q&A Post] Is my hypothetical Match Load design / strategy allowed? : Robot Events

d. The following actions are not considered ā€œplacing the Match Load gently onto a Robotā€, and are not permitted. Egregious, intentional, or repeated instances of the following actions may become Violations at the Head Refereeā€™s discretion.

  • ā€œThrowing,ā€ ā€œrolling,ā€ or otherwise imparting enough energy onto a Triball such that its motion after release is mostly defined by the human (instead of the Robot).
  • Physically interacting with the Robot, such as pushing down on a mechanism (using a sensor to detect a Triball is permitted).
  • Placing the Match Load such that it is in contact with anything other than the Robot, such as the field perimeter or gray foam tiles.

Part 2d is intended to provide a reasonable, limited scope of prohibited Match Load actions. See this Q&A post for more information: [Official GDC Q&A Post] Is my hypothetical Match Load design / strategy allowed? : Robot Events

  1. Added a new violation note and note to SG7 to clarify that excess Triballs should be removed in a non-scored position

ā€œRemovingā€ excess Triballs directly into a Teamā€™s own Goal

Note 2: When removing excess Triballs, the safest maneuver will always be to remove them into an opponentā€™s Offensive Zone, or into any Match Load Zone. Head Referees may provide more specific direction at their discretion, depending on the context of the Match and the circumstances that led to the excess Possession. See the following Q&A posts for more information:
Forced into Possession Penalty : Robot Events
<SG7> clarification : Robot Events

  1. Updated SG11 to clarify intent, and explain the process of assigning an Elevation Tier if no other Robots are Elevated

If an egregious Violation results in opponent Robot damage, or otherwise severely impedes an opponentā€™s Elevation, then it should be assumed that the Violation was Match Affecting if the opposing Alliance loses the Match by 20 points or less.

  1. Updated R7 to include SD Cards installed in the V5 Robot Brain

  2. Updated R9 to clarify that license plates must be placed on opposing sides of the Robot

This Team number must be displayed on a minimum of two (2) opposing sides of the Robot using License Plates.

  1. Updated T23 to clarify intent
  1. A VEXnet Field Controller controlled by Tournament Manager, which connects to a Controllerā€™s competition port via ethernet cable.
  2. A V5 Event Brain controlled by Tournament Manager, which connects to a Controller via Smart Cable."

Note: Official Qualifying Events may only use the official, unmodified version of Tournament Manager for field control, along with approved hardware and networking solutions found in the REC Library.
Note 2: Add-ons that abide by the TM Public API guidelines [link] are permitted. Once add-ons are enabled, the software is no longer supported by the REC Foundation, VEX Robotics, or DWAB Technologies; any necessary troubleshooting will be done at the userā€™s own risk."

  1. Updated Sheet 15 in Appendix A to show the correct field layout

  2. Updated RSC4 to clarify that SG8 does not apply for Robot Skills Matches

e. Rule does not apply in Robot Skills Matches (i.e., Robots may freely break the plane of either Goal at any time).

  1. Updated VUR1 to include VUR14

  2. Updated VUR4 to include C-Channel and U-Channel

  3. Removed Bearings from VUR9, and added them to a new rule, VUR14 to clarify intent.

Teams may use commercially available fastener hardware on their Robot. For the purposes of this rule, a ā€œfastenerā€ is a part designed and used to join or secure together two otherwise legal parts. Legal examples include (but are not limited to):

  • Screws, nuts, rivets
  • Hinges, pins, rod ends, threaded rods, hose clamps
  • Ancillary fastener accessories, such as washers or spacers
  • Adhesives such as epoxy, glue, or tape (when used to join together two parts)

If the primary function of the part is not ā€œfasteningā€, then , , and/or take precedence over this rule. Illegal examples include (but are not limited to):

  • A prefabricated non-VEX wheel, even though it may technically connect tread to a shaft
  • 80/20 extrusion; other items get ā€œfastened to itā€, it is not the part doing the ā€œfasteningā€
  • Using grip tape to improve wheel traction

VUR14 - Teams may use commercially available bearings on their Robot. For the purpose of this rule, a ā€˜bearingā€™ is a part that supports external loads, reduces friction, and improves efficiency by facilitating smooth dynamic motion between components. Legal examples include (but are not limited to):

  • Parts supporting rotational motion: radial bearings, roller bearings, thrust bearings, needle bearings, one-way bearings, bushings, etc.
  • Parts supporting linear motion: linear bearings, linear slides, drawer slides, etc.
  1. Updated VAIT2 to clarify intent

High School Students, as described by the definition of Student. This includes Middle School Students who are ā€œplaying upā€ and competing as High School Students.

  1. Minor typo / formatting fixes

The next manual update, Version 3.0, will occur on January 30th, 2024.

10 Likes
10

On January 30th, 2024, Version 3.0 of the VRC Over Under Game Manual was released, and the following changes were made:

  1. Updated the definition of Goal to provide clarity

As a scoring and gameplay element, the ā€œGoalā€ refers specifically to the three-dimensional volume bounded by a vertical projection of the outermost PVC pipes onto the field and below the surface of the net.

  1. Removed the yellow Elevation Bar Cap from VRC and Skills Matches. This change does NOT apply to VEX U, or VAIRC

  2. Updated various figures throughout to remove the Elevation Bar Cap

  3. Updated the definitions of Elevation Bar Cap and Elevated

  4. Updated SG6 with a new table and violation notes to clarify intent

a. For the purposes of Match Affecting calculations, each illegal Match Load should be considered worth a value of 2 points. These values are not added to the actual score. As with all Match Affecting calculations, only the winnerā€™s points should be considered.

b. For the purposes of this rule, the following guidelines should be used for escalating repeated Minor Violations to a Major Violation during Qualification Matches:

  • Six or more illegal Match Loads in a single Qualification Match.
  • Three or more Qualification Matches with at least one illegal Match Load (i.e., the third Match and all subsequent Matches with a Violation).

c. For the purposes of this rule, only Match Affecting Violations should be considered during Elimination Matches (i.e., repeated SG6 Minor Violations in Elimination Matches do not compound to Major Violations).

  • Point B-1 does not explicitly apply during Elimination Matches, although the risk of illegal Match Loads becoming Match Affecting still inherently increases as the quantity of Match Loads increases.
  • Point B-2 does not apply during Elimination Matches.
  1. Updated SG9 to clarify intent

Robots may not contact foam tiles, Triballs, or Field Elements that are entirely on the opposing Allianceā€™s side of the Neutral Zone, or entirely in the opposite Offensive Zone from which they began the Match.

  1. Updated R18f to clarify intent

Plastic sheets sold by VEX are considered ā€œplasticā€ in the context of this rule, and are subject to the same limitations as ā€œoff-the-shelfā€ plastic sheets. Examples include the 276-8340 PET sheets, and the 217-6626 / 217-6627 polycarbonate sheets."

  1. Updated SG11 to reduce the Short Barrier protection time from 30 seconds to 15 seconds

  2. Updated the VEX U Field Setup rule modifications to specify that Elevation Bar Caps must be used

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

21 Likes
11

On April 2nd, 2024, Version 4.0 of the VRC Over Under Game Manual was released, and the following changes were made:

  1. Added Section 5, containing important information for the 2024 VEX Robotics World Championship

  2. Added new grey boxes to various rules throughout the manual to note significant Q&Aā€™s that Teams should be aware of before the VEX Robotics World Championship

  3. Updated the definitions of Offensive Zone and Elevation Tier to clarify boundaries

The boundary of the Offensive Zones below the Elevation Bars follows the shape of the interlocking tabs of the Field Tiles.

Elevation Tier is measured by placing the Height Guide vertically next to an Elevated Robot and determining which letter-labeled segment of the Height Guide the lowest point of the Robot falls within (excluding any portion of the Robot inside the volume of the Elevation Bar).

  1. Added a new bullet point and note to SC2 to clarify intent

Any rule Violations, Major or Minor, during the Autonomous Period will result in the Autonomous Bonus being awarded to the other Alliance. If both Alliances violate rules during the Autonomous Period, no Autonomous Bonus will be awarded.

Note: In general, minor Violations of SG rules that occur during the Autonomous Period should only affect the outcome of the Autonomous Period (i.e., the Alliance canā€™t win the Autonomous Bonus or earn an Autonomous Win Point) and should not be considered when determining whether a Violation has been repeated during the event. This does not apply to rule SG6; any Match Loads introduced during the Autonomous Period of a VRC head-to-head Match must be recorded as a Violation and assessed to determine whether or note the Violation was Major and/or Match Affecting.

If a Head Referee determines that minor Violations of rules SG2, SG3, SG5, SG7, SG8, SG9, or any ā€œGā€ rule during the Autonomous Period were intentional/strategic rather than accidental/situational, they should be recorded as Minor Violations and considered when determining whether a Violation has been repeated during the event.

  1. Updated G8 to clarify intent

To ensure that Drive Team Members are aware of verbal calls or warnings during a Match (as an application of rules T1, G1, S1, and G3), powered headphones, earbuds, and passive earpieces connected to electronic devices cannot be worn/used in the Alliance Station except as required by an officially approved accommodation request.

  1. Updated SG2 to clarify intent

This limit refers to ā€œhorizontalā€ expansion measured between any two points of the Robot, including diagonals, relative to the playing field (i.e., it does not ā€œrotate with the Robotā€).

  1. Added a red box to SG10 to clarify Neutral Zone interactions during the Autonomous Period

"The Neutral Zone is intended to be a zone that Robots from both Alliances can utilize during the Autonomous Period. This will inevitably result in Robot-on-Robot interactions, both incidental and intentional. The overarching intent of SG10 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, who tips over every time they enter the Neutral Zone and contacts an opponent, should not attempt to claim a violation on their opponent.

Clause ā€œbā€ of SG10 is intended to provide a ā€œbenefit of the doubtā€ tiebreaker for interactions which require a Head Referee judgment call beyond clause ā€œaā€. If the interaction does not require a judgment call, it is not intended to be an automatic ā€œget out of jail freeā€ card. This could refer to interactions in which one Alliance is clearly at fault, as well as interactions which would clearly be a ā€œno-callā€ if they had occurred during Driver Control. 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.

  1. Updated R6 to include microSD cards for in-Match file storage

Third-party microSD card for in-Match file storage, as supported by the VEX API.

  1. Updated R12a to clarify intent

This limit applies to all motors on the Robot, even those which are not plugged in.

  1. Updated R14c to clarify that EXP Smart Motors (5.5W) are also included

Clauses ci-civ also apply to EXP Smart Motors (5.5W).

  1. Updated T7b to note that the V5 white screen error is no longer a permitted cause for a replay

Note: Beginning with the 2024 VEX World Championship, the V5 white screen error is no longer a permitted cause for a replay. More information about this error can be found here: https://kb.vex.com/hc/en-us/articles/18341400395156-Troubleshooting-the-V5-Brain-White-Screen-Error

  1. Added a note to Appendix A to state that Goals will be secured to field risers at the VEX Robotics World Championship

  2. Minor typo / formatting fixes

5 Likes