This was definitely a tough loss. To make matters worse, I am one of those YouTubeTV subscribers that lost the game with around 3 mins to go. To say I was angry was an understatement. Finished the game listening to it on the radio. Perhaps it was a blessing in disguise to not see the ending.
There's no doubt that this one will hurt for a while, but nowhere near the hurt these players must be feeling. Credit to NDSU. They beat us and deserved to win.
It is a shame that bad officiating for both sides affected the game in different ways. None of it should have happened. I have never seen 20+ seconds of clock time just vanish with no explanation and (even worse) no acknowledgement or desire to fix it. Can't say that any of it would have changed the outcome, because we'll never know. NDSU still won the game and they were the better team.
I think everyone can agree that was some of the WORST color commentary I have ever heard on TV.
The only thing that makes this loss tolerable is that we are leaving FCS behind. If NDSU ever wants to play us again, they will have to come to Harrisonburg. They are going to continue to be at the top of the FCS for years to come. Good for them.
Ready to move on to the big time. I know there will be some growing pains, but I'm ready and eager to endure them.
As others have said, I do think our best days are ahead of us.
Time to look forward.

(12-20-2021 11:40 AM)JMUDukes1750 Wrote:  The non call on a JMU delay of game was because the operator didn't reset the play clock from the prior play. As you can see, the 3rd and 1, JMU snapped with :22 left on the play clock. After the first down, the clock should have reset to :40, but it stayed at :22. JMU didn't even huddle, and got the play off well before :40.

https://youtu.be/NFDtEeXqJ_o?t=5738

Good catch, that should shut up our new found troll. I wonder what the in stadium scoreboard read at that moment because they players never acted like they were hurrying to beat the clock and they took 4 seconds too long. That clock is an ESPN graphic and might not have been synced with the actual scoreboard clock, so it’s possible at that moment the score clocks visible in the stadium to players and officials was properly reset. That said, whoever controlled the clock this game ought to be relegated to pee wee football and far away from this neck roll football.

(12-20-2021 11:40 AM)JMUDukes1750 Wrote:  NDSU played better, and won. They don't beat themselves, and follow their formula to sustained success. If JMU executed on the plays that were there, the clock operator failures would not have mattered. Things happen, and breaks happen for some teams. Great teams should overcome them, JMU didn't.

I also fully acknowledge that you do not care about what I'll type out next, because it doesn't change the result, you will likely either just point to something else in the game and not acknowledge the items below, or insult the use of the 10 minutes of time I used to look these up.

With that said:

There was no error on NDSU's delay of game after the TD. The 40 second play clock started immediately after the TD, just as it did on NDSU's first TD, just like it did after both of JMU's TD. The other three occurrences, both teams were able to get the snap of well before the expiration of the play clock. Entz's indecisiveness, and inability to have a play ready cost NDSU, not the clock operator.

1st NDSU TD (you can see the play clock ticking down mid celebration): https://youtu.be/NFDtEeXqJ_o?t=800
1st JMU TD (play clock resets to 40 after TD, disappears for 25 seconds, comes back with 15 on the clock while JMU kicks): https://youtu.be/NFDtEeXqJ_o?t=3819
2nd JMU TD (same as above): https://youtu.be/NFDtEeXqJ_o?t=4964
2nd NDSU TD (same as 1st NDSU TD, they even reset it at 25 to give NDSU a few extra seconds): https://youtu.be/NFDtEeXqJ_o?t=5382


The non call on a JMU delay of game was because the operator didn't reset the play clock from the prior play. As you can see, the 3rd and 1, JMU snapped with :22 left on the play clock. After the first down, the clock should have reset to :40, but it stayed at :22. JMU didn't even huddle, and got the play off well before :40.

https://youtu.be/NFDtEeXqJ_o?t=5738

The :28 seconds JMU lost have been addressed earlier.

Again, things happen, and JMU could have overcome, but they didn't. Good luck vs. Montana St, and the future of the program.

So I was actually pretty close when I said that knowing that clock operator, he probably set it to 12 seconds before our play. I stand by my statement that ndsu coaches and players are class acts and run a great program. I also stand by my statement that the clock issue(s) were intentional and that the ndsu official timekeeper is crooked.

(12-20-2021 12:13 PM)Polish Hammer Wrote:  

(12-20-2021 11:40 AM)JMUDukes1750 Wrote:  The non call on a JMU delay of game was because the operator didn't reset the play clock from the prior play. As you can see, the 3rd and 1, JMU snapped with :22 left on the play clock. After the first down, the clock should have reset to :40, but it stayed at :22. JMU didn't even huddle, and got the play off well before :40.

https://youtu.be/NFDtEeXqJ_o?t=5738

Good catch, that should shut up our new found troll. I wonder what the in stadium scoreboard read at that moment because they players never acted like they were hurrying to beat the clock and they took 4 seconds too long. That clock is an ESPN graphic and might not have been synced with the actual scoreboard clock, so it’s possible at that moment the score clocks visible in the stadium to players and officials was properly reset. That said, whoever controlled the clock this game ought to be relegated to pee wee football and far away from this neck roll football.

That video also showed a moment that I had forgotten about. Same drive, but a few plays later. If we simply don't gain any yards ( an incomplete pass or stuffed at the line) when we were 3rd & 5 from the NDSU 30, we would be lining up for an Ethan Ratke 47 yd FG attempt. I like our odds to convert. As it was, their edge rusher blew by Fornadel and sacked CJ. So we had to punt. Being down only 3 on our last two drives creates a much different dynamic.

(12-20-2021 02:52 PM)olddawg Wrote:  

(12-20-2021 12:13 PM)Polish Hammer Wrote:  

(12-20-2021 11:40 AM)JMUDukes1750 Wrote:  The non call on a JMU delay of game was because the operator didn't reset the play clock from the prior play. As you can see, the 3rd and 1, JMU snapped with :22 left on the play clock. After the first down, the clock should have reset to :40, but it stayed at :22. JMU didn't even huddle, and got the play off well before :40.

https://youtu.be/NFDtEeXqJ_o?t=5738

Good catch, that should shut up our new found troll. I wonder what the in stadium scoreboard read at that moment because they players never acted like they were hurrying to beat the clock and they took 4 seconds too long. That clock is an ESPN graphic and might not have been synced with the actual scoreboard clock, so it’s possible at that moment the score clocks visible in the stadium to players and officials was properly reset. That said, whoever controlled the clock this game ought to be relegated to pee wee football and far away from this neck roll football.

That video also showed a moment that I had forgotten about. Same drive, but a few plays later. If we simply don't gain any yards ( an incomplete pass or stuffed at the line) when we were 3rd & 5 from the NDSU 30, we would be lining up for an Ethan Ratke 47 yd FG attempt. I like our odds to convert. As it was, their edge rusher blew by Fornadel and sacked CJ. So we had to punt. Being down only 3 on our last two drives creates a much different dynamic.

Fornadel got beat outside, but Cole has to get rid of the ball, especially if VanHorse isn’t going to pick up that man and releases quickly. That “sack” might have had the least amount of physical contact possible.

(12-20-2021 03:02 PM)Polish Hammer Wrote:  

(12-20-2021 02:52 PM)olddawg Wrote:  

(12-20-2021 12:13 PM)Polish Hammer Wrote:  

(12-20-2021 11:40 AM)JMUDukes1750 Wrote:  The non call on a JMU delay of game was because the operator didn't reset the play clock from the prior play. As you can see, the 3rd and 1, JMU snapped with :22 left on the play clock. After the first down, the clock should have reset to :40, but it stayed at :22. JMU didn't even huddle, and got the play off well before :40.

https://youtu.be/NFDtEeXqJ_o?t=5738

Good catch, that should shut up our new found troll. I wonder what the in stadium scoreboard read at that moment because they players never acted like they were hurrying to beat the clock and they took 4 seconds too long. That clock is an ESPN graphic and might not have been synced with the actual scoreboard clock, so it’s possible at that moment the score clocks visible in the stadium to players and officials was properly reset. That said, whoever controlled the clock this game ought to be relegated to pee wee football and far away from this neck roll football.

That video also showed a moment that I had forgotten about. Same drive, but a few plays later. If we simply don't gain any yards ( an incomplete pass or stuffed at the line) when we were 3rd & 5 from the NDSU 30, we would be lining up for an Ethan Ratke 47 yd FG attempt. I like our odds to convert. As it was, their edge rusher blew by Fornadel and sacked CJ. So we had to punt. Being down only 3 on our last two drives creates a much different dynamic.

Fornadel got beat outside, but Cole has to get rid of the ball, especially if VanHorse isn’t going to pick up that man and releases quickly. That “sack” might have had the least amount of physical contact possible.

When I get up the courage to watch the game on replay, I want to see how they managed to stop our running, short-passing and long-passing games so effectively. I really didn't think they could all be stopped. I know Cole picked a bad day to be mortal, but I don't think it's just that.

Liam got beat on the final play too. Unfortunate way to end a great career

(12-20-2021 12:13 PM)Polish Hammer Wrote:  

(12-20-2021 11:40 AM)JMUDukes1750 Wrote:  The non call on a JMU delay of game was because the operator didn't reset the play clock from the prior play. As you can see, the 3rd and 1, JMU snapped with :22 left on the play clock. After the first down, the clock should have reset to :40, but it stayed at :22. JMU didn't even huddle, and got the play off well before :40.

https://youtu.be/NFDtEeXqJ_o?t=5738

Good catch, that should shut up our new found troll. I wonder what the in stadium scoreboard read at that moment because they players never acted like they were hurrying to beat the clock and they took 4 seconds too long. That clock is an ESPN graphic and might not have been synced with the actual scoreboard clock, so it’s possible at that moment the score clocks visible in the stadium to players and officials was properly reset. That said, whoever controlled the clock this game ought to be relegated to pee wee football and far away from this neck roll football.

There was a lot of fans that started groaning about it so I assume that was reading zero also. I didn't see it myself and at the time I wasn't sure what people were upset about but looking at the replay that's what it was. And yes it was correct that JMU didn't get a delay of game on that.

(12-20-2021 03:14 PM)94computerguy Wrote:  

(12-20-2021 03:02 PM)Polish Hammer Wrote:  

(12-20-2021 02:52 PM)olddawg Wrote:  

(12-20-2021 12:13 PM)Polish Hammer Wrote:  

(12-20-2021 11:40 AM)JMUDukes1750 Wrote:  The non call on a JMU delay of game was because the operator didn't reset the play clock from the prior play. As you can see, the 3rd and 1, JMU snapped with :22 left on the play clock. After the first down, the clock should have reset to :40, but it stayed at :22. JMU didn't even huddle, and got the play off well before :40.

https://youtu.be/NFDtEeXqJ_o?t=5738

Good catch, that should shut up our new found troll. I wonder what the in stadium scoreboard read at that moment because they players never acted like they were hurrying to beat the clock and they took 4 seconds too long. That clock is an ESPN graphic and might not have been synced with the actual scoreboard clock, so it’s possible at that moment the score clocks visible in the stadium to players and officials was properly reset. That said, whoever controlled the clock this game ought to be relegated to pee wee football and far away from this neck roll football.

That video also showed a moment that I had forgotten about. Same drive, but a few plays later. If we simply don't gain any yards ( an incomplete pass or stuffed at the line) when we were 3rd & 5 from the NDSU 30, we would be lining up for an Ethan Ratke 47 yd FG attempt. I like our odds to convert. As it was, their edge rusher blew by Fornadel and sacked CJ. So we had to punt. Being down only 3 on our last two drives creates a much different dynamic.

Fornadel got beat outside, but Cole has to get rid of the ball, especially if VanHorse isn’t going to pick up that man and releases quickly. That “sack” might have had the least amount of physical contact possible.

When I get up the courage to watch the game on replay, I want to see how they managed to stop our running, short-passing and long-passing games so effectively. I really didn't think they could all be stopped. I know Cole picked a bad day to be mortal, but I don't think it's just that.

It seemed like they only brought 4 and dropped 7 so much I wonder why we couldn’t hit the quick passes or get the run game going better either.

Cole was off at the worst possible time. Really cost us the game.

Sent from my SM-G988U using Tapatalk

(12-20-2021 03:14 PM)olddawg Wrote:  Liam got beat on the final play too. Unfortunate way to end a great career

Yeah, 4 year starter, even though the last 2 were injury shortened. All CAA 2018 & 2019. Near consensus AA in 2019. Gave up a sack in the Montana game, and got beat a couple times vs NDSU. I'm wondering if he wasn't anywhere near 100% after coming back from that injury, even though he came back late Oct.

(12-20-2021 11:40 AM)JMUDukes1750 Wrote:  NDSU played better, and won. They don't beat themselves, and follow their formula to sustained success. If JMU executed on the plays that were there, the clock operator failures would not have mattered. Things happen, and breaks happen for some teams. Great teams should overcome them, JMU didn't.

I also fully acknowledge that you do not care about what I'll type out next, because it doesn't change the result, you will likely either just point to something else in the game and not acknowledge the items below, or insult the use of the 10 minutes of time I used to look these up.

With that said:

There was no error on NDSU's delay of game after the TD. The 40 second play clock started immediately after the TD, just as it did on NDSU's first TD, just like it did after both of JMU's TD. The other three occurrences, both teams were able to get the snap of well before the expiration of the play clock. Entz's indecisiveness, and inability to have a play ready cost NDSU, not the clock operator.

1st NDSU TD (you can see the play clock ticking down mid celebration): https://youtu.be/NFDtEeXqJ_o?t=800
1st JMU TD (play clock resets to 40 after TD, disappears for 25 seconds, comes back with 15 on the clock while JMU kicks): https://youtu.be/NFDtEeXqJ_o?t=3819
2nd JMU TD (same as above): https://youtu.be/NFDtEeXqJ_o?t=4964
2nd NDSU TD (same as 1st NDSU TD, they even reset it at 25 to give NDSU a few extra seconds): https://youtu.be/NFDtEeXqJ_o?t=5382


The non call on a JMU delay of game was because the operator didn't reset the play clock from the prior play. As you can see, the 3rd and 1, JMU snapped with :22 left on the play clock. After the first down, the clock should have reset to :40, but it stayed at :22. JMU didn't even huddle, and got the play off well before :40.

https://youtu.be/NFDtEeXqJ_o?t=5738

The :28 seconds JMU lost have been addressed earlier.

Again, things happen, and JMU could have overcome, but they didn't. Good luck vs. Montana St, and the future of the program.

Just watched NDSUs last offensive series. On 3rd down the play ends with 1:48 on the clock, the play clock gets reset to 40 and doesn’t start to run until 1:40. If I watch some more I’ll probably just piss myself off even more as I’m sure it couldn’t have all been by accident. Add in the extra time and you don’t have a guy running for his life on the last two plays trying to get something off. Then again if Cole doesn’t scramble and then stumble eating the ball on the next to last play with receivers wide open and right near the sideline he doesn’t rush that last play.

(12-20-2021 03:14 PM)94computerguy Wrote:  

(12-20-2021 03:02 PM)Polish Hammer Wrote:  

(12-20-2021 02:52 PM)olddawg Wrote:  

(12-20-2021 12:13 PM)Polish Hammer Wrote:  

(12-20-2021 11:40 AM)JMUDukes1750 Wrote:  The non call on a JMU delay of game was because the operator didn't reset the play clock from the prior play. As you can see, the 3rd and 1, JMU snapped with :22 left on the play clock. After the first down, the clock should have reset to :40, but it stayed at :22. JMU didn't even huddle, and got the play off well before :40.

https://youtu.be/NFDtEeXqJ_o?t=5738

Good catch, that should shut up our new found troll. I wonder what the in stadium scoreboard read at that moment because they players never acted like they were hurrying to beat the clock and they took 4 seconds too long. That clock is an ESPN graphic and might not have been synced with the actual scoreboard clock, so it’s possible at that moment the score clocks visible in the stadium to players and officials was properly reset. That said, whoever controlled the clock this game ought to be relegated to pee wee football and far away from this neck roll football.

That video also showed a moment that I had forgotten about. Same drive, but a few plays later. If we simply don't gain any yards ( an incomplete pass or stuffed at the line) when we were 3rd & 5 from the NDSU 30, we would be lining up for an Ethan Ratke 47 yd FG attempt. I like our odds to convert. As it was, their edge rusher blew by Fornadel and sacked CJ. So we had to punt. Being down only 3 on our last two drives creates a much different dynamic.

Fornadel got beat outside, but Cole has to get rid of the ball, especially if VanHorse isn’t going to pick up that man and releases quickly. That “sack” might have had the least amount of physical contact possible.

When I get up the courage to watch the game on replay, I want to see how they managed to stop our running, short-passing and long-passing games so effectively. I really didn't think they could all be stopped. I know Cole picked a bad day to be mortal, but I don't think it's just that.

I wouldn’t say they stopped the short passing game. VanHorse was uncoverable out of the backfield. It was like a default running game to the edge. We discussed it a lot this season why he wasn’t used even more as a RB receiver. They maxed him out against ND State.
He had 25 receptions in 11 games coming into the semis.
He had 8 receptions vs ND State. Very effective out of the backfield. Probably would have been a good target when JMU got in the red zone late and looking to take the lead.

(12-20-2021 03:22 PM)Chalupa Batman Wrote:  

(12-20-2021 12:13 PM)Polish Hammer Wrote:  

(12-20-2021 11:40 AM)JMUDukes1750 Wrote:  The non call on a JMU delay of game was because the operator didn't reset the play clock from the prior play. As you can see, the 3rd and 1, JMU snapped with :22 left on the play clock. After the first down, the clock should have reset to :40, but it stayed at :22. JMU didn't even huddle, and got the play off well before :40.

https://youtu.be/NFDtEeXqJ_o?t=5738

Good catch, that should shut up our new found troll. I wonder what the in stadium scoreboard read at that moment because they players never acted like they were hurrying to beat the clock and they took 4 seconds too long. That clock is an ESPN graphic and might not have been synced with the actual scoreboard clock, so it’s possible at that moment the score clocks visible in the stadium to players and officials was properly reset. That said, whoever controlled the clock this game ought to be relegated to pee wee football and far away from this neck roll football.

There was a lot of fans that started groaning about it so I assume that was reading zero also. I didn't see it myself and at the time I wasn't sure what people were upset about but looking at the replay that's what it was. And yes it was correct that JMU didn't get a delay of game on that.

I was at the game. Our entire section was screaming for at least three seconds prior to the snap that the play clock had read zero.

(12-20-2021 09:02 PM)WeAreThePride Wrote:  

(12-20-2021 03:22 PM)Chalupa Batman Wrote:  

(12-20-2021 12:13 PM)Polish Hammer Wrote:  

(12-20-2021 11:40 AM)JMUDukes1750 Wrote:  The non call on a JMU delay of game was because the operator didn't reset the play clock from the prior play. As you can see, the 3rd and 1, JMU snapped with :22 left on the play clock. After the first down, the clock should have reset to :40, but it stayed at :22. JMU didn't even huddle, and got the play off well before :40.

https://youtu.be/NFDtEeXqJ_o?t=5738

Good catch, that should shut up our new found troll. I wonder what the in stadium scoreboard read at that moment because they players never acted like they were hurrying to beat the clock and they took 4 seconds too long. That clock is an ESPN graphic and might not have been synced with the actual scoreboard clock, so it’s possible at that moment the score clocks visible in the stadium to players and officials was properly reset. That said, whoever controlled the clock this game ought to be relegated to pee wee football and far away from this neck roll football.

There was a lot of fans that started groaning about it so I assume that was reading zero also. I didn't see it myself and at the time I wasn't sure what people were upset about but looking at the replay that's what it was. And yes it was correct that JMU didn't get a delay of game on that.

I was at the game. Our entire section was screaming for at least three seconds prior to the snap that the play clock had read zero.

We’re you yelling that they didn’t reset it and started it at :22? We’re you yelling when you ran 75 seconds off on one play? It was a national semifinal game so they had a seasoned hand operating the clock, which with these snafus leads people to believe it wasn’t exactly accidental..

Congrats on another fine season Dukes

Best Wishes in FBS