![]() |
The "noodle agreement" is back! Now the defense agreement.
If both alliances picked defenses that were easily breach able by the other alliance each alliance could earn a free Ranking Point thus raising their standing. This could also aid in faster cycle times making weakening the tower faster and aiding in capturing the tower for the second Ranking Point. If the other alliances you were with were on board you could manage to rank better than teams that aren't able to breach the defenses should that be your entire robots design and your teams strategy.
|
Re: The "noodle agreement" is back! Now the defense agreement.
That my friend... is genius. How will the GDC get beyond that?
|
Re: The "noodle agreement" is back! Now the defense agreement.
Oh for the love of Monty Python...
Actually this violates T7 and T8. They deal with intentionally playing below one's ability, which I presume includes the selection of defenses that are known to be difficult for a particular set of opponents. Here we go Quote:
|
I believe that the only method would be randomization. However playoffs are still difficult
|
Re: The "noodle agreement" is back! Now the defense agreement.
Quote:
|
Also the defenses aren't completely simple, they are all uniquely challenging
|
Re: The "noodle agreement" is back! Now the defense agreement.
Quote:
|
Re: The "noodle agreement" is back! Now the defense agreement.
Quote:
Actually teams who do above average have incentives by the RP structure to vehemently disagree and block the agreement in order to cinch the win (and 2 RP's). If the team in station 2 (ref T28) goes with the agreement regardless then either other team on that alliance can simply bring it up to the head ref that T7/T8 are violated. |
Re: The "noodle agreement" is back! Now the defense agreement.
Quote:
You could make a case that if that team does put out defenses you request that they are then playing below their ability. Because defense selection is a part of the game, selecting hard ones might be "playing at your ability". |
Quote:
For example falling in rank so that you aren't an alliance captain. That rule is there to ensure that you aren't bringing other teams on your alliance down with you. Specifically some of the larger more well known teams that might get targeted to make it easier for other teams to be the first alliance captain. |
Re: The "noodle agreement" is back! Now the defense agreement.
Quote:
This is especially true for teams who chose to specialize in the defenses to begin with. Such an agreement effectively nullifies their specialty, giving an opponent a distinct advantage if the opponents are skewed more towards scoring boulders. |
Re: The "noodle agreement" is back! Now the defense agreement.
Not selecting the defenses that your scouts tell you are hardest for the opposing alliance is playing below your ability.
Violates T7/T8 for sure. |
Re: The "noodle agreement" is back! Now the defense agreement.
You will notice that the defenses are grouped such that both defenses in a group are of similar difficulty to traverse. Some of the groups are harder than others, but one defense from every group will be on the floor for every match. Which of the two choices happens to be on the floor is no big deal.
In keeping with the medieval theme, during those times politicking and treaty making was arguably a more valuable skill than outright warfare. If the game encouraged deal making, it would just be in keeping with the theme. But, I don't see that the benefits of deal making are all that tangible. I could be proven completely wrong on the field, though, if two particular defenses prove to be particularly tough. Note that if ONE of the defenses is the hardest, alliances can just skip that one. |
Re: The "noodle agreement" is back! Now the defense agreement.
Quote:
Voluntarily choosing weak defenses seem to violate the spirit of this rule if not the letter. |
Re: The "noodle agreement" is back! Now the defense agreement.
Quote:
|
| All times are GMT -5. The time now is 21:32. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi