Well Richt seems to agree with us

[LuCane]

The thing is Richt HAS run this type of offense before at FSU. The Sugar Bowl NC win over VT he spread out VT and Weinke picked them apart. They put up 40+ on a good defense that way. My problem is I suspect he may not be adjusting to the strengths and weaknesses of Kaaya and instead running his O the way he wants to run it. For example: no way you run RPO with BK as he really is no threat to run. Also maybe we take advantage of Kaaya being a streaky rhythm passer and call a couple of plays to get him warmed up (easy completions) then go downfield in a 4 wide set for several plays in a row.

Guys...again...

RPO's have NOTHING to do with QB runs.

That's not entirely true, but I'm supporting you on these posts because it doesn't have everything to do with QB runs. There seems to be a lot of confusion about RPO on here, and I'm not sure why. It's been broken down time and again.

- Not every RPO is reading the DE; actually, many of them are reading a "stuck in between" LB who is responsible for, say, the "B" gap in run support and the stick route from the slot WR. When he makes his decision on which to cover, the QB either hands off or passes it over him.

- Some RPOs have three options: handoff, QB run, then bubble screen or the like. This is NOT the RPO Richt is running with Kaaya.

- We *have* done well with the passing option in the RPO this year and against FSU. In the GaTech game, it got Coley a TD by zipping it passed a pinching LB's ear. If I remember correctly (from watching in the stadium), in the 3rd quarter, on that huge, huge play where Stacy Coley got tripped up going into the endzone (then got a 5 yard neutral zone infraction immediately after because he was asking to be pulled out of the game and we went tempo), that was also an RPO.

In any case, we're not reading DEs and Kaaya isn't intended to run. We also ran it too much anyway, and Richt apparently admitted that much.

We've had a couple good plays with the RPO game. We run it so much we better have a couple good plays with it.

Problem is that overall it's been an ineffective and spotty element to the offense and Kaaya doesn't appear comfortable with it. It looks awkward and it's not working enough of the time as is evidenced by the 2nd half debacle of 88 yards against a **** D.

So, yeah, we can point to a couple good results we've had with it. But overall it's been ineffective. And the offense is disjointed and seems to be trying to do too many different things.

We haven't had a couple good results, we've been taking chunks out of defenses with it. I charted one of our games and we were averaging over 9 YPP with our gun/RPO stuff.

All those bubble screens that we take for 8+ yards a pop...those are RPO's.
When Walton/Yearby breaks a big run out of the shotgun...it's usually due to an RPO.
Coley's long TD against GT was an RPO.

It's our best offense.

I looked back and it actually wasnt the pass to Coley where he got tripped up in the 3rd quarter. It was a play or two before that where we ran the RPO to Richards on a quick slant. Man, Richards is our guy. We need to run those in breaking routes repeatedly to him and leave Berrios in the slot or moving around inside.

 

[jerzeycane]

Funny nobody complains about RPO's when Yearby is streaking into the endzone untouched

Richt didn't have a great night, but people in here are legit just mad that we lost to FSU for the 7th consecutive time...das it

 

[Coach Macho]

Guys...again...

RPO's have NOTHING to do with QB runs.

That's not entirely true, but I'm supporting you on these posts because it doesn't have everything to do with QB runs. There seems to be a lot of confusion about RPO on here, and I'm not sure why. It's been broken down time and again.

- Not every RPO is reading the DE; actually, many of them are reading a "stuck in between" LB who is responsible for, say, the "B" gap in run support and the stick route from the slot WR. When he makes his decision on which to cover, the QB either hands off or passes it over him.

- Some RPOs have three options: handoff, QB run, then bubble screen or the like. This is NOT the RPO Richt is running with Kaaya.

- We *have* done well with the passing option in the RPO this year and against FSU. In the GaTech game, it got Coley a TD by zipping it passed a pinching LB's ear. If I remember correctly (from watching in the stadium), in the 3rd quarter, on that huge, huge play where Stacy Coley got tripped up going into the endzone (then got a 5 yard neutral zone infraction immediately after because he was asking to be pulled out of the game and we went tempo), that was also an RPO.

In any case, we're not reading DEs and Kaaya isn't intended to run. We also ran it too much anyway, and Richt apparently admitted that much.

We've had a couple good plays with the RPO game. We run it so much we better have a couple good plays with it.

Problem is that overall it's been an ineffective and spotty element to the offense and Kaaya doesn't appear comfortable with it. It looks awkward and it's not working enough of the time as is evidenced by the 2nd half debacle of 88 yards against a **** D.

So, yeah, we can point to a couple good results we've had with it. But overall it's been ineffective. And the offense is disjointed and seems to be trying to do too many different things.

We haven't had a couple good results, we've been taking chunks out of defenses with it. I charted one of our games and we were averaging over 9 YPP with our gun/RPO stuff.

All those bubble screens that we take for 8+ yards a pop...those are RPO's.
When Walton/Yearby breaks a big run out of the shotgun...it's usually due to an RPO.
Coley's long TD against GT was an RPO.

It's our best offense.

I looked back and it actually wasnt the pass to Coley where he got tripped up in the 3rd quarter. It was a play or two before that where we ran the RPO to Richards on a quick slant. Man, Richards is our guy. We need to run those in breaking routes repeatedly to him and leave Berrios in the slot or moving around inside.

Richards is that dude!

You talking about the slant versus McFadden?

 

[MIATL]

Not looking for a ****ing match, but read my post again.

My point isn't about "reading" containment. It's about how disciplined the contain has to be when the QB is a running threat. And if those players are delayed from crashing on the inside runs, it increases the chances of breaking a run. Same concept can occur if they overplay the bubble.

Richt can't get that discipline with Kaaya as a runner, so he tries to do it with the bubble. It wasn't successful against FSU. So, it sounds like he's going to use more traditional run sets to get the balance he wants. And instead of running it out of passing formtations, he'll likely throw out of running formations.

And FWIW, all "option" plays are "read" plays. Triple option and run-pass option both require the QB to read the defense, and distribute the ball appropriately.

I agree 100% with this. Gary Patterson did this a few years ago and it's been great for him. Imagine having a high powered offense with Manny's defense. Now that would be scary.

The thing is Richt HAS run this type of offense before at FSU. The Sugar Bowl NC win over VT he spread out VT and Weinke picked them apart. They put up 40+ on a good defense that way. My problem is I suspect he may not be adjusting to the strengths and weaknesses of Kaaya and instead running his O the way he wants to run it. For example: no way you run RPO with BK as he really is no threat to run. Also maybe we take advantage of Kaaya being a streaky rhythm passer and call a couple of plays to get him warmed up (easy completions) then go downfield in a 4 wide set for several plays in a row.

RPO's have NOTHING to do with QB runs though.

I think some of you guys are confusing RPO's with read/option stuff.

RPO's run better with mobile QBs. Why are you pretending one has nothing to do with the other?

If contain has to worry about bubbles and the QB running, they have to stay more disciplined at the snap. And that indecision allows for runners to crease the defense easier. You coach defense ... You trying to tell me that you don't instruct your DL to attack mobile QBs in a different manner than immobile QBs?? :11263323124_b207743

It's the same concept as the triple-option. Yeah, you could run it without a super mobile QB ... But it lessens the effectiveness of the offense.

To put it simply ... Bobby Petrino didn't just remember how to coach offense this year, after 2 years of terrible offense at Louisville. He just has the QB to run it. Gus Malzhan isn't dumber now than he was as the OC at Auburn, he just doesn't have a generational talent playing QB for him. There's a reason Dak Prescott might be an issue for re-inserting Tony Romo back into the Dallas Cowboys offense ... And it's because of his running ability.

So ... Yeah, teams can run out of the spread without a running QB. But the teams that do it effectively, throw the ball 45 times a game to open the run lanes. And that's not who Richt is, right now. He's trying to be balanced, which means teams will keep 6 in the box against our shotgun looks. And our OL isn't good enough to beat the more talented teams on our schedule who do that.

Gripe about him being balanced all you want. I won't argue it. But folks who thought they were gonna see Richt doing a Art Briles or Josh McDaniels or Chad Morris impression set themselves up for disappointment. Richt wants to run the ball ... Did it at FSU and did it at UGA.

Dude, listen...

The RPO concepts that WE RUN...do not have QB run aspects built into them. We run a pure RUN/PASS OPTION, meaning the only options are to RUN (hand it off) or PASS (pull it and throw).

WE'RE NOT READING THE CONTAIN PLAYER, SO IT'S IRRELEVANT WHAT HE DOES. WE ARE READING AN "OVER HANG" PLAYER aka A FLAT DEFENDER.

RPO does not = read/option

Why do you guys think they're one in the same?

You can combine QB run concepts with RPO's and it basically becomes a triple option play, but that's not what we do. That's not even what most RPO teams do.

 

[Coach Macho]

Not looking for a ****ing match, but read my post again.

My point isn't about "reading" containment. It's about how disciplined the contain has to be when the QB is a running threat. And if those players are delayed from crashing on the inside runs, it increases the chances of breaking a run. Same concept can occur if they overplay the bubble.

Richt can't get that discipline with Kaaya as a runner, so he tries to do it with the bubble. It wasn't successful against FSU. So, it sounds like he's going to use more traditional run sets to get the balance he wants. And instead of running it out of passing formtations, he'll likely throw out of running formations.

And FWIW, all "option" plays are "read" plays. Triple option and run-pass option both require the QB to read the defense, and distribute the ball appropriately.

The thing is Richt HAS run this type of offense before at FSU. The Sugar Bowl NC win over VT he spread out VT and Weinke picked them apart. They put up 40+ on a good defense that way. My problem is I suspect he may not be adjusting to the strengths and weaknesses of Kaaya and instead running his O the way he wants to run it. For example: no way you run RPO with BK as he really is no threat to run. Also maybe we take advantage of Kaaya being a streaky rhythm passer and call a couple of plays to get him warmed up (easy completions) then go downfield in a 4 wide set for several plays in a row.

RPO's have NOTHING to do with QB runs though.

I think some of you guys are confusing RPO's with read/option stuff.

RPO's run better with mobile QBs. Why are you pretending one has nothing to do with the other?

If contain has to worry about bubbles and the QB running, they have to stay more disciplined at the snap. And that indecision allows for runners to crease the defense easier. You coach defense ... You trying to tell me that you don't instruct your DL to attack mobile QBs in a different manner than immobile QBs?? :11263323124_b207743

It's the same concept as the triple-option. Yeah, you could run it without a super mobile QB ... But it lessens the effectiveness of the offense.

To put it simply ... Bobby Petrino didn't just remember how to coach offense this year, after 2 years of terrible offense at Louisville. He just has the QB to run it. Gus Malzhan isn't dumber now than he was as the OC at Auburn, he just doesn't have a generational talent playing QB for him. There's a reason Dak Prescott might be an issue for re-inserting Tony Romo back into the Dallas Cowboys offense ... And it's because of his running ability.

So ... Yeah, teams can run out of the spread without a running QB. But the teams that do it effectively, throw the ball 45 times a game to open the run lanes. And that's not who Richt is, right now. He's trying to be balanced, which means teams will keep 6 in the box against our shotgun looks. And our OL isn't good enough to beat the more talented teams on our schedule who do that.

Gripe about him being balanced all you want. I won't argue it. But folks who thought they were gonna see Richt doing a Art Briles or Josh McDaniels or Chad Morris impression set themselves up for disappointment. Richt wants to run the ball ... Did it at FSU and did it at UGA.

Dude, listen...

The RPO concepts that WE RUN...do not have QB run aspects built into them. We run a pure RUN/PASS OPTION, meaning the only options are to RUN (hand it off) or PASS (pull it and throw).

WE'RE NOT READING THE CONTAIN PLAYER, SO IT'S IRRELEVANT WHAT HE DOES. WE ARE READING AN "OVER HANG" PLAYER aka A FLAT DEFENDER.

RPO does not = read/option

Why do you guys think they're one in the same?

You can combine QB run concepts with RPO's and it basically becomes a triple option play, but that's not what we do. That's not even what most RPO teams do.

Ok, again...

The "contain" player in an "even front" is the Defensive End. It doesn't matter how disciplined he is versus an RPO because HE'S NOT THE CONFLICT PLAYER. HE'S NOT THE ONE BEING READ BY THE QB. The DE is actually being blocked out by the Offensive Tackle, so he has outside contain regardless of what the QB does.

The defender who's being read is the SECOND LEVEL DEFENDER i.e. THE LINEBACKER. He's the one who's discipline is being tested. If HE delays then we break big runs.

Most RPO teams don't even have a running threat at QB. If you have a mobile Quarterback then you can add some QB running concepts into your RPO game, but QB runs are not a staple of the RPO world.



And FWIW, I'm fully aware that all option plays are "read" plays, however, they're not all called READ/OPTION.

 

[Coach Macho]

A lot of successful RPO's in these highlights...
https://www.youtube.com/watch?v=K3ADar4MNR0

 

[MIATL]

Fam ... my point is that, because all options plays are read plays, the read isn't the issue I'm talking about. Maybe others are talking about that, but you quoted me in your response. My point is about what I believe Richt was trying to get by running RPO plays.

IMO, he was using the bubble screens to keep the ends wide, so that his tackles could get help blocking on the inside runs. What he likely figured out from the FSU game is that the bubbles didn't help his tackles. So, he's going to use the TE and FB to do that.

Maybe it works, maybe it doesn't. But that's the point I take from the comment that started this thread. We'll see less RPO, and more 2-back.

Not looking for a ****ing match, but read my post again.

My point isn't about "reading" containment. It's about how disciplined the contain has to be when the QB is a running threat. And if those players are delayed from crashing on the inside runs, it increases the chances of breaking a run. Same concept can occur if they overplay the bubble.

Richt can't get that discipline with Kaaya as a runner, so he tries to do it with the bubble. It wasn't successful against FSU. So, it sounds like he's going to use more traditional run sets to get the balance he wants. And instead of running it out of passing formtations, he'll likely throw out of running formations.

And FWIW, all "option" plays are "read" plays. Triple option and run-pass option both require the QB to read the defense, and distribute the ball appropriately.

RPO's have NOTHING to do with QB runs though.

I think some of you guys are confusing RPO's with read/option stuff.

RPO's run better with mobile QBs. Why are you pretending one has nothing to do with the other?

If contain has to worry about bubbles and the QB running, they have to stay more disciplined at the snap. And that indecision allows for runners to crease the defense easier. You coach defense ... You trying to tell me that you don't instruct your DL to attack mobile QBs in a different manner than immobile QBs?? :11263323124_b207743

It's the same concept as the triple-option. Yeah, you could run it without a super mobile QB ... But it lessens the effectiveness of the offense.

To put it simply ... Bobby Petrino didn't just remember how to coach offense this year, after 2 years of terrible offense at Louisville. He just has the QB to run it. Gus Malzhan isn't dumber now than he was as the OC at Auburn, he just doesn't have a generational talent playing QB for him. There's a reason Dak Prescott might be an issue for re-inserting Tony Romo back into the Dallas Cowboys offense ... And it's because of his running ability.

So ... Yeah, teams can run out of the spread without a running QB. But the teams that do it effectively, throw the ball 45 times a game to open the run lanes. And that's not who Richt is, right now. He's trying to be balanced, which means teams will keep 6 in the box against our shotgun looks. And our OL isn't good enough to beat the more talented teams on our schedule who do that.

Gripe about him being balanced all you want. I won't argue it. But folks who thought they were gonna see Richt doing a Art Briles or Josh McDaniels or Chad Morris impression set themselves up for disappointment. Richt wants to run the ball ... Did it at FSU and did it at UGA.

Dude, listen...

The RPO concepts that WE RUN...do not have QB run aspects built into them. We run a pure RUN/PASS OPTION, meaning the only options are to RUN (hand it off) or PASS (pull it and throw).

WE'RE NOT READING THE CONTAIN PLAYER, SO IT'S IRRELEVANT WHAT HE DOES. WE ARE READING AN "OVER HANG" PLAYER aka A FLAT DEFENDER.

RPO does not = read/option

Why do you guys think they're one in the same?

You can combine QB run concepts with RPO's and it basically becomes a triple option play, but that's not what we do. That's not even what most RPO teams do.

Ok, again...

The "contain" player in an "even front" is the Defensive End. It doesn't matter how disciplined he is versus an RPO because HE'S NOT THE CONFLICT PLAYER. HE'S NOT THE ONE BEING READ BY THE QB. The DE is actually being blocked out by the Offensive Tackle, so he has outside contain regardless of what the QB does.

The defender who's being read is the SECOND LEVEL DEFENDER i.e. THE LINEBACKER. He's the one who's discipline is being tested.

Most RPO teams don't even have a running threat at QB. If you have a mobile Quarterback then you can add some QB running concepts into your RPO game, but QB runs are not a staple of the RPO world.



And FWIW, I'm fully aware that all option plays are "read" plays, however, they're not all called READ/OPTION.

 

[Coach Macho]

Fam ... my point is that, because all options plays are read plays, the read isn't the issue I'm talking about. Maybe others are talking about that, but you quoted me in your response. My point is about what I believe Richt was trying to get by running RPO plays.

IMO, he was using the bubble screens to keep the ends wide, so that his tackles could get help blocking on the inside runs. What he likely figured out from the FSU game is that the bubbles didn't help his tackles. So, he's going to use the TE and FB to do that.

Maybe it works, maybe it doesn't. But that's the point I take from the comment that started this thread. We'll see less RPO, and more 2-back.

Not looking for a ****ing match, but read my post again.

My point isn't about "reading" containment. It's about how disciplined the contain has to be when the QB is a running threat. And if those players are delayed from crashing on the inside runs, it increases the chances of breaking a run. Same concept can occur if they overplay the bubble.

Richt can't get that discipline with Kaaya as a runner, so he tries to do it with the bubble. It wasn't successful against FSU. So, it sounds like he's going to use more traditional run sets to get the balance he wants. And instead of running it out of passing formtations, he'll likely throw out of running formations.

And FWIW, all "option" plays are "read" plays. Triple option and run-pass option both require the QB to read the defense, and distribute the ball appropriately.

RPO's run better with mobile QBs. Why are you pretending one has nothing to do with the other?

If contain has to worry about bubbles and the QB running, they have to stay more disciplined at the snap. And that indecision allows for runners to crease the defense easier. You coach defense ... You trying to tell me that you don't instruct your DL to attack mobile QBs in a different manner than immobile QBs?? :11263323124_b207743

It's the same concept as the triple-option. Yeah, you could run it without a super mobile QB ... But it lessens the effectiveness of the offense.

To put it simply ... Bobby Petrino didn't just remember how to coach offense this year, after 2 years of terrible offense at Louisville. He just has the QB to run it. Gus Malzhan isn't dumber now than he was as the OC at Auburn, he just doesn't have a generational talent playing QB for him. There's a reason Dak Prescott might be an issue for re-inserting Tony Romo back into the Dallas Cowboys offense ... And it's because of his running ability.

So ... Yeah, teams can run out of the spread without a running QB. But the teams that do it effectively, throw the ball 45 times a game to open the run lanes. And that's not who Richt is, right now. He's trying to be balanced, which means teams will keep 6 in the box against our shotgun looks. And our OL isn't good enough to beat the more talented teams on our schedule who do that.

Gripe about him being balanced all you want. I won't argue it. But folks who thought they were gonna see Richt doing a Art Briles or Josh McDaniels or Chad Morris impression set themselves up for disappointment. Richt wants to run the ball ... Did it at FSU and did it at UGA.

Dude, listen...

The RPO concepts that WE RUN...do not have QB run aspects built into them. We run a pure RUN/PASS OPTION, meaning the only options are to RUN (hand it off) or PASS (pull it and throw).

WE'RE NOT READING THE CONTAIN PLAYER, SO IT'S IRRELEVANT WHAT HE DOES. WE ARE READING AN "OVER HANG" PLAYER aka A FLAT DEFENDER.

RPO does not = read/option

Why do you guys think they're one in the same?

You can combine QB run concepts with RPO's and it basically becomes a triple option play, but that's not what we do. That's not even what most RPO teams do.

Ok, again...

The "contain" player in an "even front" is the Defensive End. It doesn't matter how disciplined he is versus an RPO because HE'S NOT THE CONFLICT PLAYER. HE'S NOT THE ONE BEING READ BY THE QB. The DE is actually being blocked out by the Offensive Tackle, so he has outside contain regardless of what the QB does.

The defender who's being read is the SECOND LEVEL DEFENDER i.e. THE LINEBACKER. He's the one who's discipline is being tested.

Most RPO teams don't even have a running threat at QB. If you have a mobile Quarterback then you can add some QB running concepts into your RPO game, but QB runs are not a staple of the RPO world.



And FWIW, I'm fully aware that all option plays are "read" plays, however, they're not all called READ/OPTION.

Bubbles have nothing to do with the Defensive Ends. Bubbles influence flat defenders, not DE's.

The bubbles that we run are pure RPO's.

If we have numbers in the box because FSU bumped a Linebacker out to cover bubbles, we hand the ball off.
If FSU keeps the Linebacker in the box to help defend the run, we throw the bubble.

The act of the slot WR bubbling out is what pulls the Linebacker out of the box, thus helping us run the ball. The D-Ends are not an issue.

Most of our bubbles were successful versus FSU so I don't know how he would come to that conclusion you're talking about.

Not trying to be condescending but I don't really think you understand what an RPO concept entails and that's why you keep going back and forth with me. The DE's are meaningless in an RPO. IT'S THE 2nd LEVEL "CONFLICT PLAYER" THAT DETERMINES WHETHER WE CAN RUN THE BALL OR NOT.

 

[LuCane]

That's not entirely true, but I'm supporting you on these posts because it doesn't have everything to do with QB runs. There seems to be a lot of confusion about RPO on here, and I'm not sure why. It's been broken down time and again.

- Not every RPO is reading the DE; actually, many of them are reading a "stuck in between" LB who is responsible for, say, the "B" gap in run support and the stick route from the slot WR. When he makes his decision on which to cover, the QB either hands off or passes it over him.

- Some RPOs have three options: handoff, QB run, then bubble screen or the like. This is NOT the RPO Richt is running with Kaaya.

- We *have* done well with the passing option in the RPO this year and against FSU. In the GaTech game, it got Coley a TD by zipping it passed a pinching LB's ear. If I remember correctly (from watching in the stadium), in the 3rd quarter, on that huge, huge play where Stacy Coley got tripped up going into the endzone (then got a 5 yard neutral zone infraction immediately after because he was asking to be pulled out of the game and we went tempo), that was also an RPO.

In any case, we're not reading DEs and Kaaya isn't intended to run. We also ran it too much anyway, and Richt apparently admitted that much.

We've had a couple good plays with the RPO game. We run it so much we better have a couple good plays with it.

Problem is that overall it's been an ineffective and spotty element to the offense and Kaaya doesn't appear comfortable with it. It looks awkward and it's not working enough of the time as is evidenced by the 2nd half debacle of 88 yards against a **** D.

So, yeah, we can point to a couple good results we've had with it. But overall it's been ineffective. And the offense is disjointed and seems to be trying to do too many different things.

We haven't had a couple good results, we've been taking chunks out of defenses with it. I charted one of our games and we were averaging over 9 YPP with our gun/RPO stuff.

All those bubble screens that we take for 8+ yards a pop...those are RPO's.
When Walton/Yearby breaks a big run out of the shotgun...it's usually due to an RPO.
Coley's long TD against GT was an RPO.

It's our best offense.

I looked back and it actually wasnt the pass to Coley where he got tripped up in the 3rd quarter. It was a play or two before that where we ran the RPO to Richards on a quick slant. Man, Richards is our guy. We need to run those in breaking routes repeatedly to him and leave Berrios in the slot or moving around inside.

Richards is that dude!

You talking about the slant versus McFadden?

Yep. McFadden can't hang with Richards and wait till he gets some real strength.

 

[MIATL]

A lot of successful RPO's in these highlights...
https://www.youtube.com/watch?v=K3ADar4MNR0

We averaged 2.2 yards per rush. Richt wants more from the running game, and he doesn't think RPO will give him that against better teams. 2.2 yards per rush suggests he's right.

I'm on board with Kaaya in shotgun all game. I think we'd be ok with Brad throwing 40 times per game. But I don't think that's who Richt wants to be.

 

[The Franchise]

The thing is Richt HAS run this type of offense before at FSU. The Sugar Bowl NC win over VT he spread out VT and Weinke picked them apart. They put up 40+ on a good defense that way. My problem is I suspect he may not be adjusting to the strengths and weaknesses of Kaaya and instead running his O the way he wants to run it. For example: no way you run RPO with BK as he really is no threat to run. Also maybe we take advantage of Kaaya being a streaky rhythm passer and call a couple of plays to get him warmed up (easy completions) then go downfield in a 4 wide set for several plays in a row.

Guys...again...

RPO's have NOTHING to do with QB runs.

That's not entirely true, but I'm supporting you on these posts because it doesn't have everything to do with QB runs. There seems to be a lot of confusion about RPO on here, and I'm not sure why. It's been broken down time and again.

- Not every RPO is reading the DE; actually, many of them are reading a "stuck in between" LB who is responsible for, say, the "B" gap in run support and the stick route from the slot WR. When he makes his decision on which to cover, the QB either hands off or passes it over him.

- Some RPOs have three options: handoff, QB run, then bubble screen or the like. This is NOT the RPO Richt is running with Kaaya.

- We *have* done well with the passing option in the RPO this year and against FSU. In the GaTech game, it got Coley a TD by zipping it passed a pinching LB's ear. If I remember correctly (from watching in the stadium), in the 3rd quarter, on that huge, huge play where Stacy Coley got tripped up going into the endzone (then got a 5 yard neutral zone infraction immediately after because he was asking to be pulled out of the game and we went tempo), that was also an RPO.

In any case, we're not reading DEs and Kaaya isn't intended to run. We also ran it too much anyway, and Richt apparently admitted that much.

We've had a couple good plays with the RPO game. We run it so much we better have a couple good plays with it.

Problem is that overall it's been an ineffective and spotty element to the offense and Kaaya doesn't appear comfortable with it. It looks awkward and it's not working enough of the time as is evidenced by the 2nd half debacle of 88 yards against a **** D.

So, yeah, we can point to a couple good results we've had with it. But overall it's been ineffective. And the offense is disjointed and seems to be trying to do too many different things.

We haven't had a couple good results, we've been taking chunks out of defenses with it. I charted one of our games and we were averaging over 9 YPP with our gun/RPO stuff.

All those bubble screens that we take for 8+ yards a pop...those are RPO's.
When Walton/Yearby breaks a big run out of the shotgun...it's usually due to an RPO.
Coley's long TD against GT was an RPO.

It's our best offense.

I disagree that it's been effective. Anything we did against some of the garbage on our schedule would work. It was an abomination against the one good team we played, and it resulted in one or two good gains against GT.

 

[daytonacane]

He's been a head coach for 15 years and feels rusty.

Re-read...........rusty on play calling which is usually done by the OC.

 

[Coach Macho]

Guys...again...

RPO's have NOTHING to do with QB runs.

That's not entirely true, but I'm supporting you on these posts because it doesn't have everything to do with QB runs. There seems to be a lot of confusion about RPO on here, and I'm not sure why. It's been broken down time and again.

- Not every RPO is reading the DE; actually, many of them are reading a "stuck in between" LB who is responsible for, say, the "B" gap in run support and the stick route from the slot WR. When he makes his decision on which to cover, the QB either hands off or passes it over him.

- Some RPOs have three options: handoff, QB run, then bubble screen or the like. This is NOT the RPO Richt is running with Kaaya.

- We *have* done well with the passing option in the RPO this year and against FSU. In the GaTech game, it got Coley a TD by zipping it passed a pinching LB's ear. If I remember correctly (from watching in the stadium), in the 3rd quarter, on that huge, huge play where Stacy Coley got tripped up going into the endzone (then got a 5 yard neutral zone infraction immediately after because he was asking to be pulled out of the game and we went tempo), that was also an RPO.

In any case, we're not reading DEs and Kaaya isn't intended to run. We also ran it too much anyway, and Richt apparently admitted that much.

We've had a couple good plays with the RPO game. We run it so much we better have a couple good plays with it.

Problem is that overall it's been an ineffective and spotty element to the offense and Kaaya doesn't appear comfortable with it. It looks awkward and it's not working enough of the time as is evidenced by the 2nd half debacle of 88 yards against a **** D.

So, yeah, we can point to a couple good results we've had with it. But overall it's been ineffective. And the offense is disjointed and seems to be trying to do too many different things.

We haven't had a couple good results, we've been taking chunks out of defenses with it. I charted one of our games and we were averaging over 9 YPP with our gun/RPO stuff.

All those bubble screens that we take for 8+ yards a pop...those are RPO's.
When Walton/Yearby breaks a big run out of the shotgun...it's usually due to an RPO.
Coley's long TD against GT was an RPO.

It's our best offense.

I disagree that it's been effective. Anything we did against some of the garbage on our schedule would work. It was an abomination against the one good team we played, and it resulted in one or two good gains against GT.

Ol' chise, maybe you need to look back at the last 2 games. Or maybe you just didn't recognize which plays were RPO's.

Our highlights from the GT and FSU games are chuck full of RPO's.

Walton's big run Saturday night = RPO
Coley's long TD versus GT = RPO
All of those 8+ yard gains on bubble routes to Njoku/Herndon = RPO's
The successful slant routes to Richards = RPO's

A lot of our big runs came on RPO's.

 

[MIATL]

Actually, you can't help but be condescending. It's your thing. But it's all good! Lol

You keep replying to me from your coaching clinic perspectives.

Have you ever implemented something from a clinic, and found that it didn't work for you and your team strengths?

... We averaged 2.2 yards per rush. The run game was unsuccessful against FSU even if you want to give credit to RPO for when we were able to move the ball. But Richt is saying he used it too much to run the ball, and he didn't have success. He's acknowledging that, so why do you keep replying to me about something Richt is stating, and the stats validate?

The point I believe you're missing, which is obvious, sense you understand the concept of what RPO is and is supposed to do ... Is that we had the numbers we wanted when we ran the ball, and still didn't have success.

So, I'll try a different approach to see if we can find common ground ... Why do you think FSU was able to stifle the run AND limit the bubble game?

Fam ... my point is that, because all options plays are read plays, the read isn't the issue I'm talking about. Maybe others are talking about that, but you quoted me in your response. My point is about what I believe Richt was trying to get by running RPO plays.

IMO, he was using the bubble screens to keep the ends wide, so that his tackles could get help blocking on the inside runs. What he likely figured out from the FSU game is that the bubbles didn't help his tackles. So, he's going to use the TE and FB to do that.

Maybe it works, maybe it doesn't. But that's the point I take from the comment that started this thread. We'll see less RPO, and more 2-back.

Not looking for a ****ing match, but read my post again.

My point isn't about "reading" containment. It's about how disciplined the contain has to be when the QB is a running threat. And if those players are delayed from crashing on the inside runs, it increases the chances of breaking a run. Same concept can occur if they overplay the bubble.

Richt can't get that discipline with Kaaya as a runner, so he tries to do it with the bubble. It wasn't successful against FSU. So, it sounds like he's going to use more traditional run sets to get the balance he wants. And instead of running it out of passing formtations, he'll likely throw out of running formations.

And FWIW, all "option" plays are "read" plays. Triple option and run-pass option both require the QB to read the defense, and distribute the ball appropriately.

Dude, listen...

The RPO concepts that WE RUN...do not have QB run aspects built into them. We run a pure RUN/PASS OPTION, meaning the only options are to RUN (hand it off) or PASS (pull it and throw).

WE'RE NOT READING THE CONTAIN PLAYER, SO IT'S IRRELEVANT WHAT HE DOES. WE ARE READING AN "OVER HANG" PLAYER aka A FLAT DEFENDER.

RPO does not = read/option

Why do you guys think they're one in the same?

You can combine QB run concepts with RPO's and it basically becomes a triple option play, but that's not what we do. That's not even what most RPO teams do.

Ok, again...

The "contain" player in an "even front" is the Defensive End. It doesn't matter how disciplined he is versus an RPO because HE'S NOT THE CONFLICT PLAYER. HE'S NOT THE ONE BEING READ BY THE QB. The DE is actually being blocked out by the Offensive Tackle, so he has outside contain regardless of what the QB does.

The defender who's being read is the SECOND LEVEL DEFENDER i.e. THE LINEBACKER. He's the one who's discipline is being tested.

Most RPO teams don't even have a running threat at QB. If you have a mobile Quarterback then you can add some QB running concepts into your RPO game, but QB runs are not a staple of the RPO world.



And FWIW, I'm fully aware that all option plays are "read" plays, however, they're not all called READ/OPTION.

Bubbles have nothing to do with the Defensive Ends. Bubbles influence flat defenders, not DE's.

The bubbles that we run are pure RPO's.

If we have numbers in the box because FSU bumped a Linebacker out to cover bubbles, we hand the ball off.
If FSU keeps the Linebacker in the box to help defend the run, we throw the bubble.

The act of the slot WR bubbling out is what pulls the Linebacker out of the box, thus helping us run the ball. The D-Ends are not an issue.

Most of our bubbles were successful versus FSU so I don't know how he would come to that conclusion you're talking about.

Not trying to be condescending but I don't really think you understand what an RPO concept entails and that's why you keep going back and forth with me. The DE's are meaningless in an RPO. IT'S THE 2nd LEVEL "CONFLICT PLAYER" THAT DETERMINES WHETHER WE CAN RUN THE BALL OR NOT.

 

[The Franchise]

That's not entirely true, but I'm supporting you on these posts because it doesn't have everything to do with QB runs. There seems to be a lot of confusion about RPO on here, and I'm not sure why. It's been broken down time and again.

- Not every RPO is reading the DE; actually, many of them are reading a "stuck in between" LB who is responsible for, say, the "B" gap in run support and the stick route from the slot WR. When he makes his decision on which to cover, the QB either hands off or passes it over him.

- Some RPOs have three options: handoff, QB run, then bubble screen or the like. This is NOT the RPO Richt is running with Kaaya.

- We *have* done well with the passing option in the RPO this year and against FSU. In the GaTech game, it got Coley a TD by zipping it passed a pinching LB's ear. If I remember correctly (from watching in the stadium), in the 3rd quarter, on that huge, huge play where Stacy Coley got tripped up going into the endzone (then got a 5 yard neutral zone infraction immediately after because he was asking to be pulled out of the game and we went tempo), that was also an RPO.

In any case, we're not reading DEs and Kaaya isn't intended to run. We also ran it too much anyway, and Richt apparently admitted that much.

We've had a couple good plays with the RPO game. We run it so much we better have a couple good plays with it.

Problem is that overall it's been an ineffective and spotty element to the offense and Kaaya doesn't appear comfortable with it. It looks awkward and it's not working enough of the time as is evidenced by the 2nd half debacle of 88 yards against a **** D.

So, yeah, we can point to a couple good results we've had with it. But overall it's been ineffective. And the offense is disjointed and seems to be trying to do too many different things.

We haven't had a couple good results, we've been taking chunks out of defenses with it. I charted one of our games and we were averaging over 9 YPP with our gun/RPO stuff.

All those bubble screens that we take for 8+ yards a pop...those are RPO's.
When Walton/Yearby breaks a big run out of the shotgun...it's usually due to an RPO.
Coley's long TD against GT was an RPO.

It's our best offense.

I disagree that it's been effective. Anything we did against some of the garbage on our schedule would work. It was an abomination against the one good team we played, and it resulted in one or two good gains against GT.

Ol' chise, maybe you need to look back at the last 2 games. Or maybe you just didn't recognize which plays were RPO's.

Our highlights from the GT and FSU games are chuck full of RPO's.

Walton's big run Saturday night = RPO
Coley's long TD versus GT = RPO
All of those 8+ yard gains on bubble routes to Njoku/Herndon = RPO's
The successful slant routes to Richards = RPO's

A lot of our big runs came on RPO's.

Maybe you need to rewatch the FSU game and tell me about all those great RPO plays that led us to 260 total yards on a defense that was statistically one of the worst in P5 and lost 2 veteran starters early in our game. Is Erma Lame an RPO buster extraordinaire that no one could have beaten?

The offense, overall, stunk against GT too. I'm not talking about one play here or there that gets your coaching toes all tingly because it looks so perfect on the occasions where it works.

Put Kaaya in the goddam gun. Spread the field. Use the vertical pass game more than once or twice per game. And gash them with quick hitting runs when they start getting the yips trying to cover 4 receivers stretching the field vertically and horizontally.

I've seen enough of that slow-developing RPO **** with Kaaya bumbling around to know it shouldn't be our base offense. Do what works best for him. He's a very limited guy athletically, and I'm not so sure he processes info all that quickly. But he's got a really nice arm and when he gets confident and in a rhythm he can be deadly accurate.

And contrary to popular belief, we have 2 WRs that any team would love to have and a couple good complementary guys. We have 2 NFL TEs who can really run too. There are weapons that should have absolutely destroyed that **** heap defense from FSU. But Rick fcked around with too much disjointed nonsense and we blew it.

 

[Coach Macho]

But...

RPO's are fast developing plays.

 

[Coach Macho]

Actually, you can't help but be condescending. It's your thing. But it's all good! Lol

You keep replying to me from your coaching clinic perspectives.

Have you ever implemented something from a clinic, and found that it didn't work for you and your team strengths?

... We averaged 2.2 yards per rush. The run game was unsuccessful against FSU even if you want to give credit to RPO for when we were able to move the ball. But Richt is saying he used it too much to run the ball, and he didn't have success. He's acknowledging that, so why do you keep replying to me about something Richt is stating, and the stats validate?

The point I believe you're missing, which is obvious, sense you understand the concept of what RPO is and is supposed to do ... Is that we had the numbers we wanted when we ran the ball, and still didn't have success.

So, I'll try a different approach to see if we can find common ground ... Why do you think FSU was able to stifle the run AND limit the bubble game?

Fam ... my point is that, because all options plays are read plays, the read isn't the issue I'm talking about. Maybe others are talking about that, but you quoted me in your response. My point is about what I believe Richt was trying to get by running RPO plays.

IMO, he was using the bubble screens to keep the ends wide, so that his tackles could get help blocking on the inside runs. What he likely figured out from the FSU game is that the bubbles didn't help his tackles. So, he's going to use the TE and FB to do that.

Maybe it works, maybe it doesn't. But that's the point I take from the comment that started this thread. We'll see less RPO, and more 2-back.

Not looking for a ****ing match, but read my post again.

My point isn't about "reading" containment. It's about how disciplined the contain has to be when the QB is a running threat. And if those players are delayed from crashing on the inside runs, it increases the chances of breaking a run. Same concept can occur if they overplay the bubble.

Richt can't get that discipline with Kaaya as a runner, so he tries to do it with the bubble. It wasn't successful against FSU. So, it sounds like he's going to use more traditional run sets to get the balance he wants. And instead of running it out of passing formtations, he'll likely throw out of running formations.

And FWIW, all "option" plays are "read" plays. Triple option and run-pass option both require the QB to read the defense, and distribute the ball appropriately.

Ok, again...

The "contain" player in an "even front" is the Defensive End. It doesn't matter how disciplined he is versus an RPO because HE'S NOT THE CONFLICT PLAYER. HE'S NOT THE ONE BEING READ BY THE QB. The DE is actually being blocked out by the Offensive Tackle, so he has outside contain regardless of what the QB does.

The defender who's being read is the SECOND LEVEL DEFENDER i.e. THE LINEBACKER. He's the one who's discipline is being tested.

Most RPO teams don't even have a running threat at QB. If you have a mobile Quarterback then you can add some QB running concepts into your RPO game, but QB runs are not a staple of the RPO world.



And FWIW, I'm fully aware that all option plays are "read" plays, however, they're not all called READ/OPTION.

Bubbles have nothing to do with the Defensive Ends. Bubbles influence flat defenders, not DE's.

The bubbles that we run are pure RPO's.

If we have numbers in the box because FSU bumped a Linebacker out to cover bubbles, we hand the ball off.
If FSU keeps the Linebacker in the box to help defend the run, we throw the bubble.

The act of the slot WR bubbling out is what pulls the Linebacker out of the box, thus helping us run the ball. The D-Ends are not an issue.

Most of our bubbles were successful versus FSU so I don't know how he would come to that conclusion you're talking about.

Not trying to be condescending but I don't really think you understand what an RPO concept entails and that's why you keep going back and forth with me. The DE's are meaningless in an RPO. IT'S THE 2nd LEVEL "CONFLICT PLAYER" THAT DETERMINES WHETHER WE CAN RUN THE BALL OR NOT.

If you think I'm being condescending then I guess I should just let you be wrong. There's obviously no way I can correct you without being condescending. Truth of the matter is, most people don't like being corrected, so they take it as the other person as being condescending. I'm not being condescending, I'm trying to show/teach you. However, like most people on here, you'd rather be a contrarian and go back and forth with a person who does football for a living and sees RPO's on a daily basis.
Perhaps I should just STFU and let you think that DC's widen their Defensive Ends to stop bubbles. LOL


FSU was able to control our offense because they played a lot of single-high coverage. Single-high not only takes away bubble but it leaves adequate defenders in the box to stop the run.

 

[Coach Macho]

Actually, I'm wrong. I'm watching the 3rd quarter right now and I haven't seen single-high coverage.

What I'm seeing is us marching down the field then throwing a pick in the endzone.
I see our QB throwing a ball in the dirt to an open Coley on 3rd down. (so we punt)
I see Walton breaking a huge run, right after two previous big gains, only to have it called back by a holding.
We then kill the drive by running twice in a row when we need 20 yards for a first down. (making it 3rd & 15)



Still watching.

 

[Coach Macho]

We're simply getting our a$$es kicked up front. Our O-line looks terrible.

 

[Coach Macho]

3rd & 3...

Going in for the game tying score...

We hand the ball off to Walton when FSU has numbers in the box. Plus their DL kicked our a$$. No gain.