Team Update 21 (2016)
 

Re: Team Update 21 (2016)
 

Wow they actually increased the strength of the tower from 8 up to 10. Will be interesting to see how this affects capture rates in the qualifications.

Re: Team Update 21 (2016)
 

Woahh, Tower Strength increase? Eight Ten now?

Re: Team Update 21 (2016)
 

Is anyone else wondering why there is a BACKUP Coupon Window on Einstein if you cannot call a backup robot?

Re: Team Update 21 (2016)
 

Because then they would have to actually change the graphic.

Re: Team Update 21 (2016)
 

Copy. Paste. Done. :)

Re: Team Update 21 (2016)
 

At MSC we saw many matches in which towers were fully or over weakened, but not captured because one robot failed to challenge. Capture rate 58%, challenge rate 72%.

I expect the importance of capture RPs for seeding will increase the incentive to shoot more and defend less.

Re: Team Update 21 (2016)
 

Called it.

http://www.chiefdelphi.com/forums/sh...d.php?t=145870

Re: Team Update 21 (2016)
 

I'm glad they changed G12, now I don't need to follow through on how to get one of our alliance robots to climb our own tower and block the 3 high goals. Figuring out a cheesecake to allow a robot to jump 10 inches straight up and lock onto a rung, rotate up and deploy blocking flaps sounded awesome but way too much time to develop and make. Now I might actually get to watch some of our matches!!!

After we did some post Sac Regional scheming we determined that blocking all 3 high goals was allowed in the rules, as was hanging from your own tower thus getting around the blocking goals while ON the BATTER. After about a week of thinking about it we had come up with 2 methods of achieving this by cheesecaking an alliance member for elims. We decided to give up the idea to go through with it for a a couple of reasons.
1. We didn't want to sink our valuable iteration time into R&D for something that would be very hard to have work.
2. In Bird Person culture this is what is considered an "Ungracious move".
Glad to see this loophole got closed up.

Prototype concept pictures of "chokehold" bot(as proof of our crazy ideas).

G41 - Boulder Crossing
 

So, how is a Ref supposed to remember if a Boulder came from the Courtyard to the Outerworks vs. Neutral Zone to the Outerworks?

Re: Team Update 21 (2016)
 

I was aware of the same choke-hold, it would have been insane to see it pulled off.

Re: Team Update 21 (2016)
 

Let's say the Robot #2 is broken. It gives you time to fix Robot #2. If you can't (withing the Backup Coupon Window) fix #2, then you call the time out. That gives you more time to fix #2, and/or swap to Robot #4.

It is easy in FMIS to swap out a robot. The Alliance may need more time to effect the change.

Re: G41 - Boulder Crossing
 

I think this is to eliminate the argument whether a boulder sitting "in" the lowbar (due to HP or whatever) that is then pushed through is a penalty or not.

Previously the wording implied that the boulder would have to be completely pushed through from the NEUTRAL ZONE into the COURTYARD by a robot, rather than from the outerworks to the courtyard.

Re: G41 - Boulder Crossing
 

Which is going to make those boulders stuck on the low bar flaps even more of a pain now....

Re: Team Update 21 (2016)
 

I think you are confusing the backup coupon window with the timeout coupon window. They are both included in Figure 5-11: Einstein TIMEOUT Timeline. My question is why is the backup coupon window there.