Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Rules/Strategy (http://www.chiefdelphi.com/forums/forumdisplay.php?f=6)
-   -   Our answer to the long range shooter (http://www.chiefdelphi.com/forums/showthread.php?t=115692)

xSAWxBLADEx 01-04-2013 23:55

Re: Our answer to the long range shooter
 
Quote:

Originally Posted by 2789_B_Garcia (Post 1255977)
2468 has a very reliable full-court shooter...in fact, they were the only full-court shooter at Alamo. We know that if we (a small defensive robot with a good drivetrain) went into elims with them and a small & quick pyramid shooter (our good friends at 4063), we had a good chance at winning...and it was exactly through the strategy mentioned above (and a few others) that we were able win.

It was this same combo with 118 and 148 that won at Lone Star this year.

2468 has been the most devastating full court shooter I've seen this year. It is amazing that they can shoot from literately everywhere. Also, great job 2789. You guys gave 2468 the space they needed. Perfect Alliance!

2789_B_Garcia 02-04-2013 00:40

Re: Our answer to the long range shooter
 
Quote:

Originally Posted by xSAWxBLADEx (Post 1255986)
2468 has been the most devastating full court shooter I've seen this year. It is amazing that they can shoot from literately everywhere. Also, great job 2789. You guys gave 2468 the space they needed. Perfect Alliance!

Thanks!

faust1706 02-04-2013 01:02

Re: Our answer to the long range shooter
 
With trig and extensive field testing (aka st louis regional), it is impossible for a robot to block all 3 targets if there is a robot between the full court shooter and the 80 inch blocker bot. Wonder how many teams will realize this and program a "juke mode." With a push of a button score at the far two point, another the 3 point, and another the close 2 point. ;)

friskywombat 02-04-2013 01:22

Re: Our answer to the long range shooter
 
Quote:

Originally Posted by xSAWxBLADEx (Post 1255986)
2468 has been the most devastating full court shooter I've seen this year. It is amazing that they can shoot from literately everywhere. Also, great job 2789. You guys gave 2468 the space they needed. Perfect Alliance!

Thanks, we appreciate the recognition. I think mobility is the root of our success as a full-court shooter. From the beginning of the season, people have been saying that full-courters are easily defendable with a tall blocking mechanism ("unappreciators"). We try to work around the tall defensive bots by being fluid and mobile on the other side of the field. We have the ability to feed from both sides, shoot from both sides, and switch between left and right quickly if we are affronted by a tall bot. (As opposed to most full-court shooters that I have seen who will switch to being cycle-runners to the pyramid when defended). And, yes, having 2789 keep away strong defenders such as 457 and 3545 was an immense help to us.

LoveRobots1425 02-04-2013 01:39

Re: Our answer to the long range shooter
 
My team has been a fairly successful long-range shooter at our regionals. Our theory is that, even if we do get blocked, that occupies 1/3 of the other alliance. If we picked our elimination alliance well, they should be able to pull us through if need be, even if we can only make our autonomous, a few discs, and our 10 point climb.

Also, we did face teams that slapped tall blockers onto their robots...and some were actuated. A word of warning: it's a technical foul (20 points) for leaving your autozone when you are taller than 60". We had a match with tons of foul points because the robot defending us would periodically (presumably accidentally) leave the autozone.

Amy_LeadFerret 02-04-2013 08:41

Re: Our answer to the long range shooter
 
Yeah, we were pretty proud of our long range shooter and its performance in Match 51 at the Wisconsin Regional. We've honored it in this (rather grainy) video made by one of the team members - from the perspective of the FCS team, of course.
http://www.youtube.com/user/TechnoFerrets

We appreciated all the teams on our alliances who forfeited their own potential disc points to be defender defender bots in order to give our bot the opportunity to do its thing, as well as the alliance partners who passed their frisbees to our human loader as our bucket ran dry. In a rather strange way, we're pleased to have provided that competitive edge that caused other teams to have to scramble (and even post pics of their alliance partners and pit neighbors assisting with jerry rigging!) to figure out how to shut us down. All in all, an amazing three days in Milwaukee!

PVCpirate 02-04-2013 10:56

Re: Our answer to the long range shooter
 
The face is a nice touch, I bet it would frustrate an opposing team even more if they're getting blocked by a big face. :D

Jaxom 02-04-2013 11:14

Re: Our answer to the long range shooter
 
Quote:

Originally Posted by LoveRobots1425 (Post 1256056)
Also, we did face teams that slapped tall blockers onto their robots...and some were actuated. A word of warning: it's a technical foul (20 points) for leaving your autozone when you are taller than 60". We had a match with tons of foul points because the robot defending us would periodically (presumably accidentally) leave the autozone.

It's only a Technical ⁿif continuous or repeated violations" according to G22. Otherwise, just a normal 3 point foul.

Jefferson 02-04-2013 12:47

Re: Our answer to the long range shooter
 
Quote:

Originally Posted by 2789_B_Garcia (Post 1255977)
2468 has a very reliable full-court shooter...in fact, they were the only full-court shooter at Alamo. We knew that if we (a small defensive robot with a good drivetrain) went into elims with them and a small & quick pyramid shooter (our good friends at 4063), we had a good chance at winning...and it was exactly through the strategy mentioned above (and a few others) that we were able win.

BTW, very cool to see you and 4063 (our alliance partners in Hub City) win with 2468 (a Hub City foe). Glad y'all could finish what we couldn't in Hub city.

See you in St. Louis.

2789_B_Garcia 02-04-2013 12:58

Re: Our answer to the long range shooter
 
Quote:

Originally Posted by Jefferson (Post 1256188)
BTW, very cool to see you and 4063 (our alliance partners in Hub City) win with 2468 (a Hub City foe). Glad y'all could finish what we couldn't in Hub city.

See you in St. Louis.

THANKS! Don't know if you saw the webstream, but our teams were Tweeting with the hashtag: #hubcityredemption lol

Coach Norm 02-04-2013 13:05

Re: Our answer to the long range shooter
 
Quote:

Originally Posted by Jefferson (Post 1256188)
BTW, very cool to see you and 4063 (our alliance partners in Hub City) win with 2468 (a Hub City foe). Glad y'all could finish what we couldn't in Hub city.

See you in St. Louis.

Jeff, we were very happy to see both of them available in selections. It was nice not to have to deal with them with opposing colored bumpers.

Looking forward to seeing you in St. Louis.

GaryVoshol 02-04-2013 19:00

Re: Our answer to the long range shooter
 
Anybody else see a blocker added during a 6-minute time-out between back-to-back matches?

EricVanWyk 02-04-2013 19:20

Re: Our answer to the long range shooter
 
Quote:

Originally Posted by GaryVoshol (Post 1256395)
Anybody else see a blocker added during a 6-minute time-out between back-to-back matches?

Yes.

Friendly reminder: all modifications require re-inspection.

vikesrock777 02-04-2013 20:03

Re: Our answer to the long range shooter
 
Quote:

Originally Posted by GaryVoshol (Post 1256395)
Anybody else see a blocker added during a 6-minute time-out between back-to-back matches?

Yeah, that also happened at Peachtree between finals-2 and finals-3. It didn't go so well for the team adding it though as they forgot (or ran out of time, not sure) to recharge their pneumatics.

Ninja_Bait 02-04-2013 21:03

Re: Our answer to the long range shooter
 
We turned 1991's climber into a pool noodle wall to defend against 195 in semis at CT; it was hastily duct-taped together and just barely tall enough to tip the disks off their mark. Had it been a little less droopy, it might have worked.

Of course, 20 just picked up 195's duds and popped up points anyway...

EDIT: This wasn't during a 'tween matches timeout, but we did use the timeout to get a little more time.


All times are GMT -5. The time now is 13:59.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi