|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: Etiquette of the coopertition bridge
I was crunching some numbers earlier today (a lot of numbers...), and something I thought I'd take a look at was how rankings would have turned out if coopertition points did not effect qualification score. Let me tell you, there was a BIG difference. In fact, none of the top 8 teams would have come up in the same order, and with the exception of 772 at Smoky Mountain, 4161 in San Diego, 247 at Gull Lake, and 341 at Hatboro-Horsham, the number one seeded team would have been different. And teams as far down as the 7th Seed could have become 1st seed (3568 at Kettering). So, given these numbers, it's understandable why some teams would decline. If you can't beat a top seeded team, the best you can do is deny them the top spot. It goes without saying, that's what a lot of teams are willing to do. Simply put, it's not a nice or GP thing.
However, what a lot of teams didn't seem to realize, and this also came from the numbers, the top few spots were rarely determined by more than a hand full of qualification points (2-4, usually). And the tiers (what I've called the clusters 4-5 teams with the same number of qualification points), could easily have been totally changed by just one balance of the coopertition bridge. Teams could have advanced by leaps and bounds if they had chosen to cooperate more. Yeah, it's understandable why teams would want to not balance. It gives some a better chance to come out on top (especially if the stronger teams have had a run of bad luck and are losing). That being said, you make no friends, and don't guarentee yourself a better finish by turning down balancing. tl;dr: Just balance. You make more friends, look nicer to teams looking for a good balancer, and you rank higher. Those things come in order of how important I think they are. Last edited by LeelandS : 06-03-2012 at 17:34. |
|
#2
|
||||
|
||||
|
Re: Etiquette of the coopertition bridge
1.Offer to send your best robot to the co-op bridge if the other team will as well. That way both sides agree they are not just trying to slow down the other offense so they can win. Let the opposite alliance pick who they think your best robot is if it helps the negotiations.
2.Set a time to meet with a pre-negotiated time to pull out if the other doesn't show. Make it early enough that success is assured. If you've been burned by this try asking the other team to go first and then meet them promptly. Verbaly acknowledge that both teams have a reputation at stake here when it comes to honoring their commitments. 3.Set a strategy for the bridge so the other alliance feels confident that the time invested will achieve success. (One team gets on and tips the bridge to the other side, allowing the opponent on. Down hill member pushes until bridge starts to tip and then freezes. Uphill person then makes the fine adjustments.) 4.If you invite the other alliance to your key area to get on, tell your partners to avoid fouling them. If all else fails, try beating the other team by so many points that they realize their only hope for a qualification point is to co-op. ![]() |
|
#3
|
||||
|
||||
|
Re: Etiquette of the coopertition bridge
Every match in the Kansas City regional seemed to focus on coopertition points to the detriment of their own team many times. Look, if you are losing by less than 10 points and have single "bridge-bot" you have to try and get on your bridge to secure the 2 QP. Its at least twice as hard to balance two bots from teams on opposite ends of the field and I saw quite a few fail and end up with zero points where their own bridge would have gotten them the win and 2 QP. My instructions are to secure the win first and then go for coopertition points or as someone else already said, if the win is out of hand you go for coopertition points. I can't believe how many times I saw a team down by less than 10 get flipped or not able to pull of a coopertition balance on the middle bridge and walk away with nothing while handing two points to the other alliance. Why?
|
|
#4
|
||||||
|
||||||
|
Re: Etiquette of the coopertition bridge
Quote:
|
|
#5
|
|||||
|
|||||
|
Re: Etiquette of the coopertition bridge
Quote:
That said, I'm not 100% sure about that. If you have another robot on each alliance that isn't coopertitionating (that's a word now), then you have another robot for each alliance that can score or balance. If teams sent their best balancer/best robot in general to the co-op bridge (which would theoretically be the smart thing to do), then that robot is left to score for their alliance, potentially balancing things out. So, in theory, it would be a wash, or close to one. But that's just my guess. This will require further study Also, with the 20pt cap on balancing in qualification rounds, the addition of a 3rd robot solely for benefiting the alliance wouldn't be a super drastic change. Depending on the alliance, strategy and robot firepower. But that's definitely a point I need to consider more next round. Thank you very much for pointing this out to me! -Leeland |
|
#6
|
||||
|
||||
|
Re: Etiquette of the coopertition bridge
Even with pre-made plans, my drive team reported to me that my team was ditched from the coopertition bridge in least two separate qualification matches.
|
|
#7
|
||||
|
||||
|
Re: Etiquette of the coopertition bridge
Quote:
We've been ditched before too, but it never resulted in the other team winning. We always had time to recover. This has a way of making a lasting impression on a team. Sometimes for years. (Our scouts have a long memory when it comes time for alliance selections.) A reputation is a valuable thing. A plea to all teams. Don't make an agreement you can't or won't keep. You represent more than just yourself in this endeavor, and the consequences can reach beyond the game. ![]() |
|
#8
|
||||
|
||||
|
Re: Etiquette of the coopertition bridge
Quote:
Looking back, I had 4 agreements to balance in 12 matches (our allies had some as well). We always had to go second as we couldn't lower. 1 ended in the partner robot tipping themselves before we got there, 1 broke down, and 2 didn't go for unclear reasons. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|