User Pass
Home Sign Up Contact Log In
Link
 
either a problem with timeout logic or something real crazy stuff like a 6 yard run takes 29 seconds from the clock

1st & 10 at 23 yd line, 2 timeouts left
http://goallineblitz.com/game/replay.pl?game_id=1450938&pbp_id=7000890

afte that timeout called with 1 second left and FG kicked
http://goallineblitz.com/game/replay.pl?game_id=1450938&pbp_id=7000891

Edited by VolBrian on Dec 12, 2010 12:32:18 (Closed)
Edited by VolBrian on Dec 5, 2010 09:36:02 (Not likely a bug)
 
Link
 
yup
 
VolBrian
Rocky Top
offline
Link
 
Originally posted by Changelog
Dec 2, 2010
- Change chip blocking method to slow defender instead of pushing him around; fixes issue with too-fast defenders after chip block speed boost
- Fix time remaining settings at end of half to work like they used to (more intuitively)

Nov 18, 2010
- Require at least 15 seconds left to be able to auto run clock down to 1 on game winning FG attempt

Nov 17, 2010
- Allow clock to run down to 1 second or as much as possible when attempting to kick the game winning field goal
- Adjust 4th quarter timeout logic for use of 3rd timeout to use more freely when trailing


I think what you are seeing here is a result of the above tweaks to the TO logic.

What likely happened in the scenario you posted is that the run play took about 15 seconds from snap to re-spot, and then the auto-runoff occurred since there would have been 15 seconds or left remaining. The clock ran down to one, called a TO, and kicked the FG.

I don't think it's a bug tbh. They've set it up this way.

Not likely a bug
 
GMathiasf
offline
Link
 
I would actually say that if there really was two timeouts left, that would be a bug, or at least a logic fail. Plenty of time to call a timeout and run another play with a timeout in reserve. I like the run off to 1 second thing when you are on your last time out.
 
Link
 
Originally posted by GMathiasf
I would actually say that if there really was two timeouts left, that would be a bug, or at least a logic fail. Plenty of time to call a timeout and run another play with a timeout in reserve. I like the run off to 1 second thing when you are on your last time out.


This it is, 2 timeouts left, more than enough time to run another play and call a timeout.

Eivissa Maniacs 0:48
0:48 2nd & 1 OWN 28.5 small hands Culpepper pass to l_arry Fitzgerald, hurried by Ben "Franken" Stein, over the middle, thrown low intercepted by Chuck Pankow (36 yd return) [diving tackle: Speedy Delivery]
0:34 1st & 10 OPP 33.5 Dirk McDirt rush up the middle (10 yd gain) [tackle: Pat Emerson]
0:30 1st & 10 OPP 23.5 Offensive Timeout Called: Eivissa Maniacs Replay
0:30 1st & 10 OPP 23.5 Lunar Wind rush to the left (6.5 yd gain) [tackle: Da ISH III]
0:01 2nd & 3.5 OPP 17 Offensive Timeout Called: Eivissa Maniacs
0:01 2nd & 3.5 OPP 17 34 yd field goal attempted by DOUG BRIEN*, made [FG]
 
VolBrian
Rocky Top
offline
Link
 
The thing is that the new logic automatically runs the final 15 seconds of to one and then calls a TO to kick the FG. If the play starting at 0:30 took about 15 seconds, then this is working as intended per the new change/code.
 
GMathiasf
offline
Link
 
Originally posted by VolBrian
The thing is that the new logic automatically runs the final 15 seconds of to one and then calls a TO to kick the FG. If the play starting at 0:30 took about 15 seconds, then this is working as intended per the new change/code.


Did you watch the play and seriously conclude that the play took 15 seconds?
 
Link
 
Originally posted by GMathiasf
Did you watch the play and seriously conclude that the play took 15 seconds?


in 15 seconds you could have run that play twice
 
Catch22
offline
Link
 
This is working as coded/intended. Verifying not a bug - can notify OP and close.
 
VolBrian
Rocky Top
offline
Link
 
Originally posted by Catch22
This is working as coded/intended. Verifying not a bug - can notify OP and close.


Done
 


You are not logged in. Please log in if you want to post a reply.