User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > RESOLVED BUGS > Poor Casual Time Management - BUG FILED #265
PrizzlePulse
offline
Link
 
http://goallineblitz.com/game/game.pl?game_id=1399171&mode=pbp
1:26 4th & 7 OWN 47.5 Punt by One Legged A$$kicker, 30 yd, fielded by Jiraiya © (10 yd return) [tackle: Ricardo. Allen] Replay
1:16 1st & 10 OWN 32 Naruto © pass to Mei Terumī © up the left side [deflected by Karl Holzsohn] (incomplete) Replay
1:09 2nd & 10 OWN 32 Naruto © sacked by steve punam (7 yd loss) Replay
1:02 2nd & 10 OWN 32 Houston Boom calls timeout Replay
1:02 3rd & 17 OWN 25 Naruto © pass to Minato © up the left side, caught (14 yd gain) [tackle: Karl Holzsohn] Replay
0:52 3rd & 17 OWN 25 Houston Boom calls timeout Replay

Shanghai Packers 0:52
0:52 4th & 3 OWN 39 Punt by Kabuto ©, 28 yd, fielded by Kenny Y Hill (2.5 yd return) [tackle: Danzo ©] Replay
0:43 1st & 10 OWN 35.5 Paco Salad pitch to Wyld Thyng to the left (0.5 yd loss) [diving tackle: Human Path ©] Replay
0:37 1st & 10 OWN 35.5 Shanghai Packers calls timeout Replay
0:37 2nd & 10.5 OWN 35 Wyld Thyng rush [missed diving tackle: Deva Path ©] up the middle (3 yd gain) [tackle: Itachi ©] Replay
0:32 2nd & 10.5 OWN 35 Shanghai Packers calls timeout Replay
0:32 3rd & 8 OWN 37.5 Max "dragon" Wulfman pass to Milad Zell III, hurried by Pretra Path ©, up the left side [deflected by Tobirama ©] (incomplete) Replay

Houston Boom 0:26
0:26 4th & 8 OWN 37.5 Punt by One Legged A$$kicker, 22 yd, fielded by Jiraiya © (19.5 yd return) [diving tackle: One Legged A$$kicker] Replay
0:16 1st & 10 OPP 40 Naruto © bad pass to Zabuza © up the left side, caught (9.5 yd gain) [tackle: Ken Easily] Replay
0:08 1st & 10 OPP 40 Houston Boom calls timeout Replay
0:08 2nd & 0.5 OPP 30.5 Naruto © pitch to Minato © to the right (1.5 yd gain) [tackle: Ricardo. Allen] Replay
5th Quarter

Ok sorry for that wall of text, you can look at the play by play at end of 4th quarter if you do not wish to look at that, basically ill sumarize it. My team gets the ball with 1:16 left in casual, first play incompletion, no problem time stopped, 2nd play sack, timeout called which is fine which will leave me wtih 1:02 left with a 3rd and 17, on this 3rd down we get 14 yards, which is fine its a hard down to get the first, but after the play my team calls a timeout? What is the justification for calling a timeout in this situation to stop the clock with 52 seconds left, when im going to punt it away?(and yes we did punt it), but this is not all as after my opponent got the ball he punted away, which gave me the ball with 16 seconds left on my opponents 40(Had an excellent punt return, which was saved by a punter tackle), so on this drive im not expecting much, I have 1 timeout left, so im going to need to get some big yardage to put myself in a good situation to win this game, since my team is level 11s across the board, and a level 11 kickers chances with 40+ yarders isnt going to be very effective. So on my first play, I get a 9.5 yard gain which puts me at the 30.5 yard line with 8 seconds left. So, with this most likely being out of my field goal range im guessing(I have it set to 45 yards, although sometimes it exceeds range for kicks under certain time, correct? or is that only for advanced AI?). So I see my team ligning up for a play with 8 seconds left, on my opponents 30.5 yard line, tied 14-14, and I see im not in field goal formation, so i'm pretty much oh well at this point, hopefully we can get a big gain for a miracle TD, but my team runs on 2nd & 0.5 with 8 seconds left in the 4th quarter tied 14-14??? What is the justification with this, is this the possible bug of the situation over taking the time clock? IE it put a run in for me due to the 2nd & .5 situation? Shouldnt the time clock management be more advanced? I mean its the 4th quarter tied 14-14, im on the 30.5 with 8 seconds left and no timeouts, should it not be more advanced to not call a run? Btw incase your wondering i'm also on %100 pass, although I do know that it will occaisonaly do runs overriding the tactics in short, goalline and when im up type situations.

Yeah so I guess that was a wall of text too, this could of cost me the game, as I went into OT and my opponent missed a 33.5 yard fg, then I went on to score on my 2nd drive in OT. Sorry for the long post, any input/info would be appreciated!
Edited by Lensar on Oct 10, 2010 16:33:21
Edited by NiborRis on Oct 1, 2010 10:24:35 (bug, second verification)
Edited by Stray Doug on Oct 1, 2010 09:20:46 (BUG - FIRST VERIFICATION)
Edited by VolBrian on Sep 30, 2010 14:19:09 (Sent To QA)
Edited by VolBrian on Sep 25, 2010 10:51:41 (Reason in thread)
 
VolBrian
Rocky Top
offline
Link
 
Ok, a few things here:

Were you using auto-adjust at all?

Originally posted by PrizzlePulse
I have it set to 45 yards, although sometimes it exceeds range for kicks under certain time, correct? or is that only for advanced AI?


This is incorrect even in advanced AI. If you have the FG distance set specifically, the sim will not adjust that just based off of score or time remaining. In advanced AI's, you can tell the offense to kick it sooner or longer depending on the situtation you want, but the sim won't do it for you.

I believe you had a rushing play on 2nd and .5 because you were out of FG range and the score was tied. Had you been behind, I'm sure it would have been a pass play. That may be a suggestion that needs to be made as far as how aggressive the sim should be in tied-late situations in casual, but it's not a bug. If you had thrown an interception for a TD and lost on that play, we would probably be here discussing why it was so aggressive.

As far as timeout management goes, I'm not entirely sure there is an issue in this situation specifically especially considering you were left with one still when you got the ball back, but be aware that the TO strategies in casual is a filed bug here: http://goallineblitz.com/game/forum_thread.pl?thread_id=4219785

Maybe the issue will get an overhaul when that is looked at I don't know.

As for this situation in particular, I don't see anything that can really be called a bug. Yes, you were on 100% passing as you say, but we all know that 100% passing does not necessarily mean so in casual in GLB and is not a bug in itself. You probably could have won in regulation, but you pulled off a nice one in OT.

There's a wall of text right back at you.

Not likely a bug
 
PrizzlePulse
offline
Link
 
Originally posted by VolBrian
This is incorrect even in advanced AI. If you have the FG distance set specifically, the sim will not adjust that just based off of score or time remaining. In advanced AI's, you can tell the offense to kick it sooner or longer depending on the situtation you want, but the sim won't do it for you.

I believe you had a rushing play on 2nd and .5 because you were out of FG range and the score was tied. Had you been behind, I'm sure it would have been a pass play. That may be a suggestion that needs to be made as far as how aggressive the sim should be in tied-late situations in casual, but it's not a bug. If you had thrown an interception for a TD and lost on that play, we would probably be here discussing why it was so aggressive.

As far as timeout management goes, I'm not entirely sure there is an issue in this situation specifically especially considering you were left with one still when you got the ball back, but be aware that the TO strategies in casual is a filed bug here: http://goallineblitz.com/game/forum_thread.pl?thread_id=4219785

Maybe the issue will get an overhaul when that is looked at I don't know.

As for this situation in particular, I don't see anything that can really be called a bug. Yes, you were on 100% passing as you say, but we all know that 100% passing does not necessarily mean so in casual in GLB and is not a bug in itself. You probably could have won in regulation, but you pulled off a nice one in OT.

There's a wall of text right back at you.

Not likely a bug


So then why did it pass when I had 16 seconds left, should it not run it out then? I understand the aggressiveness of the sim thinking as one owner or coordinator would want his team to run out the clock and another be aggressive(btw there should be a setting in casual as to how aggressive in under a minute or something ). I just don't get why it would also call that time out before I punted, is there any reasoning into that at all? That was the main thing that was really strange to me, then if you look at my opponents drive, he ran on first down and second down yet called timeouts on both?(I believe both were up the gut too). Its just a really strange usage of time management to me, which seems to need to be improved for casual where they can't control settings such as wanting to run out the clock, or score in these type of situations. Edit(well not an actual edit, just saw a section did not see before): On the casual timeout bug, I suppose it could be related, although its not the same situation i'd say, as we all used our timeouts, or mainly all of them, my opponent might have had one left. If this is going to be filed as the similar bug of timeout management, is there any chance it could be added to that thread? As it kind of presents a different situation, i'm not too sure how you guys file bugs though.
 
VolBrian
Rocky Top
offline
Link
 
As it's currently set up, the sim will call TO's consecutively to stop the clock without thought to actually strategy of say, "let's stop it here, let it run next play, and save the last one for if we get the ball back in good position". In other words, the opponents TO's were called just because the clock was running and they were not ahead. Same for your own TO before your punt. The clock was running, you weren't winning, so the TO was called.

You passed on 1st Down because you were at 100% pass. The second down play is the aberration from your settings because it was tied and 2nd and .5 will nearly always be a run regardless of Casual settings.

As to whether or not to file this. I'm 99% certain that a general reworking of the TO's will be done when the existing bug is filed, just in case though, I'll ask this thread to be linked in.

As far as the aggressiveness/pass ratio/not following settings exactly, that's something that is suggested periodically and just hasn't been changed. Not sure if it will either tbh. I think there's some exploit concerns to allowing a Casual team to truly pass 100% of the time regardless (or run 100%)
 
PrizzlePulse
offline
Link
 
Originally posted by VolBrian
As it's currently set up, the sim will call TO's consecutively to stop the clock without thought to actually strategy of say, "let's stop it here, let it run next play, and save the last one for if we get the ball back in good position". In other words, the opponents TO's were called just because the clock was running and they were not ahead. Same for your own TO before your punt. The clock was running, you weren't winning, so the TO was called.

You passed on 1st Down because you were at 100% pass. The second down play is the aberration from your settings because it was tied and 2nd and .5 will nearly always be a run regardless of Casual settings.

As to whether or not to file this. I'm 99% certain that a general reworking of the TO's will be done when the existing bug is filed, just in case though, I'll ask this thread to be linked in.

As far as the aggressiveness/pass ratio/not following settings exactly, that's something that is suggested periodically and just hasn't been changed. Not sure if it will either tbh. I think there's some exploit concerns to allowing a Casual team to truly pass 100% of the time regardless (or run 100%)


Alright thanks , im fine with not being able to pass %100 because I understand the sim doing certain things in certain situations and keeping teams from abusing certain gameplans. Hopefully the sim will improve with its timeout thinking, it is surprising to me that it is not more advanced at this point, but hopefully it will be in the working.
 
doobas
™
offline
Link
 
Regardless of all the other stuff going on, I really don't think it should be calling a timeout for a 4th down punt. That's gotta be a bug, surely?

doobas™
 
VolBrian
Rocky Top
offline
Link
 
This was brought to my attention:


Originally posted by Changelog

Apr 5, 2010
- Update timeout logic to not call timeouts when in a likely punt scenario


Gonna go ahead and change to likely a bug for the TO in the punting situation.
 
VolBrian
Rocky Top
offline
Link
 
This has sat long enough, sending to QA for the punting issue above.
 
The Avenger
Hulk Smash
offline
Link
 
Originally posted by VolBrian
This has sat long enough, sending to QA for the punting issue above.


Isn't this working as intended for casual league play Vol or Catch????


Thats the exact logic behind a play called that looks logically buggy i posted yesterday, but was closed in 4 minutes flat due to 'too bad its Casual' attitude??

http://goallineblitz.com/game/forum_thread.pl?thread_id=4315684

No difference here WHAT-SO-EVER!
 
The Avenger
Hulk Smash
offline
Link
 
Originally posted by VolBrian
This is not a bug.

Casual tactics are designed this way and it's well known that it is intended.

100% anything can be changed depending on game situations.


Edited by The Avenger on Sep 30, 2010 15:29:11
 
VolBrian
Rocky Top
offline
Link
 
The only reason this is here is because of this:

Originally posted by PrizzlePulse
What is the justification for calling a timeout in this situation to stop the clock with 52 seconds left, when im going to punt it away?

....

tied 14-14


and

Originally posted by VolBrian
Originally posted by Changelog


Apr 5, 2010
- Update timeout logic to not call timeouts when in a likely punt scenario


Has nothing in common with your thread I'm sorry to say.

 
Stray Doug
offline
Link
 
IMO, timeout prior to punt could make sense in some cases if you were losing (espeically if you had multiple TOs left... idea being you gain field position, hold, and get the ball back... which is actually exactly what happened here). But I don't think it should call TO prior to punt with game tied.
 
NiborRis
offline
Link
 
Given that Bort's listed this should NOT be calling a timeout when in a punt scenario, I'm calling the TO a bug.

The rest of it is the exact reason why there's an advanced AI - there are chances of doing pass plays or run plays in just about every scenario, even if the chances in some scenarios are very low. What that means is that even in a case where the gameplan is to pass the ball 95% of the time, out of every 20 games that get to that scenario, 1 of them will run. If you want more detailed control over how the AI handles specific situations, you need to be in the normal leagues using the advanced AI.

Calling a TO before punting the ball away, especially while tied, bug, second verification.
 
Lensar
offline
Link
 
Bug filed #265
 
Catch22
offline
Link
 
New timeout logic should have corrected this issue.
 


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