Originally posted by Jose Bagg I don't think this is going to ease your pain. What we have here is a case where the clock expired trying to get your FG unit on the field. There was 46 seconds left, you ran a very long play. It takes time to get everyone else down field to set up for the FG. I don't think this is a clock management issue. In the NFL you see things like this, and sometimes they get the FG play off, sometimes they don't. Tough break.
The real question we should be asking is why didn't the WR run to the sidelines so he could step out when he felt the tacklers getting too close?
No, it's definitely a problem with clock management. In any level of football, they would have gotten their asses down the field immediately and spiked the ball to stop the clock or as you mentioned, the receiver should have stepped out of bounds. Either way, it's still clock management.
Not a "Bug" though, just a lack of implantation of a time management system. It has been suggested in the suggestion forum, and Jed said he thought Bort has already discussed it will be implemented sometime.
Originally posted by JDaniels127 Not a "Bug" though, just a lack of implantation of a time management system. It has been suggested in the suggestion forum, and Jed said he thought Bort has already discussed it will be implemented sometime.
I've lost 3 close games thanks to it this year.
We just keep moving on though.
^ This.
We just don't have the options, YET. I am sure we will at some point. An option to spike the ball in certain situations, or to use a timeout only in certain situations would work wonders.
For now, all you can do is set up an input with the absolute longest FG your kicker can possibly make, and set it to around 48 seconds or so.
For those with it at 40 seconds, you'll eventually get burned in the current system. I've seen it happen. 45 is probably enough, but we've got ours at 48. It's far from perfect, but it's the best we can do right now.