hey guys I am wondering the best score you are able to get.
The highest score are 124pts by Team 2211B (with video confirmed) and 133pts by Team 44(https://vexforum.com/t/team-2211b-robot-skills/17080/1).
so is it really that someone has already got points more than 133? If it is, I think our team has to put all our effort to get 140pts(but very incredible).
Wish it to come true. lol
131 by 721 @ BCIT
130 by 575 also @ BCIT, for 2nd place
Rick, who is the fourth robot in the 130+ club you mentioned here? Is it 10Q?
I think the winning Robot Skills score will be around 138-140. I’ve seen a few teams that could score around 130-132 already. Teams 721 and 575 scored 131 and 130 in Vancouver on March 20 (no video, but I was there and the scores are official). Both 721 and 575 claim to have scored about 135 in practice, as have several other teams on the VEX forum.
We’re practicing right now, and 2467B just got 135. He can get 126+ every time we practice.
EDIT:
We just got a score of 143!!! we may upload a teaser video later for proof, but that is up to our coach.
We scored an uneasy 67 for programming (no robot on the other side), more accurately a reliable 45-50. This is without going for the back row of footballs, and no sensor input (programmer was lazy :P). Everything is dead reckoning xD
if everything is dead reckoning
then your autonomous will change based on the battery
Yeah, we’re replacing with shaft encoder and potentiometer inputs. 
(hence “uneasy 67”). We were distracted watching FRC championships at our meeting today xD
exactly why sensor’s are neessary. I see a lot of people doing their autonomous using only the wait() function. I guess it will work, but a lot of unneccessary testing will need to be done, and what murdomeek mentioned, a slightly over charged, or under charged battery from the time you tested can screw you over a lot.
The key is to mix the Waits and sensor inputs. A lot of simple functions like moving a generic distance or opening a claw can be used with wait. It’s when precise movement and limits come in that sensors are really needed. Sometimes a few well placed sensors and some tested waits will do quite fine without loading your bot with switches and rotational sensors.
You can also use both. I used the timer as a fail safe for the encoders. when backing up to the wall if something is messy or the field is not perfect sometimes the encoders do not quite reach their desired value and my drive motors stall trying to back up more for the remaining time in autonomous. I added in a timer value that tells the robot to “give up” on that step of the code after X seconds and move on. this way if i am second to the wall in autonomous and their are balls in the way. the robot will not just continue with the first step it will move on and actually score some more points elsewhere.
I think it is much easier to use the wait function this year because your 20 second auto does not have to be very precise unless you lock up balls. However for auto skills i think you really need sensors to score consistently.
~DK