I've actually been thinking about it off and on all day, and I haven't come up with a good solution yet. Obviously I'm not a pro like the guys at Tiburon, but if I can't even conceptually come with an idea, that doesn't bode well imo. As far as I can tell, the problem stems from the fact that the blockers are told to find the closest threat and go to block that threat. In an open-field situation (as you guys have been talking above), that's exactly what we want to see (yet it doesn't always happen, strange). But in a close area like in my video, obviously, that doesn't work in our favor.
The only thing I can think of is that the blockers should recognize when their block will cross the path of the ball-carrier. That would be a general rule of thumb for any blocker looking for someone to block ... don't impede the ball carrier in order to do it.
Otherwise the only thing I could think of is that they need to continue going north instead of turning around ... but there are situations where you want your blockers to clean up threats behind the ball carrier. So I'm at a loss for a "simple" solution, which means the solution is complex ... and those suck to code![]()
Bookmarks