menu
Logo
99+
Bobcat Attack Menu
Logo
99+
Ohio Football Topic
Topic: Official Game 8 Thread: Kent St.
Page: 5 of 5
mf279801
General User
M279801
Member Since: 8/6/2010
Location: Newark, DE
Post Count: 2,486
person
mail
mf279801
mail
Posted: 10/24/2016 4:04 PM
settings_applications edit_note
Ted Thompson wrote:expand_more
I'll ask the same question I did after the BG game. Kent St. called their last timeout after 1st down and there was 1:27 left. Why did we run a play? Two kneeldowns and it's a ball game. Brown ran for a first down on the ensuing play but that ball almost got stripped from behind.
you are right, no need to take a risk.
we would still need three plays. :40 + :40 = 1:20

This brings up a question... What determines a 25 second play clock vs 40? I can't tell which one applies to which situation.
But the plays themselves take time. So just wait a second and kneel. After they got the first down, Maxwell was waiting to kneel (even though, at that point, he didn't need to).
Announcing that you are taking a knee gives the QB and other protections from being blown up. Not going directly down after announcing you are taking a knee is a penalty of 15 yards, and will cause the clock to stop until the next snap under the consume, conserve principle. When under a :40 second clock, the clock begins as soon as the play is over, with no regards to how slow or fast people move to un-pile, and get set. Before the :40, teams and officials could manipulate the pace at the end of a game if it was needed. Not now.
But you can wait to take the knee. I see it all the time and have never seen a penalty. We're already taking a shotgun snap, so I don't see how you can announce you're taking a knee without actually taking the knee.
I've never seen a team get flagged for taking the practice kick when the end-of-game FG attempt has been iced either...wait...crap
Brian Smith (No, not that one)
General User
BSNNTO
Member Since: 2/4/2005
Post Count: 3,057
person
mail
Brian Smith (No, not that one)
mail
Posted: 10/24/2016 4:24 PM
settings_applications edit_note
You know what would be crazy? If a team got called for a safety when its quarterback was at the 3-yard line and it was not reviewable? Can you imagine?
bobcatsquared
General User
B
Member Since: 12/20/2004
Post Count: 5,846
person
mail
bobcatsquared
mail
Posted: 10/24/2016 5:08 PM
settings_applications edit_note
Alright, BillytheCat, and any others with knowledge, here's one that I think changed in recent years and I still don't comprehend.

How come the clock doesn't always stop when you run out of bounds? Used to be the clock would always stop after a player goes out of bounds. Doesn't seem to be the case the last few years. Only in certain situations. Am I wrong? Or has the rule changed? If so, what are the changes?
Monroe Slavin
General User
MS
Member Since: 12/21/2004
Location: Oxnard, CA
Post Count: 9,121
person
mail
Monroe Slavin
mail
Posted: 10/24/2016 5:36 PM
settings_applications edit_note
Brian Smith wrote:expand_more
You know what would be crazy? If a team got called for a safety when its quarterback was at the 3-yard line and it was not reviewable? Can you imagine?

How about if we were playing BG and the refs took a mysterious time out stoppage mid fourth quarter, only to explain that they were huddling to determine what the down was--when everyone else in the stadium and watching the game knew what the down was because absolutely nothing unusual had happened which would cause one to lose track of the down?
C Money
General User
Member Since: 8/28/2010
Post Count: 3,420
mail
C Money
mail
Posted: 10/24/2016 5:47 PM
settings_applications edit_note
bobcatsquared wrote:expand_more
Alright, BillytheCat, and any others with knowledge, here's one that I think changed in recent years and I still don't comprehend.

How come the clock doesn't always stop when you run out of bounds? Used to be the clock would always stop after a player goes out of bounds. Doesn't seem to be the case the last few years. Only in certain situations. Am I wrong? Or has the rule changed? If so, what are the changes?

I think if the player is knocked backwards out of bounds, it is treated as though he was tackled in bounds. But if the player runs out of bounds of his own volition, or is moving forward when knocked out of bounds, the clock stops.

(That's just based on my observation. Not sure if that rule changed in the past few years, but I have noticed that seems to be the way the refs call it now.)
BillyTheCat
General User
BTC
Member Since: 10/6/2012
Post Count: 10,795
person
mail
BillyTheCat
mail
Posted: 10/24/2016 6:03 PM
settings_applications edit_note
bobcatsquared wrote:expand_more
Alright, BillytheCat, and any others with knowledge, here's one that I think changed in recent years and I still don't comprehend.

How come the clock doesn't always stop when you run out of bounds? Used to be the clock would always stop after a player goes out of bounds. Doesn't seem to be the case the last few years. Only in certain situations. Am I wrong? Or has the rule changed? If so, what are the changes?
Depends, is there forward progress or did the runner simply go OB. If hit and knocked sideways then the official will be winding the clock signifying he has forward progress spot. If the runner steps out on his own, or knocked forward out, you would have a stoppage.

HOWEVER with the new timing rules a few years ago, going OB does not really matter as the clock is only stopped until the ball is thrown back to the hash marks.

Note, under 2:00 in each half you have traditional timing rules.
bobcatsquared
General User
B
Member Since: 12/20/2004
Post Count: 5,846
person
mail
bobcatsquared
mail
Posted: 10/24/2016 6:05 PM
settings_applications edit_note
Thanks.

Although not knowing the new rules (new, right?) it seemed that what happened at the end of halves was different than what happened the rest of the game.
OhioCatFan
General User
Member Since: 12/20/2004
Location: Athens, OH
Post Count: 15,683
mail
OhioCatFan
mail
Posted: 10/24/2016 8:07 PM
settings_applications edit_note
bobcatsquared wrote:expand_more
Alright, BillytheCat, and any others with knowledge, here's one that I think changed in recent years and I still don't comprehend.

How come the clock doesn't always stop when you run out of bounds? Used to be the clock would always stop after a player goes out of bounds. Doesn't seem to be the case the last few years. Only in certain situations. Am I wrong? Or has the rule changed? If so, what are the changes?
Even I know the answer to that. The new rule specifies a stoppage of the clock after run out of bounds until the ball is hiked only in the last two minutes, not throughout the game as previously. A run out of bounds during the rest of the game stops the clock only until it's marked ready for play by the official. BTC can fine-tune this, I'm sure.

Edit: I see that BTC has already chimed in. I missed that when I first skimmed through the thread. Glad to see that this once I actually did know basically what I was talking about. I guess my only error was that prior to the last two minutes the ball is ready for play when it it's thrown in not when the ready signal is given.
Last Edited: 10/24/2016 8:13:45 PM by OhioCatFan
Showing Messages: 101 - 108 of 108
reply
vertical_align_top
vertical_align_center
vertical_align_bottom
add_comment
chevron_backward
MAC News Links



extra small (< 576px)
small (>= 576px)
medium (>= 768px)
large (>= 992px)
x-large (>= 1200px)
xx-large (>= 1400px)