![]() |
2012 Picklist Formation and Strategy
I've been thinking a lot about this recently and I thought i'd share my thoughts and get the opinions of others.
I think the ability to triple balance will be neccesary for any alliance planning to win their division. I could be wrong, and something like an 1114 2056 combo could be good enough to outscore their opponents by 7 top baskets (or they could find a way to triple together :eek:), but i'm going to operate under the assumption that we want to triple, generally meaning 2 widebots and a long or 3 widebots. (note: our robot is a widebot) For alliance selections, I plan to give our representative 2 lists. First a list of the best 30 teams in the opinion of our scouting team, ranked in order from number 1 to number 30. The rankings of these teams however will generally favor wide bots over long bots, meaning a longbot may score higher than a wide bot by a some margin yet the wide orientation is enough to put them above the longbot on our picklist. Our representative will use this list to pick our first robot. The second list will be a list of the 30 best wide robots in order from 1 to 30. If our first pick is a widebot we use the first list again for our second pick. If our first pick is long we use the second list. (this is of course assuming there's enough widebots in the division.) If you're a longbot then i'd only have one list ranking all the widebots with a few top pick exceptions that would make you're alliance forego the triple. Generally speaking though, I would think you'd want the top widebot as you're first pick. If you're wide and you pick the best widebot available as you're first pick, then your second pick becomes the best robot still left. If you pick a longbot first your second pick is limited to the best widebot left, and depending on their scarcity that well may be starting to dry up by then, or the gap between the best longbots and widebots left may have become incredibly large. Anyway, what do you guys think? What are you planning on doing for you're picklists? Do you pick robots to fit your strategy or do you pick the best robots and then form a strategy? |
Re: 2012 Picklist Formation and Strategy
Quote:
Drafting straight off of a list can be a huge mistake. When forming an alliance, there are usually distinct traits you will want from each of your alliance partners. You want to draft to play a strategy. There will be roles that you want your alliance partners to fit into. Figure out what roles you can fit into. Determine what other teams can fit into other roles you want and will play effectively with you. (Of course there are often times situations were you want to just take the best team available, but many others where you need each team to play a part in your strategy, rather than just being good. This is especially true when all of the teams you have to draft from have clear weaknesses, that you need to be able to cover up in your strategy.) Based on your first pick, then you will need to reevaluate what traits your alliance has, and what other roles your alliance needs filled, in order to select a your third alliance partner. So, if part of your strategy is to triple balance, and you only have one wide, then select a wide (if that is what you feel is important to complete your alliance). But in a more general sense, (as a very simple example) say you draft an offensive robot first (Team A), and decide that you now have enough good scorers that there wont be enough balls to score, so drafting a third scorer doesn't make sense. Then there is a scorer (Team B) that you ranked above a robot (Team C), that plays better defense than B. In this situation you would want to draft C. Had you not been able to get A, you would want B, but now your alliance no longer needs B, so you should draft C, but drafting straight off of a list you would have ranked B higher than C. Another reason to not draft directly from a list is that it allows you to take input from your alliance partner on who to select with the second pick. It is important that all 3 alliance partners are comfortable working together. I would suggest that you have your teams representative be as well versed in the teams, so that they can make an educated selection. Give them a pick list, but don't make it strict. Get your representative to be knowledgeable about the plan, how it works, and what teams need to be able to do to be a part of it. Also, enable them with as much information as possible. This way your representative can also help your alliance captain make a better second selection, if you are not an alliance captain. |
Re: 2012 Picklist Formation and Strategy
I would agree that the triple balance is a good way to win...but not the only way. It does take a good amount of time typically to triple balance......meanwhile your opponents are scoring up a storm. A perfect 36 point auto with super strong offensive play can outscore it especially if two bots on the opposing alliance easily and quickly balance for 20 while their third bot continuing offense the whole time .....its a winning strategy that could outscore a triple balance.
|
Re: 2012 Picklist Formation and Strategy
Quote:
For the most part, you shouldn't have a strategy set in stone before your alliance makes its final draft selection. You can have a pretty good idea that you want to triple balance every match, or do a certain thing in hybrid, but please take a look at the teams still available before making a pick based on a certain strategy. For example, if it turns out there's a longbot available for first pick that can shoot 4 balls in hybrid reliably (including 2 from the coop bridge), and no widebots can do that, we will pick that bot immediately because that's 24 points in hybrid plus 6-12 points taken away from the other alliance because the coop balls are ours. Another thing: If you split your list up into different categories (first pick, hybrid second pick, defense second pick) you can run into this kind of problem: Code:
First pick Second pick (defense) Second pick (hybrid) Good balancersCode:
Pick ListAnd another thing, if you really do like a team for one strategy that you think will give you a huge edge over other alliances, put them on your list exactly where you'd want them. I think 3601 was as high as 9th or so on 3322's list at Kettering; without them, we wouldn't have had a 6 ball Rube Goldberg autonomous! |
Re: 2012 Picklist Formation and Strategy
Keep in mind, that those two robots (1114 and 2056 in this example) would actually have to score 11 balls in the same time as a triple, due to the fact that they would only be able to score a single. That being said, it might be possible. 1717 scored 7 balls in about the same time as a double. Assuming a adequate ball supply, two teams(maybe 469 and 1717) could possibly pull it off, but it would really depend on the field conditions at the time. From what I have seen though, the triple can be pulled off pretty quickly. 973 pulled off triples with 3 widebots really easily and quickly, and many of the better teams with stingers should be able to pull a triple off just as quickly.
|
Re: 2012 Picklist Formation and Strategy
Quote:
Also, i think there are a number of ways to play defense, a good scorer can also be a good defender, but how would you know unless they played defense in their quals? unless you're ranking defenders on pitscouting and drivebase alone... which i feel would be another mistake. A good defender could simply be a ball feeder/stealer starving you're opponents of opportunities to score. What if in the course of your matches one of your scoring robots break? Maybe they can still drive but their shooter fell off severely hindering their ability to score. Do you then go with 2 defenders and one scorer? Or can the robots on your alliance switch and adapt to play different roles? If you're third bot is just a drivebase, but a really good balancer and defender, i don't think they can fill that void. So then you have to bring in a backup bot and hope that they can fill the role in your strategy. |
Re: 2012 Picklist Formation and Strategy
Quote:
|
Re: 2012 Picklist Formation and Strategy
Quote:
In most cases, the tactical robot's role will be very defined (either offense or defense), but it's additional versatility over a 'pure' defense or offense bot might be just what you need in a pinch to move on. |
Re: 2012 Picklist Formation and Strategy
Why not just pick three really good offensive bots, and have the one that can play the best defense out of the three play defense/ball starvation? This works really well if you're in alliance 4-8, because then you are starving the rest of the field of another offense bot.
|
Re: 2012 Picklist Formation and Strategy
I always thought one of the dumbest things you could do in alliance selection is send down anyone but your head scout to make the picks. (With an exception for teams who "whiteboard" picks from the stands, then you can send whomever you want.) The person picking needs to have knowledge of all of the teams being selected.
No matter what you do, ANY list this year NEEDS to have robot orientation on it. In my opinion, if you're not trying for the triple balance, you're not trying for the World Championship. Have fun trying to score 7 balls in the extra ~15 seconds you have over a good triple alliance, or rolling the dice with legally hazy defensive strategies that take a robot away from an offensive contribution anyway. Some long bots can hang off the end. Some long bots will say they can hang off the end but in practice be really, really bad at it, or won't be able to get enough of themselves on the bridge by the time it starts moving. Knowing the difference is part of good scouting and there is certainly a trust factor in there. Every pick should have the triple balance in mind. In the first round you should have enough of an idea who you might get to pick that you can talk to them in advance and see what they need to make a triple work. In my mind, that is the true advantage of a top seed in the era of the serpentine. |
Re: 2012 Picklist Formation and Strategy
Quote:
|
Re: 2012 Picklist Formation and Strategy
Quote:
|
Re: 2012 Picklist Formation and Strategy
Quote:
But if you go far in the tournament most teams will probly be able to triple so that means they will cancel out and it comes down to hybrid and telop. And hybrid is more point then telop but potentially you have more time to shoot more baskets. So then comes the question what which one do you go for? |
Re: 2012 Picklist Formation and Strategy
Quote:
|
Re: 2012 Picklist Formation and Strategy
Quote:
Your best bet is to for for the triple yourself and if you are down, pray that the other alliance can't pull it off. |
Re: 2012 Picklist Formation and Strategy
Quote:
|
Re: 2012 Picklist Formation and Strategy
Quote:
See posts 71 through ~90 -Duke |
Re: 2012 Picklist Formation and Strategy
Quote:
|
Re: 2012 Picklist Formation and Strategy
Quote:
|
Re: 2012 Picklist Formation and Strategy
Quote:
|
Re: 2012 Picklist Formation and Strategy
Quote:
|
Re: 2012 Picklist Formation and Strategy
Quote:
I was replying to the topic of if two long bots who are great scorers can forego a triple balance and outscore the other alliance in ball points alone. |
Re: 2012 Picklist Formation and Strategy
Quote:
|
Re: 2012 Picklist Formation and Strategy
Quote:
*Our alliance sought head-ref clarification well in advance to ensure there was no G45. The key was that we knew we wanted a G28 (without G44) rather than a G25 (with G44), so we took this approach instead of the Queen City style. Moral: know your rules, and be willing to take the licks they require. |
Re: 2012 Picklist Formation and Strategy
Quote:
This is G45 in action, is it not? Perhaps I am misunderstanding you and you are not bragging about causing your opponent to take penalty points. |
Re: 2012 Picklist Formation and Strategy
Quote:
|
Re: 2012 Picklist Formation and Strategy
Quote:
G28 exists to make defenders move if offensive robots can create the needed situation, the same way anyone picks up a ball and has to use G28 to get a clear shot on the key, or crosses into their lane uses it to load from their inbounder station. The point is not to force penalties, but rather to force movement via penalties/threats thereof. 1218 being over there was not a result of our actions, but rather theirs*. Their decision to stay (rather than get out/sit beside the bridge) was also their own, despite our attempts to dissuade them. The most important part though, is the head ref aspect. Any alliances thinking of doing this at Worlds (I expect we'll see at least one) may want to check themselves very early as well to make sure everyone is prepared and understands the relevant intricacies. *The only G45 I've ever known (not implying it's the only one) was when an defensive bot pushed a offensive bot across the field and into their lane, repeatedly smashed them, was waved off by a ref, and came back and smashed them again. Is that better? I hadn't intended to sound pompous. Strategy gets exciting to me. :o |
Re: 2012 Picklist Formation and Strategy
Quote:
With the clock ticking down, I told our driver to try and dislodge 1218's robot from its position in front of the bridge. They have a long robot and I was hoping that by pushing them from a corner, we could "spin" them out of their position at the front of the bridge. You can see from the video that we were able to turn them out of position partially, but still didn't give 25 enough room. I believe that at no point 1218 was truly "pinned in" - had they applied forward throttle they would have scooted out towards the co-op bridge. You can see what I mean here: http://youtu.be/w2bQ_frSNlk?t=1m57s The discussion with the referees prior to the match was to clarify that trying to balance a bridge is "within the spirit of the game" and not an abuse of G44. It's exactly like lining up for a key shot; you can keep hitting a blocking robot until they move out of your way. |
Re: 2012 Picklist Formation and Strategy
Thanks for the explanations. The initial post made it sound like the strategy was to force the other alliance into penalties. Makes more sense now.
|
| All times are GMT -5. The time now is 00:44. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi