Best Matches/Moments of 2016

[wajirock]

Seeing my team, 2052, shoot over a 54 inch blocker for the first time was pretty exciting.

Another exciting match was Quals 20 from Newton. It was a pretty strong match up with 118 on Blue going against 16 and 1477 on Red, but what made it interesting was that 118 stopped moving shortly after autonomous. They came back to life 50 seconds later, and the Blue alliance ended up winning by 1 point.

[AveryLevin.]

Originally Posted by wajirock

Seeing my team, 2052, shoot over a 54 inch blocker for the first time was pretty exciting.

Another exciting match was Quals 20 from Newton. It was a pretty strong match up with 118 on Blue going against 16 and 1477 on Red, but what made it interesting was that 118 stopped moving shortly after autonomous. They came back to life 50 seconds later, and the Blue alliance ended up winning by 1 point.

*sigh* My team was in the match with 118. We are the red alliance robot that was stuck near the portcullis for most of the match. *another sigh* I am to blame for our robot's malfunction and, subsequently, the loss. Being the team's lead programmer, I was asked to create an autonomous sequence to go breach the portcullis and shoot a high goal. LET THE NEXT SENTENCE BE A WARNING TO ALL PROGRAMMERS . One line in the code was missing a semicolon, causing the robot to get stuck in a loop, ruining the entire match. My missed keystroke is to blame for that close match (we didn't have time to test the auto code so it was never discovered).

[Dan Waxman]

Originally Posted by AveryLevin.

*sigh* My team was in the match with 118. We are the red alliance robot that was stuck near the portcullis for most of the match. *another sigh* I am to blame for our robot's malfunction and, subsequently, the loss. Being the team's lead programmer, I was asked to create an autonomous sequence to go breach the portcullis and shoot a high goal. LET THE NEXT SENTENCE BE A WARNING TO ALL PROGRAMMERS . One line in the code was missing a semicolon, causing the robot to get stuck in a loop, ruining the entire match. My missed keystroke is to blame for that close match (we didn't have time to test the auto code so it was never discovered).

It happens to the best of us haha. If it's any consolation it made the match a lot more entertaining than just another 118 win.