This thread will be used to publish updates to the VRC Nothing But Net Game Manual.
On June 15th, 2015, the following updates will be made to the VRC Nothing But Net Manual.
Various renders were updated to show the white tape line that mark the Low Goals.
The definition of Ball was updated to the following:
A corresponding update was made in Appendix A. This updated tolerance better reflects the variance we expect to see in the Nothing But Net Balls. You will need to design your Robots around this tolerance.
The definition of Low Elevated was updated to the following (with major changes marked in bold):
There are two changes in this definition. The intent of the first change is to make it clear that Robots may not rest or rely on the field perimeter as a means of support for a Low Elevation. Touching the field perimeter is fine, however being supported by it is not. Robot are to be supported by their partner Robot, not the field. The second change was done to make it crystal clear that only a single Robot on an Alliance can earn points for a Low Elevation during a Match.
The definition of High Elevated was updated to the following (with major changes marked in bold):
There are two changes in this definition. The first was the removal of the clause allowing High Elevated Robots from touching the field perimeter. High Elevated Robots may not touch the field perimeter at all. The intent here is that High Elevated Robots are supported by their partner Robot, not the field. The second change was done to make it crystal clear that only a single Robot on an Alliance can earn points for a High Elevation during a Match.
<G5a> was added to say the following:
The intent of this rule is to ensure that Drive Team Members are loading Robots on their own without assistance. If an event would like to provide a storage solution (a VEX IQ storage tote is a convenient ball holder) in addition to the provided mesh bag, that is fine, as long as it is made available to all teams at the event. However this provided device may only be used for storage and not for loading of Robots.
Rules <G7a> and <SG6> were updated to say the following (with major changes marked in bold):
These changes were made to allow Drive Team Members to break the plane of the field while legally introducing Driver Control Loads. However, we still want to make sure that Drive Team Members are being safe during this process. <S1> still applies.
Rule <R4b> was updated to say the following:
The intent of this change was to make it clear that any expansion still has to be legal as per <SG10>.
Rule <R7c> was updated to say the following:
The intent of this change was to allow for the use of common washers, much like the original allowance of screws and nuts.
Rule <R11> was updated to say the following (with major changes marked in bold):
Over the years many teams have expressed concern that the use of pneumatics of was too expensive and complicated and thereby provided an extreme advantage to only those teams who could afford them and had experience with them. The VEX Robotics Competition has always placed affordability and accessibility as major tenets of the program. As such we wanted to provide additional options for teams who are unable or choose not to use pneumatics. Now teams who forgo the use of pneumatics, are able to use two additional motors/servos if they so wish. Teams who wish to continue using pneumatics can do so under the original motor constraints.
Appendix A has been updated with the following text:
The intent of this change was to make it clear that field resetters may orient the piles of balls in the center of the field in any rotation. This will help speed up the field reset process for the game. Teams should design accordingly.
and have been updated as follows:
(The corresponding change has also been made in )
The intent of this change is to split the Skills Loads across both Loading Zones. This change means that if a Robot starts a red Alliance Starting Tile they will have access to 4 Robot/Programming Skills Preloads and 28 Robot Skills Loads from the red Loading Zone. They would then need to move to the blue Loading Zone to access the remaining 32 Robot/Programming Skills Loads.
The original has been deleted. The original version referred to interaction during Programming Skills Matches, however with the elimination of this type of interaction in the High School game, it no longer needed a specific rule in VEX U. A new was added as follows:
This change was made to make it clear that VEX U teams can earn points for Elevation during the VEX U skills challenges.
On August 17th, 2015, there was a scheduled update to the VRC Nothing But Net Manual, as per <G18>. However there were no changes to manual, thus no update was published.