Stopping a Triple Balance
 

In the week 2 Autodesk Oregon regional only one alliance triple balanced and, even though they were the 8th alliance, ended up winning the regional. As the weeks tick by I suspect triple balancing will become the path to victory for many alliances.

Teams with a long orientation robot, like ours, would seem to be at a disadvantage here. They are more stable on the bridges in the qualification matches and double balance nicely but unless you are lucky enough to pick a couple of abnormally short robots for your alliance you aren't likely to be doing much triple balancing.

I haven't watched all the week three regionals but has a method emerged to legally slow down or stop a triple balance by an opposing alliance? Can anyone point to videos of matches where that worked out?

Re: Stopping a Triple Balance
 

As a defensive player and a feeder robot, a team can just park on the wall right behind the opposing alliances bridge. Keep enough distance to eliminate a chance of a foul from transitive contact, but make it a tight squeeze so navigating to the bridge is tough. Doesn't stop it, but it does require a lot more time to pull off even a double balance with this in place.

Re: Stopping a Triple Balance
 

In reality, the alliance is playing defense on themselves. I can't even count how many times I've seen while watching the webcasts this week a robot tip over while trying to triple balance with their alliance. You really don't have too many options to stop a balance because of [G25].
I suppose one could sit in front of the bridge on the opposing side of the field where you're not in their alley, but then you could be pushed into the bridge, which may cause a foul.

You might also be able to get balls under the opposing alliance's bridge to try and stop them from being able to get on. This should at least slow them down somewhat.

Re: Stopping a Triple Balance
 

[G14]

Strategies that use Basketballs to either aid or inhibit Balancing of any Bridge are not allowed.
Violation: Technical-Foul, and counting or discounting the affected Bridge as Balanced, as appropriate.

Re: Stopping a Triple Balance
 

Aha, I knew there was a rule I overlooked. Nevermind then. :)

Re: Stopping a Triple Balance
 

I suppose you could trap a robot in the corner. Push them into the corner opposite your alley. Essentially box them out by angling between the corner of the fender and the wall near the opponents bridge. It effectively traps a robot in the corner assuming they don't have a drive train capable of pushing your robot out of the way sideways.

Its a 1 for 1 trade in terms of available robots on the field so your alliance would still have to out score the 2 bot balance. Ideally you could trap a good hoop scorer using the same strategy.

NOTE: I'm not positive but I believe as long as this is a 1v1 defense it would not violate [G-23]. Its still risky as you are close to the key and the bridge at times, and requires some reasonably advanced drives skill to prevent not being "juked" out enough that the opponents robot could catch a corner of your robot and spin you in place and escape.

Re: Stopping a Triple Balance
 

I saw 488 defend the triple balance in week 1. what they did is get inbetween the bridge and the robots trying to get up. it worked well, and actually stopped the triple that match.

Re: Stopping a Triple Balance
 

Today 2054 attempted to block 910 from reaching the bridge to finish off our triple balance since 910 was trying to play defense on the other side while 1918 and us, 85 were freely allowed to go on our bridge due to 141 and 3546 already double balancing leaving 2054 to shoot 3 pointers in. 910 however managed to break free and finish off the balance barely in time (like 1 second on the clock.)

The team in the lead has a possible advantage with not needing a triple balance to win the match so they could dedicate a robot purely to defense on the bridge timing approximately before when the other alliance will attempt. Trying to time the defense is a lot more risky but frees up a robot to do something else besides block a bridge.

My 2 cents on bridge balancing.

Re: Stopping a Triple Balance
 

I'd take a good look at the robots attempting the balance. If they haven't done it before, or aren't very successful/have a high CG, there's one great trick that will always work: Leaving them alone.

Most teams who get the triple balance do so because they practice it, or have a real good mechanism. Most teams don't get it on their first try if they don't have a mechanism for doing so.

All you need to do is sit back and watch the carnage.


Though IMO, if you can't mirror with a triple balance, you shouldn't try and disrupt their balance. The risk os too heavy, and the extra bot can be doing something good for your team (like scoring).

Re: Stopping a Triple Balance
 

We tried to stop the 3-bridge balance ala 488 in Alamo. They did it pretty successfully, and we just couldn't pull it off.

Re: Stopping a Triple Balance
 

If you know the opposing alliance will try to triple balance since they've done so before in earlier elimination matches then, as we learned the hard way, you need to have a plan. It's very hard to make up that extra 20 points with baskets during teleop assuming both alliances have reasonable hybrid scoring.

Re: Stopping a Triple Balance
 

My team, 3487, just compeated in the bmr here in Indiana, and I was wondering if it was leagal for another robot on the blue alliance to run into our robot on purpose? I ask this because this happened to us in the simi-finals and they pentilized us and caused an electrical blow out on our robot. ::rtm::

Re: Stopping a Triple Balance
 

I would recommend that you check the rulebook (as well as a dictionary), but in general, running into another robot is allowed.

Re: Stopping a Triple Balance
 

not my fault for having the worst spelling on the planet, but thank you.
:mad:

Re: Stopping a Triple Balance
 

That's quite off topic and there aren't enough details in your post to respond in your case. That being said there are many places in the rules this year where one robot could cause another to get a foul by pushing them into the opposing alliance's key, alley, or bridge.