User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Offense AI not following on a 4th down?
Page:
 
MoneyMan
offline
Link
 
I have the following Offense AI setting:

Input:
Between the opponents 40 and opponents 35
4th down
Between 3 and 5 yards

Output:
100% Pass

Why did we run the ball here:
http://goallineblitz.com/game/replay.pl?game_id=95982&pbp_id=1016551
 
Thaak
offline
Link
 
I have a input line for going for it on 4th down. Between the opponents 35 and 45, if the score is within 7 points, between 0 and 2 yards to go, we'd go for it approximately 30% of the time.

What ended up happening was, we went for it almost everytime we were within FG range, which was NOT supposed to happen (within 35 yards.)

We'd have won our game today (assuming our Kicker made 4 more field goals) if the AI followed what we set up.

I can actually not see any reasoning why it would not follow what we set up. It totally went against our settings and went for it on 4th down inside field goal range.

And yes, I did have the field goal range thing set.
 
Bort
Admin
offline
Link
 
Originally posted by MoneyMan
I have the following Offense AI setting:

Input:
Between the opponents 40 and opponents 35
4th down
Between 3 and 5 yards

Output:
100% Pass

Why did we run the ball here:
http://goallineblitz.com/game/replay.pl?game_id=95982&pbp_id=1016551


Check your output - it's not set to pass. It's set to "use basic settings."
 
Grimmer
offline
Link
 
Similar situation for us...

http://goallineblitz.com/game/replay.pl?game_id=108255&pbp_id=849443

We went for it on 4th and 10 on their 40 yard line with 12 minutes left in the game while up by 38. We were outside FG range and within the ball spot specified to punt. I don't see any 4th quarter criteria that would be applied to this play. Why did we go for it instead of punting?
Last edited Aug 3, 2008 12:40:10
 
Thaak
offline
Link
 
Originally posted by Thaak
I have a input line for going for it on 4th down. Between the opponents 35 and 45, if the score is within 7 points, between 0 and 2 yards to go, we'd go for it approximately 30% of the time.

What ended up happening was, we went for it almost everytime we were within FG range, which was NOT supposed to happen (within 35 yards.)

We'd have won our game today (assuming our Kicker made 4 more field goals) if the AI followed what we set up.

I can actually not see any reasoning why it would not follow what we set up. It totally went against our settings and went for it on 4th down inside field goal range.

And yes, I did have the field goal range thing set.


I think I figured out part of it...

1) The "Field Goal Range" field is for the distance rather than the line of scrimmage? I was under the impression it was for the line of scrimmage. So this explains why we didn't kick 3 of the field goals we should have in the last game.

2) The yards part of it? We went for it on 4th down with 5.5 yards to go. I thought I'd set it for 2 yards or less. Which number should be first? The 2 or the 0? Or should I put .5? Is 0 and an illegal variable?

3) The other field goal that never was, was at the end of the 2nd quarter on 3rd down. So I just need to enter an input that kicks a field goal when a certain number of seconds are left in the quarter, no matter what down it is.
 
Thaak
offline
Link
 
Another reason I think the Offensive AI screwed up, is I have the score part of the (Go for it 4th down input) set to 0 to 7. Which means we should be winning to do this.

We were never winning in this game, and the AI still went for it.
 
Grimmer
offline
Link
 
1) The "Field Goal Range" is the actual distance (LoS + 17 yards).

2) From my understanding, the lowest number should always be first, so it would be 0 to 2 yards to go.

3) Yes, you would need to enter an input for that scenario and have it above any others it might conflict with, since the first input that meets the criteria on your list is what it will do.
 
Thaak
offline
Link
 
2) another poster said Bort has already confirmed that the order of the two variables doesn't matter? Is this true?

3) Apparently we did have this input in the "end of half" input in the 2nd quarter. We had it set to 10 seconds, and we threw a pass on 3rd down with 19 seconds left. I've modified it to 20 seconds.

Still doesn't account for why we went for it on 4th down with 5.5 yards to go. By all accounts, this should have been a punt considering my field goal range was messed up.
 
Bort
Admin
offline
Link
 
Things to watch out for, that I've noticed people do: 2 inputs that are mutually exclusive, where there is a gap in the middle.

For instance:

input 1: Outside FG range, between own goal and opponent 35: Punt
input 2: Inside FG range, between opponent 35 and opponent goal: Kick FG

If you're on the opponent 38 and your FG range is for the 40 yard line, neither of these will trigger.

Input 1 won't fire because you're not outside FG range.
Input 2 won't fire because you're not between the 35 and opponent goal

So it goes on to the next thing which is probably a pass or something and you go for it.
 
Thaak
offline
Link
 
can someone please verify with Bort the order in which the Yards required for an Input must be?

For example... which of the following is correct?

Between 0 and 2 yards

- or -

Between 2 and 0 yards

This is very important for setting up the AI I think, and may be why the AI went for it on 4th and 5.5.

Also apparently my OC had the "use only our settings" box checked, and we didn't have a specific setting set up for 4th and 5.5 outside of FG range, so we went for it. That seems kinda silly to me, as nothing in the "Go For It" input met the criteria and so it should have went down to the "Outside of FG Range, Punt" input and punted the ball.
 
Bort
Admin
offline
Link
 
it shouldn't matter the order - it sorts them before comparing, unless it's somehow buggy and I missed sorting a particular pair or something. I don't think so, though. I've tested all the things and they seem to work either way.
Last edited Aug 3, 2008 13:26:21
 
Thaak
offline
Link
 
Originally posted by Bort
Things to watch out for, that I've noticed people do: 2 inputs that are mutually exclusive, where there is a gap in the middle.

For instance:

input 1: Outside FG range, between own goal and opponent 35: Punt
input 2: Inside FG range, between opponent 35 and opponent goal: Kick FG

If you're on the opponent 38 and your FG range is for the 40 yard line, neither of these will trigger.

Input 1 won't fire because you're not outside FG range.
Input 2 won't fire because you're not between the 35 and opponent goal

So it goes on to the next thing which is probably a pass or something and you go for it.


I don't think we had this problem in our settings. Although I will go through the AI and double check it to make sure.

Can you clarify what the AI reads FG range as?

Is it the line of scrimmage, or the actual FG distance (LOS +17 yards)?

Reason I ask, is your comment above implies that FG range is LOS. Or am I interpreting it incorrectly?
 
Grimmer
offline
Link
 
Originally posted by Bort
Things to watch out for, that I've noticed people do: 2 inputs that are mutually exclusive, where there is a gap in the middle.

For instance:

input 1: Outside FG range, between own goal and opponent 35: Punt
input 2: Inside FG range, between opponent 35 and opponent goal: Kick FG

If you're on the opponent 38 and your FG range is for the 40 yard line, neither of these will trigger.

Input 1 won't fire because you're not outside FG range.
Input 2 won't fire because you're not between the 35 and opponent goal

So it goes on to the next thing which is probably a pass or something and you go for it.


Our FG range is listed as 52. The inputs above are exactly our inputs. We were on the 40 yard line and went for it. The 40 yard line falls into input 1, as does "outside FG range", right?
 
Bort
Admin
offline
Link
 
FG range should be LOS + 17, but let me check and make sure. I guess that's probably caused some confusion for people.

Edit: Ok I just looked and that's the case, except for one of the sim servers for some reason, where it was LOS. It started out at LOS during preseason and I fixed it, but must have missed that server. It's now fixed.
Last edited Aug 3, 2008 13:30:32
 
Thaak
offline
Link
 
Originally posted by Bort
FG range should be LOS + 17, but let me check and make sure. I guess that's probably caused some confusion for people.


Putting one of those little informational "?"'s above Field Goal range to explain that might help. Although now that I and my OC know it, it won't be necessary for us <G>
 
Page:
 


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