Guvner
Last second field goal logic?
February 22, 2011 at 01:33AM View BBCode
Gene Upshaw League - Baton Rouge
http://football.simdynasty.com/boxscore.jsp?boxscoreid=5653
I was down by 3 pts with under 30 seconds to play inside the 7 yard line (first down) and my team called a time out. Instead of kicking to tie the game my guys ran the ball, didn't score, and lost the game.
I was using the default setting for last minute field goals and it appears as though my guys should have attempted to tie the game instead of going for the win, even on first down.
Am I misinterpreting or misreading the Kicking rule? Does something else override the decision to kick in this situation?
Guvner
Kingturtle
February 22, 2011 at 01:49AM View BBCode
default settings say
*"At the end of the game, on any down, if tied or behind by 3 or less, with less than 30 seconds remaining and no time outs remaining" - you meet all that criteria
*"and within 30 yards of the goal line" - you meet that criteria
*"and the estimated chance of making a field goal is at least 50%" - your kicker has an A- kick accuracy, and a C+ execution. including the pre-season he's 7 for 8 on FGs longer than this one.
so i agree....this doesn't make sense.
phen0m
February 22, 2011 at 05:05PM View BBCode
I also had a problem with something similiar
http://football.simdynasty.com/boxscore.jsp?boxscoreid=7573&thid=763
00:27. SAS 1/10 BR 11 1st and 10 for the Sasquatch, they line up in a Pro Set; the Crawfish line up in a 4-3.
Wilford Rocker takes the snap, hands off to Mark Ambrose.
Mark Ambrose runs up the left for a 4 yard loss.
The Saskatchewan Sasquatch call a time out. They have 0 remaining.
00:22. SAS 2/14 BR 15 2nd and 14 for the Sasquatch, they line up in a I Formation; the Crawfish line up in a 4-3.
Wilford Rocker takes the snap, hands off to Mark Ambrose.
The linebackers are blitzing!
Mark Ambrose runs up the middle for a 2 yard gain.
00:10 SAS 3/12 BR 13 3rd and 12 for the Sasquatch, they line up in a Field Goal/PAT; the Crawfish line up in a Field Goal/PAT Block.
Ken Wells prepares to attempt a field goal for Saskatchewan, Al Buckhalter holding.
Time expires before the snap.
00:00 SAS --- BR 13 End of 2nd quarter.
Baton Rouge Crawfish 3, Saskatchewan Sasquatch 7
Heres what my settings are
At the end of the first half, on any down, with less than 30 seconds remaining and no time outs remaining (or 6 or fewer seconds with timeouts remaining), and within 40 yards of the goal line and the estimated chance of making a field goal is at least 25%, attempt a field goal.
We should have kicked the FG after the first run when we used our last timeout... there was less than 30 seconds left, and clearly the 32 yard FG had to be at least a 25% shot (clear day, not much wind, best kicker in the league).
dirtdevil
February 22, 2011 at 07:48PM View BBCode
Originally posted by Kingturtle
default settings say
*"At the end of the game, on any down, if tied or behind by 3 or less, with less than 30 seconds remaining and no time outs remaining" - you meet all that criteria
no he doesn't. he had the time out, and used it. it was the running play thereafter that ran out the clock. same in phenom's scenario. the issue is, after calling the time out followed by a running play, ABE (or whatever the appropriate acronym is here) isn't spiking the ball to stop the clock, which is allowing time to run out before the kick gets off.
Kingturtle
February 22, 2011 at 09:01PM View formatted
You are viewing the raw post code; this allows you to copy a message with BBCode formatting intact.
No, at 00:18 "they line up in a Pro Set; the Reign line up in a 4-3. Frankie Sacca takes the snap, hands off to Robbie Durham. Robbie Durham runs up the right for a 3 yard gain. The Baton Rouge Bandits call a time out. They have 0 remaining."
Now there are 13 seconds remaining. The clock is stopped. and he meets this criteria: any down. behind by 3 or less. with less that 30 seconds left. with no time outs remaining.
"At the end of the game, on any down, if tied or behind by 3 or less, with less than 30 seconds remaining and no time outs remaining"
phen0m
February 22, 2011 at 09:08PM View BBCode
Originally posted by dirtdevil
Originally posted by Kingturtle
default settings say
*"At the end of the game, on any down, if tied or behind by 3 or less, with less than 30 seconds remaining and no time outs remaining" - you meet all that criteria
no he doesn't. he had the time out, and used it. it was the running play thereafter that ran out the clock. same in phenom's scenario. the issue is, after calling the time out followed by a running play, ABE (or whatever the appropriate acronym is here) isn't spiking the ball to stop the clock, which is allowing time to run out before the kick gets off.
What? There should be no running play or having to spike the ball, once your last timeout is used and you meet the criteria you should be kicking a field goal. Unless your saying that AFE counts the timeout towards the next play rather than the play the timeout is called after, which would be pretty retarded.
nuzzy62
February 23, 2011 at 02:25AM View BBCode
I posted this in support a few days ago and Chris says there will be a spike the ball option. It will vary between eight to 15 seconds so there's no guarantee with 12 seconds to go it will happen.
My team also has called time outs when the other team is closing within field goal range, at the end of a half/game - which doesn't make any sense but this will get fixed too.
Admin
February 24, 2011 at 08:16AM View BBCode
Originally posted by nuzzy62
I posted this in support a few days ago and Chris says there will be a spike the ball option. It will vary between eight to 15 seconds so there's no guarantee with 12 seconds to go it will happen.
This isn't actually a spike option, just a reduction in the amount of time it takes to get the kicking unit on the field.
I have a feeling that what is being described here is an actual bug, or at the very least a mismatch in how the rule is being applied vs. the description of it.
Of course, my usual field goal caveat applies in that if the ball is being kicked into the wind, the percentage may be lower than the threshold. But Phenom's description leads me to believe it's a bug.
--Chris
Pages: 1