Gosh, lots of questions here. Let’s see.
First impression at game unveiling “This is a walk through the cake.” Not the “they expect us to do WHAT!?!” that I have felt in previous years. I prefer the latter.
I think the challenge was a little bit too easy, and not NEARLY enough teams completed to NEARLY a high enough degree of success. Over two regionals, I observed no more than about a dozen teams that really “got it” Picking up and placing that tube is NOT a difficult thing to do. I’m not sure why more teams didn’t do it. And it’s not just that, it’s that if they chose not to play with tubes, their ramps often didn’t work either. 
Autonomous mode - It didn’t work. Need more incentive.
Regionals - much better run this year than last (for the one I can compare) and for the other one I went to for the first time it was very well run too. I liked the fact that the FIRST volunteers and/or staff/crew/etc seemed very approachable and very willing to listen to people for the most part. I can recall years when this was not the case.
The kit of parts - FIRST is not supposed to be easy. But the challenge isn’t supposed to be fixing defective components. I feel this years kit of parts was a downgrade in the drive system department from years past. 2005 and 2006, you could have a 4 motor 4wd robot straight from the kit of parts. This year, you had to spend more money to get that (dual motor adapter, or more gearboxes. On the BaneBots issue, I think it is something that could have been completely avoided, with proper engineering and proper testing procedure. While those gearboxes are a good value, they just aren’t robust enough for many teams, and I’m not confident it was the right move going to them. You know what I say? Don’t give us a gearbox at all. Shoot, don’t even give us wheels. Let the students learn something by building their own. If the robots cease to move, so be it. The “kit bot” has taken away a lot of the “sparkle” I think we used to have in FIRST. The goal of providing a driving chassis was to get teams to build better manipulators or whatever, but clearly, that hasn’t happened (at least not this year, imho). I really enjoyed this year reading “how are we supposed to attach the sprocket to the wheel, there were no screws in the kit” It is called a hardware store my friends. FIGURE IT OUT! Not to be rude but if you can’t figure out stuff like this perhaps you need to consider FVC. This is the big leagues. FRC teams need at least one person on there who knows how to assemble things, use tools, and fabricate things, in order to get something beneficial out of this program (imho).
So, the bottom line is, I think the parts that are given to us need to function as intended, but the robot should not be handed to us on a silver platter.
The Game - I feel this is a very fair game, although I’m not convinced it should be.
Victorious teams thought about their robots with a logical and realistic design process, built them to the specs of this well thought out design. The victorious robots were not “slapped together” nor were they designed fully and built poorly. Victorious teams cleansed and called upon their “crystal ball” in week one and did not design robots beyon their means to build them (this is a big problem I see).
Pairing alrgorithm It has its upsides. But, there are too many teams that never get to play with too many teams. I don’t like that.
And one last note on the KOP, that robot radio has got to change. I know the component got discontinued or whatever but that thing is too big, and I miss the small rubber antenna. And finally, as I’m sure most of us would agree, that rockwell block has to go, or at least the absurd requirement to use it does. I’m more in fear of robots catching fire this year than I ever had been before. I never have to retighten any of the bolts I design in anywhere on the robot. It is rediculous to think it is normal procedure to retighten the screws in that thing. The rockwell block is like driving from florida to new york by going through Colorado. There just is no point. (nothing against Colorado)