![]() |
Re: Team Update #18
Quote:
|
Re: Team Update #18
Quote:
|
Re: Team Update #18
Quote:
|
Re: Team Update #18
It's good entertainment watching everyone's pre-game strategies go to waste! :p
|
Re: Team Update #18
Why do I have a disturbing feeling that we are heading for another Update 16 debacle. It seems interesting to me that FIRST wouldn't have learned their less on that one. Also I say props to WildStang for thinking of this one haven't seen anyone else try this in any of the last 3 regionals I've been at/watched I guess because of the size restriction issue. Once again the action of FIRST reversing it's decision mid-season seems far worse than the decision itself. Although this used to be the norm and it may make things more interesting sometimes. I guess FIRST should put a disclaimer in the manual "rules are subject to change until the last match has been played on Einstein in Atlanta."
-Justin |
Re: Team Update #18
Quote:
|
Re: Team Update #18
I would very disappoined If the #1 seed was picking teams by how they stacked :ahh: Just pile up some junk in the cornner and throw for ringers :confused: Im glad they made the change. :)
|
Re: Team Update #18
Quote:
Seriously, I can see both sides of this one. If the rule hadn't been changed, there would have likely been some teams put in the position TVan describes above, and what kind of inspiration is that? But I can also see the side that says you don't change the rules in the middle of the game. (Jump in any time, Tristan.) |
Re: Team Update #18
Quote:
|
Re: Team Update #18
190 actually considered making a robot which would start like this, with a partner on top. Their wheels would be on some sort of rollers/tracks which would control the drivetrain below. The intent was the have them driving our base, and ensure the 30 points. Logistics and other things kept us from doing it, but it was a legit strategy that was considered. If any teams that have not competed decided to do this, they've just been shafted.
|
Re: Team Update #18
Quote:
|
Re: Team Update #18
Quote:
|
Re: Team Update #18
2002 all over again...
at least this time it's not as big a deal as it was before. :rolleyes: |
Re: Team Update #18
Well, I'm not taking sides on the Update issue but I applaud the "thinking outside the box" strategy. Creativity and thinking outside the box are skills that are still valued by some companies, aren't they?
|
Re: Team Update #18
Interesting. I think I am starting to see a pattern here:
drill presses = OK (at kickoff) drill presses = NOT OK (middle of competition season) (everyone raises a stink) drill presses = OK (again) stacking robots at the start of the match = OK (at kickoff) stacking robots at the start of the match = NOT OK (middle of competition season) (everyone raises a stink) stacking robots at the start of the match = ???????? I personally think that this strategy would be used so very rarely because of the risk involved that why in the world should it have even been a blip on FIRST’s radar. Does FIRST think that this strategy is such a problem that it in effect deserves it’s own team update? Good grief. Why can’t we just get a clear set of rules in the beginning and just stick with them the whole season. Doesn’t FIRST have enough to worry about as it is without making a “new” rule for something that has, as far as I know, only happened once? And even then, wouldn’t have made a difference in the outcome of the match because the score reflected that they would have won anyway (1 on 3 BTW). Most people got a good laugh and thought, “Now that was a cool idea, we should have thought of that!” Now that someone was creative but within the rules, FIRST has to go and make an example out of them I guess. I really have to wonder what is the big deal. I suppose FIRST doesn’t really like creativity after all. FIRST wrote the rules, the question was asked in the Q&A to make sure it was legal, and now FIRST doesn’t like it. Can’t FIRST just roll with it like everyone else and say “That was a good one, you got us.” |
| All times are GMT -5. The time now is 22:51. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi