User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Timeout Logic Change - NOT A BUG - CLOSED
.spider.
Lead Mod
offline
Link
 
Starting here - http://goallineblitz.com/game/replay.pl?game_id=2092420&pbp_id=5664898

At the 34 VDA is in FG Range, why would they be taking TO's when a FG wins the game? They would just run plays and when the clock gets to :01 they'd take a TO and kick a FG for the win, at least that's what I would think "normal" logic would be. Obv I'm upset w/ the loss, but still I dont think any OC would agree w/ this logic, unless down by 4 or more.
Edited by Catch22 on Jul 30, 2012 23:42:42
 
Redass Ranch
offline
Link
 
agree... but not sure it's a bug... more of a suggestion to give more control of timeouts to team...

maybe give check boxes like 2 point conversion of when to call, and not call timeouts...


similar event, but opposite rational: http://goallineblitz.com/game/replay.pl?game_id=2099434&pbp_id=4954494

we turn the ball over, they are in FG range... why would we NOT call timeouts to get the ball back with time on the clock
last play of the game is this: http://goallineblitz.com/game/replay.pl?game_id=2099434&pbp_id=4954713 - any time left, we attempt a FG
 
TaySC
offline
Link
 
Spider, while I see what you are saying, the sim only responds to what inputs are in it, so unless you have a specific input that the sim ignored, I don't think this is a bug.

 
TrevJo
offline
Link
 
Tay, there's no input to control timeouts.

I agree with spider that this is a bug. I have pleaded many times for offensive timeouts to not be used so early, preferrably not until under 45 seconds imo.

Here's my original list of timeout scenarios that the current logic is based on: http://goallineblitz.com/game/forum_thread.pl?thread_id=3801123&page=1#33688850
Unfortunately they doubled the times on a lot of these and now instead of 45 seconds you'll see offensive timeouts called with 90 seconds left.

In the situation spider linked, and many others, the offense is calling a timeout when it makes absolutely no sense to.
 
Mike Rogers
Lead Tester
offline
Link
 
Time Out Logic improvements were on the most recent list for an offseason fix I saw.
 
GMathiasf
offline
Link
 
There's so much dumb about end game timeout logic. It's all just senseless. In our game today, we called a timeout down 2 at the 16 yard line with a minute 17 to play. We pick up the first down and yup, call another time out. Then we run a play at the 1:12 mark, don't call a timeout, but rush onto the field for another play 18 seconds later. Why the fuck would we be in hurry up? And honestly, why isn't the DEFENSE calling time outs in this situation. we run another play, and then the kicker rushes onto the field to kick a FG in a 20 second span. what reason a team with 1 timeout left would ever leave time on the clock OR a defense wouldn't stop the clock is completely inexplicable. We were fortunate to cause a fumble on the ensuing possession or we very possibly would have lost to a team with 3 timeouts and 34 seconds left on the clock. It's almost season 30, can we get this shit right?
 
Catch22
offline
Link
 
This isn't a bug. We're working on a couple revisions hopefully this off season that will improve the time out logic (among the revisions suggested is to run the clock down without calling a timeout when a team is within 3 or leading and in FG range).
Edited by Catch22 on Jul 30, 2012 23:41:38
Edited by Catch22 on Jul 30, 2012 23:39:39
 
Catch22
offline
Link
 
Thread moved by moderator.
 


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