User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Timeouts are still broken - NOT A BUG - CLOSED
Page:
 
bug03
offline
Link
 
Originally posted by TrevJo
( Other problems caused by the doubling of time cutoffs for timeout logic include the offense calling its first timeout too soon, as observed here at 1:16...
http://goallineblitz.com/game/game.pl?game_id=1508550&mode=pbp )


punting the ball when losing... awesome
 
bug03
offline
Link
 
Originally posted by TrevJo
bug, what does your AI Tester say for 28 seconds left at the opp 32.5 with the clock running and 1 timeout left while trailing by 1?


the run the ball to get into fg range package comes up
 
TrevJo
offline
Link
 
Originally posted by bug03
Originally posted by TrevJo

( Other problems caused by the doubling of time cutoffs for timeout logic include the offense calling its first timeout too soon, as observed here at 1:16...
http://goallineblitz.com/game/game.pl?game_id=1508550&mode=pbp )


punting the ball when losing... awesome


They would have had time to get the ball back in good field position if they had saved all their timeouts for defense
Edited by TrevJo on Mar 14, 2011 09:42:07
 
TrevJo
offline
Link
 
Originally posted by bug03
Originally posted by TrevJo

bug, what does your AI Tester say for 28 seconds left at the opp 32.5 with the clock running and 1 timeout left while trailing by 1?


the run the ball to get into fg range package comes up


So yeah if you set your AI to kick the FG in that situation instead it will run the clock down to 1 second. It's not ideal, but it's the best workaround availalable.
 
bug03
offline
Link
 
Originally posted by TrevJo
They would have had time to get the ball back and get into FG range if they had saved their timeout for defense


shouldn't have run the ball when losing tbh
 
TrevJo
offline
Link
 
Irony
 
Pwned
offline
Link
 
Originally posted by Androth
I am not talking about calling timeouts...that is my OAI from my team. I am talking about telling it when to kick.
If you tell it to wait to kick the ball until the clock is stopped, it holds the last timeout until 1 second. Assuming you are already in field goal range before your last time out is called. This may seem counter intuitive, but it works.


This is true..

The OP team has their settings to kick under 35 seconds, and their team kicked under 35 seconds.
 
bug03
offline
Link
 
Originally posted by Pwned IRL
This is true..

The OP team has their settings to kick under 35 seconds, and their team kicked under 35 seconds.


fixed and fixed
 
bug03
offline
Link
 
doesn't mean its right
 
Pwned
offline
Link
 
Originally posted by bug03
doesn't mean its right


I realize this, and with the remainder of the GLB population content and able to use the current system, I'm not sure that it deems this issue a bug being that in one game, at one time, your settings lost you a game. Which in reality, your defense played a bit soft in the end and allowed a team to score back on you in 28 seconds.

It becomes a mute point.

 
TrevJo
offline
Link
 
Originally posted by Pwned IRL
Originally posted by bug03

doesn't mean its right


I realize this, and with the remainder of the GLB population content and able to use the current system, I'm not sure that it deems this issue a bug being that in one game, at one time, your settings lost you a game. Which in reality, your defense played a bit soft in the end and allowed a team to score back on you in 28 seconds.

It becomes a mute point.



It's not a mute point, nor is it a moot point. The timeout system is better than it used to be, but it could still use improvement. It's easy to blame the defense, but the bottom line is that once you send your kicker onto the field with more than a few seconds left, anything can happen, from a missed FG to a big kick return to QB/WR VA stacks performing a miracle. Any GLB veteran has seen more than a few end-of-game field goal drives in less than 30 seconds. The job is of the OC is to make that FG as easy as possible and as late as possible. That's what makes the timeout logic important.

One could argue semantics about whether this a bug or not, but I think reasonable people would agree that the ideal system would not call a timeout in this case. It puts the AI in a tough spot...
...let me ask you this, Pwned:
-Do you know the exact amount of maximum time from which the AI will run the clock down to 1 second for a final field goal? I don't. I bet it's more than 28 seconds, but how much more?
-Do you know the exact amount of minimum time that you can run another play with no timeouts left and trust that you'll still have time for a spike and a field goal? I don't. I bet it's less than 28 seconds, but how much less?

In this particular case, they probably could have called for the kick before the timeout, or run another play after the timeout, and come out ok. But the timeout logic here is not intuitive. Most people know that the clock will run down to 1 second in some situations but might not know when it won't. And most people probably don't feel too comfortable running plays late with no timeouts left when they need a field goal. The settings that you saw lost him this game are really more understandable than the timeout logic that he didn't account for.

Originally posted by Pwned IRL
First off, thanks for the "moot" correction..

Second, I never blamed a dot, the luxury of this game is in that you can set up AI's to tell your team what to do.

The team that won that game kicked their FG and moved down the field with 28 seconds.

If his AI's were different, this game would have ended different, I saw the AI's, got a GM invite, and am making a verification based on what I saw..

Another luxury of this forum, is that not 1 single Bugs Mod can make a complete determination on a thread. Just because I see it a certain way may not match what two other mods will see this as.

3 Mods must look into each thread to make a processed verification and in time this thread will reach that level.

I am just trying to do my job, and battling and arguing with every passing speaker in each Bugs thread can be tedious at times, so please contribute to the thread with hard definitive evidence, and not a stance of opinion.


I'm not sure on exactly what point you want definitive evidence for. Definitive evidence that it would be better if the timeout logic were changed? Tell me what you think. If you were setting up the timeout logic, would you make it so that it called a timeout in that situation?
I'm not criticizing you for trying to do your job, I'm just offering up an opinion. I battled for a long time to get the timeout logic improved, and the result is something a lot better than it used to be, despite a lot of people in the past making arguments like the one you are now that there were workarounds even with the old awful logic. I still think it can be better. I understand how mods classify bugs and non-bugs and it doesn't surprise me to see this one resolved as not a bug, but nevertheless in my opinion it is a bug.
Edited by TrevJo on Mar 14, 2011 18:43:58
Edited by TrevJo on Mar 14, 2011 18:38:33
Edited by TrevJo on Mar 14, 2011 18:35:44
Edited by TrevJo on Mar 14, 2011 18:35:06
 
Pwned
offline
Link
 
Originally posted by TrevJo
It's not a mute point, nor is it a moot point. The timeout system is better than it used to be, but it could still use improvement.
One could argue semantics about whether it's a bug or not, but I think reasonable people would agree that the ideal system would not call a timeout in this case. It puts the AI in a tough spot...
...let me ask you this, Pwned:
-Do you know the exact amount of maximum time from which the AI will run the clock down to 1 second for a final field goal? I don't. I bet it's more than 28 seconds, but how much more?
-Do you know the exact amount of minimum time that you can run another play with no timeouts left and trust that you'll still have time for a spike and a field goal? I don't. I bet it's less than 28 seconds, but how much less?

Bad timeout logic is the cause of this delimma. Would be better to fix it than to brush it off as a corner case and blame the dots.


First off, thanks for the "moot" correction..

Second, I never blamed a dot, the luxury of this game is in that you can set up AI's to tell your team what to do.

The team that won that game kicked their FG and moved down the field with 28 seconds.

If his AI's were different, this game would have ended different, I saw the AI's, got a GM invite, and am making a verification based on what I saw..

Another luxury of this forum, is that not 1 single Bugs Mod can make a complete determination on a thread. Just because I see it a certain way may not match what two other mods will see this as.

3 Mods must look into each thread to make a processed verification and in time this thread will reach that level.

I am just trying to do my job, and battling and arguing with every passing speaker in each Bugs thread can be tedious at times, so please contribute to the thread with hard definitive evidence, and not a stance of opinion.
 
VolBrian
Rocky Top
offline
Link
 
This is not a bug. It is possible to adjust this with OAI as has been proven in the thread. Changes to the timeout logic would be suggestion at this point as everything is currently working as it was intentionally set up a few seasons back.

Not a bug - closed

EDIT: The only reason I am subverting the normal verification process here is that I have dealt with this exact issue numerous times over the last 2 seasons and have even brought this exact situation to Catch's attention and was shown exactly how it can be fixed in the OAI and why it is not a bug. In essence, this is a duplicate thread of those closed reports.
Edited by VolBrian on Mar 14, 2011 18:40:42
 
Page:
 


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