This thread will be used to publish updates to the V5RC Push Back 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 Push Back Q&A.
On June 5th, 2025, Version 0.2 of the V5RC Push Back Game Manual was released, and the following changes were made:
Added a link to the obsoleted game manual version in the āUpdatesā section. This link serves as a way to reference the previous manual during the 7-day grace period following each manual update. The link will be only be active during these timeframes and will be disabled once each grace period ends.
Clarified that the most current version of the English language PDF of the manual (this document) takes precedence over any other supplemental or translated material
Updated the definition of Lifting to clarify intent
Preventing a Robot that is already off of the Floor from returning to the Floor may also be considered Lifting or Trapping.
The Control Zone for a Long Goal consists of the space between (but not including) the white tape lines (highlighted in green in Figure CZ-1), and holds up to three (3) Blocks.
Revised <SC2> to clarify that Blocks must be in contact with the inside surface(s) of the plastic trough to be considered as Scored
Updated <GG1a> to clarify that devices are allowed in the Alliance Station, but may not be used for any reason during a Match. Using devices for translation purposes post-Match is allowed
Updated <GG13> to clarify that an Alliance will be ineligible to receive an Autonomous Win Point if they commit a Violation during the Autonomous Period
Any Violations, Major or Minor, committed during the Autonomous Period will result in the Autonomous Bonus being automatically awarded to the opposing Alliance and make the violating Teamās Alliance ineligible for the Autonomous Win Point."
The Robot can never be larger than 22" wide or 22" long (must always be able to fit within a hypothetical 22"x22"x22" cubic sizing box).
For the purpose of this rule, all Blocks that begin the Match in groups that cross the Autonomous Line are considered to be in contact with the Autonomous Line.
Added a bullet to <SG9> to clarify that Blocks that bounce out of a Loader while being Loaded into the Field should not be considered a Violation
Updated <SG10> to clarify intent
Robots are not permitted to directly contact Blocks that are fully within enclosed sections of Long Goals, but may add or remove Blocks from open sections of Goals at any time during a Match.
License plates should be mounted in locations that remain stationary on the Robot during a Match (e.g., not on a rotating intake or flipping manipulator).
VEX IQ pins are no longer legal for mounting license plates on robots
Added VEX Smart Field Controller Brains to the list of prohibited items in <R19>
Updated <R20i> to include metric equivalents
Added a bullet to <RSC2b> to clarify intent
In a Robot Skills Match, seven (7) Blocks constitute a filled Control Zone in a Center Goal.
Updated the list of acceptable Field modifications to <T6>, and added them to the end of Appendix A
Revised <VUG3> to clarify that Match Load Blocks may be entered into the Field during the Driver Controlled Period
Drive Team Members may add Match Load Blocks to the Loaders adjacent to their Alliance Station during the Autonomous Period and Driver Controlled Period of the Match.
On June 26th, 2025, Version 1.0 of the V5RC Push Back Game Manual was released, and the following changes were made:
If noted in the rule, egregious or strategic Violations or intentional actions that result in Violations may also be Major Violations
Event Partners may construct and/or provide any sizing tool that measures the correct dimensions.
Skills Matches do not include Match Load Blocks, and Blocks that leave the Field are not returned.
Head Referees must follow the rules in this game manual and the Q&A, and must make rulings consistent with the intent of the game manual and Q&A.
The next manual update, Version 1.1 will occur on August 7, 2025.
On August 7th, 2025, Version 1.1 of the V5RC Push Back Game Manual was released, and the following changes were made:
Any Team that intentionally or strategically removes three (3) or more Blocks from the Field in a single Match will receive a Major Violation.
Incidential Violations of <SG7> will not be penalized and will not automatically award the Autonomous Bonus to the opponent as described in <GG13>.
The next manual update, Version 2.0 will occur on September 4, 2025.
On September 4th, 2025, Version 2.0 of the V5RC Push Back Game Manual was released, and the following changes were made:
A Field Element and enclosed section of the Floor that mark a location where Blocks begin a Match and Robots can be Parked at the end of the Match. Park Zones are made of red or blue plastic extrusions and black plastic connectors, and include the enclosed portions of the Field Tiles. Each Park Zone is 18.87ā (479mm) wide x 16.86ā (428mm) deep.
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.
- At least ten (10) Blocks of the Allianceās color are Scored.
- At least three (3) different Goals include at least two (2) Scored Blocks of the Allianceās color.
- At least three (3) Blocks of the Allianceās color have been removed from Loaders adjacent to the Allianceās Alliance Station.
- Neither Robot is contacting the Park Zone barrier. "
A Team may send up to three (3) Drive Team Members to their Alliance Station for each Robot, and those Drive Team Members must remain in their Alliance Station for the duration of the Match.
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.
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).
No Holding for more than a 3-count. A Robot may not Hold an opposing Robot for more than a 3-count during the Driver Controlled Period.
After a Holding count ends, a Robot may not resume Holding the same Robot again for a 5-count. If a Team resumes Holding the same Robot within that 5-count, the original Holding count will resume from where it ended. A Head Referee should use fingers to display the 5-count that occurs after the end of a Holding count, and āwave it offā after the Holding interaction has been cleared.
Holding is a standard and legal part of Head-to-Head game play, and only becomes a Violation if it exceeds the guidelines in this rule. By beginning a Holding count immediately after noticing a Holding interaction, and providing a visual signal when a Holding interaction has been cleared, Head Referees can help Teams avoid penalties.
A Block can only be added to a Loader if there are no Blocks partially or entirely within the orange portion of that Loader.
- 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.
- For the purposes of this rule, the following guidelines should be used for escalating repeated Minor Violations to a Major Violation during Qualification Matches:
a. Six or more illegal Match Loads in a single Qualification Match.
b. Three or more Qualification Matches with at least one illegal Match Load (i.e., the third Match and all subsequent Matches with a Violation).
- For the purposes of this rule, only Match Affecting Violations should be considered during Elimination Matches (i.e., repeated Minor Violations in Elimination Matches do not compound to Major Violations).
a. 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.
b. Point B-2 does not apply during Elimination Matches.
During the last 20 seconds of a Match, Robots may not directly or indirectly contact the other Allianceās Park Zone or opponent Robots that are partially or entirely within the vertical projection of that Park Zone.
Events may wish to use āinspection markersā (e.g., zip tie or sticker) to identify Robots that have passed inspection at that event. Inspection markers are subject to all Robot rules, including legal materials and robot size/expansion limits.
The V5 Brain screen must be easily visible during Robot inspection. Keeping the V5 Brain screen visible throughout a Match is recommended but not required.
Removing Blocks from the Field in a Robot Skills Match is not a Violation. Blocks that leave the Field cannot be returned.
The Team will earn points for a Parked Robot if the Robot has moved during the Match, is within the red Alliance Park Zone, and meets all criteria of rule <SC4> at the end of the Match.
The designated 24ā Robot may expand horizontally and/or vertically up to a maximum size of 24" x 24" x 24" at any time during the Match.
The next manual update, Version 2.1 will occur on October 9, 2025.
On October 9th, 2025, Version 2.1 of the V5RC Push Back Game Manual was released, and the following changes were made:
One or more Students make up a Team. To participate in an official VEX V5 Robotics Competition event, a Team must first register on RobotEvents.com and receive a VEX V5 Robotics Competition Team number. A Teamās unique number identifies their organization and their Team within that organization. Each Team must build their own Robot, create their own code, and maintain their own Engineering Notebook if they choose to use one.
A Violation of a rule that relates to the RECF Code of Conduct and related processes. For V5RC, VURC, and VAIRC, the included rules are: <S2>, <G1>, <G2>, <G4>, <G5>, <R1> through <R4>, and Major Violations of <S1>.
Referees must record counts based on verified scoring statuses evaluated after the Match, using final positions of Scoring Objects, Field Elements, and Robots. Point considerations used to determine whether a Violation is Match Affecting (e.g., specified in Violation Notes) should NOT be added to or deducted from the actual score, and points scored during a Violation should not be deducted from a score.
- A Time Out can be ended early, but only if agreed to by both Alliances and the Head Referee.
- An Allianceās Time Out request should never be denied if the Alliance legitimately needs extra time.
In most cases, if a Team causes their opponent to break a rule, the Head Referee will simply not enforce the penalty on that opponent, and it will be considered a Minor Violation for the Team that forced a Violation. However, if the forced situation becomes Match Affecting in favor of the Team that forced the Violation, it will be considered a Major Violation for the Team that forced the Violation.
A Robot can only reach into any open portion of a Goal to move Blocks (e.g., into or out of the Control Zone or the entire Goal). If a Head Referee sees a Robot that has reached into a Goal and stayed there while the Robot isnāt actively moving Blocks inside the Goal, that Robot should be verbally warned away and should receive a Violation if it remains. See the Violation Notes for more details, including how rules and may apply
Teams who participate in Qualification Matches during a specific League Ranking Session are the only Teams who can participate in Robot Skills Challenge Matches at that session
The next manual update, Version 2.2 will occur on December 4, 2025.
On December 4th, 2025, Version 2.2 of the V5RC Push Back Game Manual was released, and the following changes were made:
Defensive - A category of strategies, Robot actions, and/or Robot statuses that can be employed by a Team during a Match; see rules and for more information. A Robot is Defensive while it is engaged in actions that cannot increase its Allianceās score for the current Match, and instead limits an opponentās ability to score or play the game. A Robot can be in possession of a scoring object and capable of scoring, but still be Defensive based on its actions.
Offensive - A category of strategies, Robot actions, and/or Robot statuses that can be employed by a Team during a Match; see rules and for more information. A Robot is Offensive while it is engaged in actions that could directly increase its Allianceās score for the current Match.
Goalkeeping - A Robot status and/or Robot action. In Push Back, a Robot is Goalkeeping while it is reaching into any open portion of a Goal while not attempting to change the score of the Match through legal means. A Robot can be in possession of a Block and capable of scoring, but still be Goalkeeping based on its actions. See for more information.
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 RECF Code of Conduct investigation. Misuse of this rule is considered a serious Violation.
Head Referees must apply judgment when determining whether each Robot in a <GG15> interaction was Defensive or Offensive, and in some cases may need to consider which Robot was more Defensive or Offensive than another within the larger context of the Match. In these cases, the Head Referee should decide in favor of the less Defensive and/or more Offensive Robot based on the definitions and guidance in this game manual.
Causing a Block to contact an opponent Robot that is driving at the moment of contact is a Violation; intentional Violations may be subject to Major Violations and Disqualifications at the discretion of the Head Referee.
i. Causing a Block to contact a stationary Robot is not considered a Violation unless the Head Referee determines it was a deliberate defensive action.
ii. Blocks that move across the Autonomous Line through Goals are not subject to <SG7>.
A Robot can only reach into any open portion of a Goal to legally move Blocks (e.g., into or out of the Control Zone or the entire Goal). If a Head Referee sees a Robot that is Goalkeeping in the Driver-Controlled Period of a Head-to-Head Match, that Robot should be verbally warned away and should receive an <SG10> Violation if it remains.
a. Reaching inside the open top portion of a Goal to affect Blocks within that Goal is an inherently Defensive position, and will not get the benefit of the doubt (<GG15>) if judgment calls are required.
b. If a Robot is reaching inside the open top portion of a Goal, it is that Teamās responsibility to ensure that the Robot doesnāt become entangled with the Goal when approached by other Robots. <GG16> will not apply during related interactions, and a Robot that becomes entangled while reaching into the open top of a Goal will receive a <GG9> Violation no matter how they became entangled.
An <SG10> Violation should be considered Match Affecting if the Team responsible ties or wins the Match by 10 points or less.
Event staff and volunteers are allowed to photograph Robots during inspection and/or at other times as needed.
V5 Robot Brain accessories (short flanges, long flanges, and the magnetic screen protector) are part of the V5 Robot Brain and are only legal for use on Robots as part of the V5 Robot Brain.
Specific zip tie dimensions listed on the VEX Robotics website are nominal references to hardware sizes found within the VEX V5 product line and/or their metric equivalents. The designated size of the product may differ slightly from the actual measurement.
Heating non-shattering plastic to aid in bending is acceptable.
V5 Robot Brain accessories (short flanges, long flanges, and the magnetic screen protector) are considered āpart of the V5 Robot Brainā and cannot be modified.
A Long Goal must include one or more of the following to be considered filled in a Robot Skills Match:
a. Three Blocks of the same color fully contained between the inner edges of the Control Zone tape lines
b. Four Blocks of the same color fully contained between the outer edges of the Control Zone tape lines."
The next manual update, Version 3.0 will occur on January 29, 2026.
On January 29th, 2026, Version 3.0 of the V5RC Push Back Game Manual was released, and the following changes were made:
A Robot status and/or Robot action. In Push Back, a Robot is Goalkeeping while it is reaching into any open portion of a Goal while not attempting to change the score of the Match through legal means (i.e., the Robot is not actively moving Blocks inside a Goal, and is not adding or removing Blocks to/from a Goal or a Control Zone). A Robot can be in possession of a Block and capable of scoring, but still be Goalkeeping based on its actions. See <SG10> for more information.
Clause D does not apply in situations where both/all teams are using the unmodified Hero Bot design, as allowed by clause C of this rule.
- Neither Robot is partially or entirely within the vertical projection of its Alliance-colored Park Zone or contacting the Park Zone barrier.
Goalkeeping is allowed during the Autonomous Period.
In the event of a Goalkeeping stalemate (i.e., no Blocks are moving inside the Goal) involving two or more Goalkeeping Robots, both Robots would receive <SG10> Violations if they remain within the Goal without moving Blocks. In this case, a Robot should receive a Major Violation if their mechanism adds or removes Blocks to or from the Control Zone and/or Goal as they depart.
a. A Team with one or two <SG10> Violations in a Match should be considered Match Affecting if the Team responsible ties or wins the Match by 10 points or less.
b. For the purposes of this rule, the following guidelines should be used to escalate repeated Minor Violations to a Major Violation in Qualification and Elimination Matches:i. Three or more <SG10> Violations in a single Match.
ii. Three or more Matches with at least one <SG10> Violation (i.e., the third Match and all subsequent Matches with a Violation)."
Each Robot must have a Preload that meets the requirements of <SG1> and <SG5>.
This additional battery pack must operate at a maximum of less than 13 volts.
It is legal to rotate the blocks of the V5 Optical Sensor and V5 Distance Sensor relative to their bases, and to manufacture custom back plates for these sensors.
The next manual update, Version 4.0 will occur on April 2, 2026.
On April 2nd, 2026, Version 4.0 of the V5RC Push Back Game Manual was released, and the following changes were made:
Goalkeeping - A Robot status and/or Robot action. In Push Back, a Robot is Goalkeeping while it is reaching into any open portion of a Goal while not attempting to change the score of the Match through legal means (i.e., the Robot is not actively moving Blocks inside a Goal, and is not adding or removing Blocks to/from a Goal or a Control Zone), or while it is simultaneously reaching into both open portions of a Long Goal. A Robot can be in possession of a Block and capable of scoring, but still be Goalkeeping based on its actions. See for more information.
Event staff other than referees may review video footage and/or photographs from the event as part of CoC-related Violation investigations; these reviews cannot change gameplay rulings made by Head Referees.
Drive Team Members must wear eye protection. All Drive Team Members must wear some form of eye protection while at the Field for Matches. Safety glasses or other eyewear with side shields and non-shattering lenses are recommended. While in the pit and queuing areas, it is highly recommended that all Team members wear eye protection.
At events using a V5 Smart Field Control System, the āTeam Numberā field in the Robot Brain must be set as the Teamās registered number and letter (with no spaces).
Beta firmware, which includes any firmware version that ends with the letter ābā, is not legal for use in competition.
Rubber bands no larger than 7.5ā long and 0.25ā wide.
Plastic zip ties no larger than 12ā long and 0.25ā wide.
Anti-slip drawer liner with similar nominal dimensions to VEX Anti-Slip Mat (275-0120 or 275-0121). The pattern of the matting should be similar to VEX Anti-Slip Mat, and there should be no additional performance gained by using non-VEX anti-slip drawer liner (i.e., no additional elasticity, adhesive backing, etc.). No piece of anti-slip drawer liner can be larger than 12ā x 15ā and all pieces must be black in color.
If the RECF Regional Support Manager determines that a Team should be removed from further Matches at the event based on the outcome of a CoC-related Violation, the EP can use the full-event Disqualification feature in TM to remove that Team from all further Matches at the event. Their spots in later Qualification Matches will be replaced automatically by Teams from the end of the Match schedule, and Matches will be removed from the end of the schedule as appropriate.
If a Team must be removed after Alliance Selection due to the outcome of a CoC-related Violation (see clause e of <T10>), the EP can use the full-event Disqualification feature in TM to remove that Team from their Alliance. Their spot in that Alliance will be filled manually by the EP by the next-highest-ranked Team that is not already in an Alliance. If that Team is unavailable or unwilling to participate, the EP can manually select the next-highest-ranked and available Team. If no replacement Team is available, the remaining half of that Alliance will play alone.
