User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > New timeout system isn't set up right - ISSUE RESOLVED - CLOSED
Page:
 
RUN HARD
offline
Link
 
Call me crazy but why not.....put calling Time-outs as part of the tactics? I posted this as a suggestion:

http://goallineblitz.com/game/forum_thread.pl?thread_id=4383185
 
drewsky
offline
Link
 
http://goallineblitz.com/game/replay.pl?game_id=1492450&pbp_id=1256162
There should have been a timeout called before this play, but there wasn't. My Test OAI shows that this play should be a FG.


Atlantic City Affliction 1:55
1:55 4th & 14.5 OWN 43.5 Punt by Red "Thunderfoot", 44 yd (out of bounds) Replay
1:50 1st & 10 OWN 12.5 Ted Nugent for President rush [missed tackle: Northside Taproom] up the middle (1 yd loss) [tackle: Cedric Jeffries] Replay
1:08 2nd & 11 OWN 11.5 Mayor McCheez sacked by F-5 (Loon) Tiger (5 yd loss) Replay
0:43 3rd & 16 OWN 6.5 Aeryn Sun sacked by Arm Tackle-King (5 yd loss) Replay
0:40 4th & 21 OWN 1.5 Defensive Timeout Called: Addict Nation Replay

Addict Nation 0:40
0:40 4th & 21 OWN 1.5 Punt by ~Captain Kangaroo~, 48 yd, fielded by Leaping Lanny Poffo (16.5 yd return) [diving tackle: Corey Lemonier.] Replay
0:32 1st & 10 OPP 33 Lee White pitch to Brutal Styles to the left (2 yd loss) [diving tackle: Harry Balsach] Replay
0:28 2nd & 12 OPP 35 Offensive Timeout Called: Addict Nation Replay
0:28 2nd & 12 OPP 35 Keith Miaz pass to Henry Miller over the middle [deflected by Santino Marela] (incomplete) Replay
0:21 3rd & 12 OPP 35 Keith Miaz pass to Lois Lane, hurried by E.B. Thomas, up the left side, caught (25 yd gain) [diving tackle: Mahoney Steele] Replay
0:05 1st & G OPP 9.5 Brutal Styles rush up the middle (3 yd gain) [Monster Hit diving tackle: Brian. Cushing] Replay

0:01 2nd & G OPP 6.5 Offensive Timeout Called: Addict Nation Replay
0:01 2nd & G OPP 6.5 23.5 yd field goal attempted by Wet Suit, made [FG] Replay
 
Link
 
Originally posted by drewsky
http://goallineblitz.com/game/replay.pl?game_id=1492450&pbp_id=1256162
There should have been a timeout called before this play, but there wasn't. My Test OAI shows that this play should be a FG.


Atlantic City Affliction 1:55
1:55 4th & 14.5 OWN 43.5 Punt by Red "Thunderfoot", 44 yd (out of bounds) Replay
1:50 1st & 10 OWN 12.5 Ted Nugent for President rush [missed tackle: Northside Taproom] up the middle (1 yd loss) [tackle: Cedric Jeffries] Replay
1:08 2nd & 11 OWN 11.5 Mayor McCheez sacked by F-5 (Loon) Tiger (5 yd loss) Replay
0:43 3rd & 16 OWN 6.5 Aeryn Sun sacked by Arm Tackle-King (5 yd loss) Replay
0:40 4th & 21 OWN 1.5 Defensive Timeout Called: Addict Nation Replay

Addict Nation 0:40
0:40 4th & 21 OWN 1.5 Punt by ~Captain Kangaroo~, 48 yd, fielded by Leaping Lanny Poffo (16.5 yd return) [diving tackle: Corey Lemonier.] Replay
0:32 1st & 10 OPP 33 Lee White pitch to Brutal Styles to the left (2 yd loss) [diving tackle: Harry Balsach] Replay
0:28 2nd & 12 OPP 35 Offensive Timeout Called: Addict Nation Replay
0:28 2nd & 12 OPP 35 Keith Miaz pass to Henry Miller over the middle [deflected by Santino Marela] (incomplete) Replay
0:21 3rd & 12 OPP 35 Keith Miaz pass to Lois Lane, hurried by E.B. Thomas, up the left side, caught (25 yd gain) [diving tackle: Mahoney Steele] Replay
0:05 1st & G OPP 9.5 Brutal Styles rush up the middle (3 yd gain) [Monster Hit diving tackle: Brian. Cushing] Replay

0:01 2nd & G OPP 6.5 Offensive Timeout Called: Addict Nation Replay
0:01 2nd & G OPP 6.5 23.5 yd field goal attempted by Wet Suit, made [FG] Replay


That looks right. Much better.
 
refguru
offline
Link
 
Is the logic fixed with the D calling timeout when it doesn't want one?
 
alindyl
offline
Link
 
Originally posted by stromstarhammer
That looks right. Much better.


Well i think he's pointing out that rather than calling a time out after the 3rd and 12 on the 35, it ran another play (a run play) with 5 seconds left on the clock on the 9.5. Then it called a TO with 1 second on the clock and kicked the FG.

Since it's impossible to make sure a play, especially a run play, takes less than 5 seconds it should have called it after the 3rd &12 pass and then kicked a FG. Though the not kicking a FG was likely an AI issue. Should probably check the AI to find out why it was trying to go for another play with 5 seconds left instead of kicking a FG.

The other 2 timeouts looked reasonable though.
Edited by alindyl on Nov 16, 2010 11:29:24
 
drewsky
offline
Link
 
Originally posted by alindyl
Well i think he's pointing out that rather than calling a time out after the 3rd and 12 on the 35, it ran another play (a run play) with 5 seconds left on the clock on the 9.5. Then it called a TO with 1 second on the clock and kicked the FG.

Since it's impossible to make sure a play, especially a run play, takes less than 5 seconds it should have called it after the 3rd &12 pass and then kicked a FG. Though the not kicking a FG was likely an AI issue. Should probably check the AI to find out why it was trying to go for another play with 5 seconds left instead of kicking a FG.

The other 2 timeouts looked reasonable though.


The OAI is programmed to kick a FG w/ any timeouts remaining with less than 10 seconds remaining on the clock. Instead it ran a running play with 5 seconds left. I had a former tester (Numone) double check this for me.
 
bacardi
offline
Link
 
Originally posted by Catch22
we have certain conditions when timeouts are called. I'll have Bort go over them and refine them

on the assumption that you wont be letting GMs decide when to use timeouts...

can you actually post these "conditions" ? right now, everyone basically has to develop an AI -- with nuances about when to kick a FG, when to try for a TD, when to try and waste time by running, when to throw to limit the clock dropping -- and *hope* that the timeout logic will help. wouldnt it be a lot easier to post what the conditions are?

1- its not like it has to be a state secret... we're not asking for the forced fumble formula. teams are not gonna have some competitive advantage if you know when your opponent will call a TO
2- as with anything thats open source, this makes finding bugs or some other illogical step easier to find and fix

are there any advantages (for the game, or any players) to actually HIDE timeout logic?
Edited by bacardi on Nov 16, 2010 20:56:40
 
d1sregard
offline
Link
 
Originally posted by Catch22
The tool doesn't read FG range settings.


Isn't that a slight oversight and easily correctable? Its extremely misleading.
 
Link
 
Originally posted by bacardi

on the assumption that you wont be letting GMs decide when to use timeouts...

can you actually post these "conditions" ? right now, everyone basically has to develop an AI -- with nuances about when to kick a FG, when to try for a TD, when to try and waste time by running, when to throw to limit the clock dropping -- and *hope* that the timeout logic will help. wouldnt it be a lot easier to post what the conditions are?

1- its not like it has to be a state secret... we're not asking for the forced fumble formula. teams are not gonna have some competitive advantage if you know when your opponent will call a TO
2- as with anything thats open source, this makes finding bugs or some other illogical step easier to find and fix

are there any advantages (for the game, or any players) to actually HIDE timeout logic?


 
Catch22
offline
Link
 
The thread Timeouts are not working properly and it is going to cost people games - ADMIN RESPONSE has been merged into this thread
 
jdros13
offline
Link
 
http://goallineblitz.com/game/game.pl?game_id=1444997&mode=pbp

go to the last drive. BDC takes over with 3:06 remaining. After the long completion the offense doesn't call a timeout, which is fine since we want to run the clock down anyway. Our input called "trailing by less than 2, in FG range" kicks in and we run the ball which is correct (shows up on the AI tester as well). We call timeout after the first play (our first timeout) which is kind of dumb like the TO's used to be but whatever. We don't call TO after the 2nd run though and then we run it again on 3rd down to get a fresh set of downs. We call a timeout at that point on their 3 yard line with 1st and goal to go (2nd Timeout)

We run the ball on 1st down. We don't call timeout. With :14 seconds left we run the ball again and don't call timeout and the game ends.

According to the AI set up this is correct. With one timeout remaining and 14 seconds on the clock I have it programmed to run the ball. Why wouldn't we call a timeout though? Had we been out of timeouts there our "Need FG less than 20 seconds" input would have kicked in (working properly according to the tester).

Don't care about it today obviously, but this needs to be fixed ASAP and put on the top of the list of things to do.
 
jdros13
offline
Link
 
and clearly I'll be adjusting the less than 20seconds thing to include as many timeouts as we have left going forward since this has changed, but changing the way TO's are called is really going to screw people up if the TO logic doesn't use some common sense. I would like to use as much of the clock as possible if I can and I thought that was the point of the changes. Not working as intended imo.
 
Bloodfart
offline
Link
 
so the 'need FG less than 20 seconds' input specified no time outs left? there's the problem.
 
jdros13
offline
Link
 
Originally posted by Bloodfart
so the 'need FG less than 20 seconds' input specified no time outs left? there's the problem.


no, the problem is that the TO logic makes no sense. We don't control the timeouts, but if you need 3 points and you have less than 20 seconds left and you have a timeout remaining the sim logic should use the timeout so the clock doesn't run out. In the old sim you used the timeouts in rapid succession at the first opportunity so if you wanted to run the clock down you needed to get a first down, using your 3 timeouts in that first set of downs. That has changed, which is good. But if you have timeouts remaining you shouldn't just run to the locker room with 10 seconds left down 2 - use the damn timeout.
 
jdros13
offline
Link
 
even if we weren't going to kick the FG there and for whatever reason we were going to go for it, ANY coach would use a timeout there since he still had one, rather than just let the clock run out.
 
Page:
 


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