User Pass
Home Sign Up Contact Log In
Page:
 
Vilita
offline
Link
 
When I set the following:

Quarter: 4th
Time Left: 5 Seconds
Trailing by: 2
Down 4th
Yards to go: 10



When the ball is on the 37 yard line, it says we kick a field goal.

When the ball is on the 38 or 39 yard line, it says we punt

When the ball is on the 40, it says we go for it.

Why would we punt?
 
Forbin
offline
Link
 
What? You have it set in your AI to punt, obviously.

Unless I'm misunderstanding your post. It's not very clear what you're claiming the bug is.
 
Vilita
offline
Link
 
Originally posted by Forbin
What? You have it set in your AI to punt, obviously.

Unless I'm misunderstanding your post. It's not very clear what you're claiming the bug is.


No, its the default AI and its explained as clearly as possible...
 
Vilita
offline
Link
 
37 Yards:

Matching Input
Input Named: Late in Game, FG on the line

Possible Outputs
100% Field Goal (field_goal)


38,39 Yards

Matching Input
Input Named: 4th down, out of FG Range

Possible Outputs
100% Punt (punt)

Unmatched Inputs
Input Named: Late in Game, FG on the line
Matched Time Remaining? Yes
Matched Down? Yes
Matched Spot? Yes
Matched Yards to Go? Yes
Matched Score? Yes
Matched Special Sit? No
Input Named: Near FG Range
Matched Time Remaining? Yes
Matched Down? No
Matched Spot? Yes
Matched Yards to Go? Yes
Matched Score? Yes
Matched Special Sit? No
Input Named: Down Late, a Long Way to Go
Matched Time Remaining? Yes
Matched Down? Yes
Matched Spot? No
Matched Yards to Go? Yes
Matched Score? Yes
Matched Special Sit? Yes
Input Named: Down Late
Matched Time Remaining? Yes
Matched Down? Yes
Matched Spot? Yes
Matched Yards to Go? Yes
Matched Score? No
Matched Special Sit? Yes
Input Named: 4th down, losing big, short yardage
Matched Time Remaining? Yes
Matched Down? Yes
Matched Spot? No
Matched Yards to Go? No
Matched Score? No
Matched Special Sit? Yes
Input Named: Down two scores Late
Matched Time Remaining? Yes
Matched Down? No
Matched Spot? Yes
Matched Yards to Go? Yes
Matched Score? No
Matched Special Sit? Yes

40 Yards

Matching Input
Input Named: Down Late, a Long Way to Go

Possible Outputs
50% Long Bomb (pass)
50% Medium Air (pass)

Unmatched Inputs
Input Named: Late in Game, FG on the line
Matched Time Remaining? Yes
Matched Down? Yes
Matched Spot? Yes
Matched Yards to Go? Yes
Matched Score? Yes
Matched Special Sit? No
Input Named: Near FG Range
Matched Time Remaining? Yes
Matched Down? No
Matched Spot? Yes
Matched Yards to Go? Yes
Matched Score? Yes
Matched Special Sit? No
 
hemprobot
offline
Link
 
Man, seriously

99% it's because your "Down Late, a Long Way to Go" only triggers up to the opponents 40.

100% you have no clue what you are doing and shouldn't make unnecessarily long posts on the Bugs forum until you do.
 
Sabataged
offline
Link
 
Its out of your field goal kickers range.
 
Vilita
offline
Link
 
99% sure we shouldn't be punting down 2 points with 5 seconds to go in opposition territory, regardless of the reason, as there is nothing that says we should be punting anywhere...
 
Vilita
offline
Link
 
Originally posted by Sabataged
Its out of your field goal kickers range.


He's got a long of 62.
 
Galkuris
offline
Link
 
2 options

1. On your FG kick extend it to say 40-Goaline instead of "FG range" to kick it.
2. change the "go for it" part to extend to the 35 instead of stopping at the 40. Just make sure it is "below" your FG kick one.
 
aeakers
offline
Link
 
What do you have set as your kicker's range?

Obviously this is not a bug, you just need to refine your AI and figure out what went wrong.
 
Vilita
offline
Link
 
There is no range set, its all default
 
Vilita
offline
Link
 
So do what, edit "Late, a Long Way to Go" to remove the ball spot and make it say just outside field goal range?
 
Galkuris
offline
Link
 
Originally posted by Vilita
So do what, edit "Late, a Long Way to Go" to remove the ball spot and make it say just outside field goal range?


It is probably reading FG range as the 37. Your AI kicks in to go for it on the 40. So in the 4th quarter just have:

FG, in field goal range

followed by

go for it, 35-45 yard line.

Should cover the problem. If it decides FG range is the 37, and your on the 38, it will drop down to "go for it". If your on the 36, the second option is ignored and you kick it.
 
Vilita
offline
Link
 
But that doesn't really fix the problem it just patches it, if FG range became 33 for some reason we'd apparently be punting again.

But since there is no option specifically saying "Punt"

I really don't see how the game will punt with 5 seconds left down by 2, hence the bug report regardless
 
hemprobot
offline
Link
 
It's not a bug if the game is doing what you are telling it to do, just because you told it to do the wrong thing. Galkuris suggested something that looks like it will work, depending on the exact nature of your problem. Either way, you shouldn't be using the AI unless you are prepared to tell it exactly what to do in every given situation. For example, my 4th Q override to control the clock better in the last two minutes is 5 inputs, one of which deals with that exact problem.

The interface is a bit quick and dirty right now but it's the same for everyone. Why not just spend the time you've wasted here on making yours right?
 
Page:
 


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