On June 14, 2019, the following updates were made to the VRC Tower Takeover Game Manual.
- Updated definition of “Student” to clarify specfics of teams who wish to “Play Up”
Student - Anyone born after May 1, 2001 (i.e. who will be 18 or younger at VEX Worlds 2020). Eligibility may also be granted based on a disability that has delayed education by at least one year.
• Middle School Student - A Student born after May 1, 2004 (i.e. who will be 15 or younger at VEX Worlds 2020). Middle School Students may “play up” and compete as a High School Student.
• High School Student - Any eligible Student that is not a Middle School Student.
- Updated definition of “Team” to clarify specifics of teams who wish to “Play Up”
Team - One or more Students make up a Team. A Team is classified as a middle school Team if all members are Middle School Students. A Team is classified as a high school Team if any of its members are High School Students, or made up of Middle School Students who declare themselves “playing up” as High School Students by registering their team as a High School Team. Once declared and playing as a High School Team, that team may not change back to a Middle School Team for the remainder of the season. Teams may be associated with schools, community/youth organizations, or a group of neighborhood Students.
- Updated Rule G6 to clarify driving eligibility for multiple teams.
Drive your own Robot. Each Team shall include up to three Drive Team Members. No Drive Team Member may fulfill this role for more than one Team in a given competition season.
When a team qualifies for a Championship event (e.g., States, Nationals, Worlds, etc.) the students on the team attending the Championship event are expected to be the students on the team that was awarded the spot. Students can be added as support to the team but should not be added as drive-team members or programmers for the team.
An exception is allowed if one (1) student on the drive team, or a programmer on the team cannot attend the event. The team can make a single substitution of a drive team member or programmer for the Championship event with another student, even if that student has competed on a different team. This student will now be on this new team and may not substitute back to the original team.
Violations of this rule will be reviewed by the REC Foundation and may result in one or both teams being disqualified for the event or the remainder of the season with all trophies and awards won that season being nullified.
- Updated Rule G12 to clarify entanglement of game objects possessed by robots of the opposing alliance
d. Game elements in possession of a Robot are an extension of that Robot. Therefore, Entanglement (e.g., grasping, hooking, attaching) with Cubes that are in the possession of an opposing Robot is a violation of this rule.
- Updated Rule G22 to clarify that past years Q&A’s are no longer considered “official”
The 2019 - 2020 Q&A is the ONLY official source for rulings besides the Game Manual.
- Updated Rule R18 to clarify multiple Y Cables per motor port.
One motor or Y cable per motor port. If using a VEX ARM® Cortex®-based Microcontroller, a maximum of one (1) VEX Y-cable can be used per Motor Port of the Microcontroller or Power Expander. (You cannot “Y off a Y” to have more than two (2) motors controlled by the same Motor Port.)
a. Teams using the VEX ARM® Cortex®-based Microcontroller may only power one (1) 2-wire Motor per each of the two 2-wire motor ports on the Microcontroller. It is illegal to “Y” off a 2-wire Motor Port.
b. Teams may not “Y” off of a Motor Controller 29 (276-2193).
- Updated Rule R22 to include the use of loctite or thread locker
g. Mechanical fasteners may be secured using Loctite or a similar thread-locking product. This may ONLY be used for securing hardware, such as screws and nuts.
Updated Rule T14 with a link to the REC Foundation Qualifying Criteria Document
Other minor fixes
- Corrected definition of “Autonomous Points” with accurate values
- Corrected typo in definition of “Alliance Selection”
- T7 Typo
- RSC2 Typo
- RSC3 Typo
- Added Figure 8 to the definition of “Placed” to display another case of placed / not placed
- Added Figure 15 to the definition of “Stacked Cube” to display more cases of scored / not scored
- Added Figures 19 & 20 to Rule SG3 to display instances of contact within Protected Zones
- Added Figures 21 & 22 to Rule R8 to display legal VRC Robot radios