On December 4th, 2025, Version 2.2 of the VIQRC Mix & Match Game Manual was released, and the following changes were made:
- Updated Figures V-1 and V-3 to clarify intent
- Added new clauses to <SC3> to clarify “roughly vertical”
d. A Stack that is resting on one of the following Field Objects in a way that is more “up and down” than sideways should generally be considered as roughly vertical unless it is leaning on / supported by another Field Element or a Scoring Object that is not part of the Stack:
- Floor
- Load Zone
- The lower portion of the base of the Standoff Goal
- The VEX IQ pieces that are attached to the Floor around a Square Goal
e. A Stack that is leaning on / supported by a Scoring Object that is not part of the Stack or a Field Element other than those listed above should not be considered roughly vertical and should not count as Connected or a Stack.
f. Robot contact with a lower Stack in a multi-Stack structure has no impact on the higher Stacks in that structure for the purposes of clauses D & E. See <SE9> for an example.
- Updated <SE3> and <SE9> to reflect the updated guidelines for “roughly vertical”
- Expanded the blue box of <G4> to clarify rule enforcement
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."
- Updated <G5> to clarify “Drive Team Members”, rather than “Drivers”
- Added a new bullet to <GG1> to clarify that anyone who is not a Drive Team Member cannot coach or affect the Match
Individuals who are not Drive Team Members for a Match cannot provide directions, commands, or advice to the Drive Team Members during that Match. They’re welcome to provide cheerful, positive encouragement, but should not affect Match play or strategy.
- Updated <GG10> and <RSC5> to clarify intent regarding a Drive Team Member resetting a Robot and Scoring Objects
- Updated bullets in <SG1c> to indicate which teams are red and blue in VEXvia
i. For Teamwork Challenge Matches, the Team listed as Team 1 (printed Match list), listed as Red Team (RobotEvents.com), or listed first (VEXvia) must place their Robot in contact with the red Triangle Goal.
ii. For Teamwork Challenge Matches, the Team listed as Team 2 (printed Match list), listed as Blue Team (RobotEvents.com), or listed second (VEXvia) must place their Robot in contact with the blue Triangle Goal.
- Added a bullet to <R3> to specify that event staff are allowed to take pictures of Robots as needed
Event staff and volunteers are allowed to photograph Robots during inspection and/or at other times as needed.
- Added a bullet to <RSC7> to clarify that Teams cannot use Robot controllers for any purpose during Autonomous Coding Skills Matches
Teams cannot use VEX IQ Controllers for any purpose in Autonomous Coding Skills Matches, and are advised not to bring controllers to the Field. If there is a controller at the Field during an Autonomous Coding Skills Match, it should be placed on the floor outside the Field and remain untouched until after the Match.
- Revised <T5> to include Scoring Object positions, and specified that Pin rotation doesn’t matter
- Added significant Q&A boxes throughout the manual
- Minor typo / formatting fixes
The next manual update, Version 3.0 will occur on January 29, 2026.