![]() |
Quote:
As much as I hate to admit it, you have a good point. |
I say keep the rule. The rule was made for a reason... in the real world there will be situations that you don't like your just gonna have to design your strategy with this rule driving it. As far as the superior alliance....the best alliances sometimes don't win just because your alliance has two or more good robots doesn't't ensure that you will win the match. I have seen the best robot pairings lose to pairings that i never would have thought would win...... It's all in the game , its all part of this 6 weeks...Strategy is as important as having a robot that is reliable.
|
For all you know, last year, many 'superior' teams may have been bumped just cuz one of their motors died in a freak accident. The whole strategy of "beating, but not too badly" makes you think and the 2 of 3 idea gets rid of that smoothly. Reliability is great.
And besides, it adds a bit of entertainment here ;) |
Sounds like if you know you can't win the first match you want to get as few points as possible. Also if you win the first match and get a lot of QP's you may be able to easily tolerate a loss in the second round as long as you have very few points yourself. (one robots makes sure you have 0 points and the other plays defense)
Veeerrrry interesting.... |
Imagine this:
The game starts. The 2 robots on one alliance don't move at all at the beginning of the match. They both have "damaged drive trains." The other 2 robots set up the field in such a way that they are going to win 100 to 99. With 30 seconds left, they both move up onto the ramp and wait. Suddenly, with 2 seconds left, both of the "disabled" robots dart out and knock over a stack or knock 2 tubs out of scoring position. The other robots can't do anything about it because they are relying on the 50 points from the ramp. The team that did ABSOLUTELY NOTHING all match wins 99-98. Is this strategy, or is it a loophole? Sure this would only work one time, but I can see some modified version of this where one alliance does all the work only to be beaten by a misjudgement. There are several factors involved in winning a game: - Robot functionality - Robot reliability - Pre-game strategy - In-game strategy This year the focus in the EPs is mostly on in-game strategy whereas previous years it was robot functionality/reliability and pre-game strategy. I can see how this can work to level the playing field for rookies who tend to not build as good a robot as veteran teams, but I agree there is too much luck involved in in-game strategy to make it a good way of determining a winner. Sure, it isn't about winning, but it sure does feel good when you do win, and even better when you know you won because you drove better, built a better robot, and strategized better, and not because your opponent forgot to count 2 of the bins when they counted up the number of bins in scoring position. |
Quote:
I guess I'm torn on this. There are reasons to have it both ways. |
Quote:
And besides, knowing this is the rules of scoring, team A deserve to be the losing team simply because they didn't let the other teams to get more points to build up their base points. I would say its a poor strategy they are playing, by not taking advantage of the scoring rule. Team B was the smarter team because they let team A get 49 points, and thus get 50 + 2*49. So, in this case, the "inferior" alliance didn't advance over a superior alliance into the next round. |
Leave it as it is
I'm not torn at all. I see no reason to decide this is SO bad it must be changed.
Its the rule on scoring. Don't slaughter your opponants. Thier score is part of the total. If you know this going in then its not a surprize. OK the 100-99 set up with the team with "two bad drives" "could" happen. But thats only one match. Its takes two matches to determine a win. And now that you suspect this plan by those sneaky opponants you can counter it. I really like the scoring. Its consistant through out the game. |
consistency
I think this is better than last year. Last year you had to play the complex strategy through all the qualifying round, but as soon as you got to the elimination rounds the strategy totally changed. All you had to do was brute force your score as high as you could. Some robots that did well in the qualifying rounds faired poorly once they got to the elimination rounds.
This way the strategy is consistent throughout the game, it does not change in the elimination rounds. I think that is definitely a good thing. |
what's the issue here?
I don't get this debate at all.
2 points: 1. FIRST clearly listened to team input more than ever this year, and much of that input from teams was to keep the game scoring the same in the qualifying and the eliminations? They did that - so a petition by teams to change it would be a little hypocritical at this point. Maybe this will fall into the category of "be careful what you wish for" - but we won't know until March. 2. Both alliances have the same scoring issues before them - luck is not an issue here any more than it is any year. If you win 2 matches, you win - that simple. If you win one and lose one, then whoever managed the points better wins. If an alliance is clearly superior to their opponent, they'll win both matches. If not, they may split 1-1, in which case the points determine the winner - both alliances know this going into the round, so if someone wins on points than they played the two matches better than the other alliance....seems that simple to me. Like Dean & Woodie said - this is a game: unfair is kids without opportunity, education, food, water, peace, and so on. If both alliances are playing with the same rules and both know the scoring and how a winner is determined - that is fair. Heck - we have a president who didn't even get more votes than the other guy - so if our country can't even get "scoring" down, maybe we should hold off on a petition to change something which hasn't even been proved flawed yet? Should be a fun year - can't wait for March! |
| All times are GMT -5. The time now is 03:35. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi