Another Top 25
Posted: Fri Jan 18, 2019 6:19 pm
Not much content but a nice little blurb about App.
https://www.sbnation.com/a/college-foot ... t-games#24
https://www.sbnation.com/a/college-foot ... t-games#24
http://www.yosefscabin.com/forum/
Glad the media has noticed it as well. I thought our coaching as far as clock management and play calling last year was below average while everything else was outstanding. I expect a huge improvement in these two things in 2019.Apple@chin1 wrote: ↑Fri Jan 18, 2019 6:38 pmThe Penn State game was voted #24 of the 100 best games of 2018. It said that if it weren’t for poor time management and an ill advised throw to the end zone in overtime, that the game would have had e different ending and that we were one of the best teams in the country. 2019 can’t get here soon enough!
I'm not the poster who mentioned satts clock management, but thank you for bringing this up. Satt had to teach jalin yo dive if he got a first down. I was at my brothers house watching the game and when he scores everyone celebrated...and I just put my hands over my face and said "that's it...we lost". Satt made similar mistake vs troy in 2017, that cost us the game.
The KO was seven yards deep in the end zone. The majority of those aren't returned. The KR danced and hesitated before deciding to bring it out. Our coverage guy missed a tackle that would have nailed him at the 7 yard line and it was off to the races. It was like the hand of fate on that play was directing things against us and for Penn State.
Arsenal App wrote: ↑Mon Jan 21, 2019 6:40 pmThe KO was seven yards deep in the end zone. The majority of those aren't returned. The KR danced and hesitated before deciding to bring it out. Our coverage guy missed a tackle that would have nailed him at the 7 yard line and it was off to the races. It was like the hand of fate on that play was directing things against us and for Penn
7 yds deep? Gotchya...but for some reason I am remembering a shallower kick than that...I do recall the dancing around before bringing it out.
Or, their playmakers (KR, McSorley, Oruwariye) stepping up and making plays down the stretch. Just like Jalen Moore did for us.Arsenal App wrote: ↑Mon Jan 21, 2019 6:40 pmThe KO was seven yards deep in the end zone. The majority of those aren't returned. The KR danced and hesitated before deciding to bring it out. Our coverage guy missed a tackle that would have nailed him at the 7 yard line and it was off to the races. It was like the hand of fate on that play was directing things against us and for Penn State.
Look at it this way. Had they got Jalin to keep the ball in bounds and not score, we could have kneeled the ball or ran up the middle. Then we could have ran the clock down and not had to worry about the kick coverage.
I don't give a crap where our units rank as long as we are 13-0. If we are then I'm sure the defense will be top 15-20 and the offense will be top 20 but as long as we are 13-0 I don't care. If we are 13-0 then GSU, ASU, Troy, etc could be #1 scoring and total offense/defense in the SBC. I want to beat UNC and South Carolina and not just by a field goal but I expect double digit wins in both games.NattyBumppo'sRevenge wrote: ↑Wed Jan 23, 2019 8:54 amPeoples, Evans, Sutton, Zac, Hennigan, Malik, Pearson/Reed, Marcus
Our top rated recruit from 2018 was WR Braden Collins and the TE Kofoed is supposed to be really good, too.
All while returning 4 starters on the O-line. If Drink and company don't produce one of the top scoring offenses in FBS, I'll be disappointed.
All that is true in retrospect but no coach or player is ever going to intentionally run out of bounds with open field ahead of them. There is no guarantee that we punch it across if we do. Fumbles, penalties, sacks....all those are real possibilities in that situation. Never take points off the board.AppStFan1 wrote: ↑Sun Jan 27, 2019 1:44 amLook at it this way. Had they got Jalin to keep the ball in bounds and not score, we could have kneeled the ball or ran up the middle. Then we could have ran the clock down and not had to worry about the kick coverage.
Knowing that we were on the road in a hostile environment, you do not give the other team the ball under any circumstance if you can. You drain the clock, kick a field goal, and get out of their without giving McSorley any shot, even if he has the ball on his own one-yard line.
Actually, I have seen teams use strategy and go down in bounds to run out the clock. We did not need a TD. Just needed to drain the clock down and kick a field goal as time expired. Nothing is guaranteed either way but the smartest thing to do in terms of clock management would have been to not let Penn State get the ball back. We also managed the clock poorly against Tennessee and a few other games. I would have said the fact we had a good FCS caliber QB then was the difference but seeing our poor clock management and bad play calls at times in 2018 showed me Scott still has to develop in that area. Hopefully for him he improves on that in the ACC because the coaching is a lot better up there.Yosef84 wrote: ↑Sun Jan 27, 2019 8:15 amAll that is true in retrospect but no coach or player is ever going to intentionally run out of bounds with open field ahead of them. There is no guarantee that we punch it across if we do. Fumbles, penalties, sacks....all those are real possibilities in that situation. Never take points off the board.AppStFan1 wrote: ↑Sun Jan 27, 2019 1:44 amLook at it this way. Had they got Jalin to keep the ball in bounds and not score, we could have kneeled the ball or ran up the middle. Then we could have ran the clock down and not had to worry about the kick coverage.
Knowing that we were on the road in a hostile environment, you do not give the other team the ball under any circumstance if you can. You drain the clock, kick a field goal, and get out of their without giving McSorley any shot, even if he has the ball on his own one-yard line.
It is when you give as much time as we did. Score with say 15 seconds left but my goodness don't give a team like Penn State at home with a minute or more and a timeout or two.Yosef84 wrote: ↑Mon Jan 28, 2019 2:05 pmI just can't include a successful TD play as "poor clock management." I really do understand what you're saying and I know it has happened, but it is by far the exception. The closest thing to guaranteed is for the RB to keep running with there is green grass in front of him. If he had made the TD on a long pass, I'd say it was a coaching decision (poor clock management) especially if we were moving the ball on the ground. I agree there were games where clock management was a weakness. I just don't see this as one of them.