FUATT wrote: ↑Mon Nov 25, 2024 11:52 am
FUBeAR wrote: ↑Mon Nov 25, 2024 9:37 am
The Jackal wrote: ↑Mon Nov 25, 2024 6:38 am
I watch plays and sometimes just wonder if we just couldn't hide all of our freshmen this season.
This isn't a bad play design. We've got numbers. It appears that a freshman TE just misses his block.
…and a pulling OLman is, what Coach Caldwell would call, “lollygagging,” which gums up the works, preventing the RB from going outside when the LB ran under the TE’s block. Can’t lollygag. Find the most threatening bad-colored jersey and knock his a$$ out…RIGHT NOW! Patience is for RB’s, not OLmen.
Hold onto the ball.
I have no idea what this was supposed to be.
Hard to say. From QB’s head movements, may have been an RPO slant to R-Fr WR who was not looking for the ball, so QB seems to get discombobulated and ‘forgets’ the R part of RPO and doesn’t hand off to RB - which looks like it would have been a great, well-blocked run. And/or this was a triple-option RPO and QB saw (out of the corner of his eye) the DE squeezing hard with flow, and decided he could get the edge on him. If so, bad decision. That True FR DE for Mercer is probably 1st, maybe 2nd, Team All SoCon - unbelievable motor. On the turnover aspect, the more FUBeAR has watched this, it wasn’t a case of the QB just chunking the ball up for grabs as it may have appeared initially. Looks like the ball was stripped loose and the twisting motion of the tackle spun the ball up in the air and out with QB’s arm ‘follow-through’ trying to catch/retain it; not toss it. Very unfortunate for FU and very fortunate for Mercer.
A couple of FUBeAR’s thoughts above/in-line, in
bold
On that last one, I don't think it's that complicated. 8 was mistaken as to where the back was going to be, thought he would be at the mesh point earlier because I think he though he was coming off his right shoulder (where 7 is on the other side) and not from the gun. When back was not at the expected mesh point immediately, he flinched, panics, and then instead of running to the play side he runs to the off side and there's nobody out there but him and the unblocked (by design) end. And Chaos ensues.
I think this because of the play design and what the other 10 are doing (don't think this is RPO for this reason) and also that 33 stops and throws his hands out in a "WFT" kind of pose like "why didn't you give me the ball dude.
What's worse, this play is blocked to hell and back. Luna pulls the left side of the line has great push and cover. 15 chips and has the MLB dead. Backside backer is in the wash out of the play. 7 has the playside backer dead and 9 is on the S. It's 33 and the corner one on one and if he makes him miss this is probably a huge chunk play for 20+ yards assuming the backside S runs him down, but he has a long ass way to go and 33 can wheel so if he doesn't run 33 down the scoreboard lights up because all 11 are there in the frame.
Great 2nd and 10 call. Great execution by 10 players. This is the stuff that keeps coaches awake at night and makes them leave the film room to puke.
Good stuff - totally concur on how it’s being so well blocked, as stated.
But, your great explanation made FUBeAR take another look…and sees it differently now. It’s even simpler than we both thought. Not an RPO issue. Not a mesh point issue. Just a mental bust.
QB wasn’t looking to WR. He was looking to RB #7 to cross in front of him and take the ball in front of him - where he initially positions the ball - and run outside right.
When #7 goes away from QB to block left, that’s when the ‘panic’ and chaos ensues. QB’s are taught if something goes amiss on a handoff, you become the RB and go to the designed ‘hole.’ So, if QB, mistakenly, thought the play was going outside to the right, he did do that. Unfortunately, everyone else knew the play was designed to go outside left.
Yeah…looks like QB mental error…10 banks on Monday.