User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Offesive AI Bug! Cost us a game! "Near Field Goal Range" isn't correct.
saintedix
offline
Link
 
http://goallineblitz.com/game/game.pl?game_id=815917&mode=pbp

Late in the 4th quarter with less than a minute to go on a tie game, we had the ball with 0:38 and 0:10 left on the clock. When I go back and try this situation in my AI, it comes out as the "near field goal range" output matching, as well as the "field goal" output matching. However, it called the "near field goal range" output first (because it was above the other in the AI).

The special circumstance "near field goal range (10yds)" should not include when you are inside field goal range. The 13 yard line is well WITHIN field goal range and therefore it shouldn't match this input. This bug cost us the game, so hopefully it will get fixed before it costs others games.

EDIT: And our field goal range is set at 55 yards, so yes, a 31 yard field goal is within the range.
Edited by saintedix on Oct 18, 2009 18:07:24
 
kurieg
offline
Link
 
This has been reported before, and I believe the answer is working as intended.

Set the near FG range below the within FG range in your AI.
 
Captain Kaos
offline
Link
 
So, Near FG Range is above you're "Within FG Range" Input?
 
saintedix
offline
Link
 
Originally posted by cwisler
So, Near FG Range is above you're "Within FG Range" Input?


Yes. It shouldn't have been, I know, but I didn't know that "near FG range (10 yards)" on a 55 yard field goal meant anywhere between the goalline and 47. It should be between the 37 and 47...that's the bug.
 
Captain Kaos
offline
Link
 
Originally posted by saintedix
Originally posted by cwisler

So, Near FG Range is above you're "Within FG Range" Input?


Yes. It shouldn't have been, I know, but I didn't know that "near FG range (10 yards)" on a 55 yard field goal meant anywhere between the goalline and 47. It should be between the 37 and 47...that's the bug.


I thought the same thing as well, a few seasons ago. When I looked at it more, though, I figured it could mean just add another 5/10 yards onto what the FG distance is set for. I don't know what the intention is.

1) I know people have said there's a bug with those, I'm not sure of the exact bug with those special circumstances.

2) There are two possible solutions -- a) Move your Within FG Distance input above the special circumstance ones, or b) Compute where you would kick your max FG from, add the yards you want to it, and set that as the yard lines in the input.
 
saintedix
offline
Link
 
Yeah, I moved the FG input up, but it's kind of frustrating to tie a game we had won because of some wonky wording/coding.
 
Staz
offline
Link
 
If this is a simple wording issue, then it needs to be explained. If this is a coding error, then that needs to be fixed.

There should be a separation between "near FG range" and "in FG range".
 
deez11010
offline
Link
 
IMO, just take out all special circumstances out of your inputs. I had loads of problems until I finally took them out and havent had any since.
 
RMiller517
offline
Link
 
Thread locked by moderator.
 


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