all this will eventually be moot when they shift to optional real-time play calling, which is what i believe to be the goal
Forum > Goal Line Blitz > Field Goal Logic at end of halves needs an improvement
jdbolick
offline
offline
Originally posted by Pena_FIN
Yeah, I see your point and do agree. But that would probably be a bitch to program, since the current timeout logic is p simple compared to that.
It's not a real time-game, so the code would already know how long it would have taken before the next play starts. It shouldn't be that difficult to put in a condition to not use a timeout if it would be less than ten seconds.
Yeah, I see your point and do agree. But that would probably be a bitch to program, since the current timeout logic is p simple compared to that.
It's not a real time-game, so the code would already know how long it would have taken before the next play starts. It shouldn't be that difficult to put in a condition to not use a timeout if it would be less than ten seconds.
Pena_FIN
offline
offline
Originally posted by jdbolick
Originally posted by Pena_FIN
Yeah, I see your point and do agree. But that would probably be a bitch to program, since the current timeout logic is p simple compared to that.
It's not a real time-game, so the code would already know how long it would have taken before the next play starts. It shouldn't be that difficult to put in a condition to not use a timeout if it would be less than ten seconds.
Look at the current timeout logic, it basically works like the playcalling AI. Quarter, time remaining, ball spot, score difference, # of timeouts remaining (own and opp), etc. For all we know, it's just a bunch of invisible and uneditable inputs in all our AI's.
Originally posted by Pena_FIN
Yeah, I see your point and do agree. But that would probably be a bitch to program, since the current timeout logic is p simple compared to that.
It's not a real time-game, so the code would already know how long it would have taken before the next play starts. It shouldn't be that difficult to put in a condition to not use a timeout if it would be less than ten seconds.
Look at the current timeout logic, it basically works like the playcalling AI. Quarter, time remaining, ball spot, score difference, # of timeouts remaining (own and opp), etc. For all we know, it's just a bunch of invisible and uneditable inputs in all our AI's.
jdbolick
offline
offline
I just had a weird situation in a private scrim where my offense is driving down the field. It calls a timeout at 0:45 (thirty seconds after the previous play), and then the second timeout at 0:41 after a completed short pass. But then it never calls the third timeout as the next play goes from 0:41 to 0:27 or after the fourth play when it goes from 0:27 to 0:04. Since my OAI is set to kick the field goal only after all timeouts are exhausted, I didn't end up attempting one. I can't figure out why that third timeout never got called.
Larry Roadgrader
offline
offline
Originally posted by fogie55
all this will eventually be moot when they shift to optional real-time play calling, which is what i believe to be the goal
NGTH.
all this will eventually be moot when they shift to optional real-time play calling, which is what i believe to be the goal
NGTH.
Originally posted by Pena_FIN
Yeah, I see your point and do agree. But that would probably be a bitch to program, since the current timeout logic is p simple compared to that.
Actually the code as written has handled the complexity (If play begin < :45 call the timeout and put :45 on the clock). The logic should be based on the time remaining at the end of the play, not the time remaining when the next play would begin. Oddly enough, that isn't how the logic works at the end of a half. If a play ends with less than 20 or so seconds the timeout is never called. It wouldn't be hard to add logic that works exactly the same as the :45 logic or, better yet, call the timeout immediately after the play ends.
Yeah, I see your point and do agree. But that would probably be a bitch to program, since the current timeout logic is p simple compared to that.
Actually the code as written has handled the complexity (If play begin < :45 call the timeout and put :45 on the clock). The logic should be based on the time remaining at the end of the play, not the time remaining when the next play would begin. Oddly enough, that isn't how the logic works at the end of a half. If a play ends with less than 20 or so seconds the timeout is never called. It wouldn't be hard to add logic that works exactly the same as the :45 logic or, better yet, call the timeout immediately after the play ends.
Originally posted by jdbolick
I just had a weird situation in a private scrim where my offense is driving down the field. It calls a timeout at 0:45 (thirty seconds after the previous play), and then the second timeout at 0:41 after a completed short pass. But then it never calls the third timeout as the next play goes from 0:41 to 0:27 or after the fourth play when it goes from 0:27 to 0:04. Since my OAI is set to kick the field goal only after all timeouts are exhausted, I didn't end up attempting one. I can't figure out why that third timeout never got called.
What was the field position on 3rd down? I'm assuming you were in FG range?
I just had a weird situation in a private scrim where my offense is driving down the field. It calls a timeout at 0:45 (thirty seconds after the previous play), and then the second timeout at 0:41 after a completed short pass. But then it never calls the third timeout as the next play goes from 0:41 to 0:27 or after the fourth play when it goes from 0:27 to 0:04. Since my OAI is set to kick the field goal only after all timeouts are exhausted, I didn't end up attempting one. I can't figure out why that third timeout never got called.
What was the field position on 3rd down? I'm assuming you were in FG range?
jdbolick
offline
offline
Originally posted by AirMcMVP
What was the field position on 3rd down? I'm assuming you were in FG range?
0:41 was third down but resulted in a first down at the 30.5, then the next play resulted in another first down at the 15.
What was the field position on 3rd down? I'm assuming you were in FG range?
0:41 was third down but resulted in a first down at the 30.5, then the next play resulted in another first down at the 15.
You are not logged in. Please log in if you want to post a reply.
