User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > OAI Bug - 4th down not punting. - NOT A BUG - CLOSE
Peacesells
iBuying
offline
Link
 
http://goallineblitz.com/game/replay.pl?game_id=1736446&pbp_id=2134357

This has been happening all pre-season in closed scrims. Haven't posted since you cant verify closed games.

Today it happened in the live game. AI calls for a punt yet it pulls a random pass play with our running qb throwing the ball. In the closed scrims the same thing happened. Pass play with our running qb.

Here is the AI tester results:

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

Possible Outputs
100% Punt (punt)


I've tried with special circumstances and without. This game was without.

The one thing I've noticed is this only happens when around the opponents 30 yard line. Otherwise we punt just fine.
Edited by TruthHammer on Jul 9, 2011 22:43:14 (Closed - not a bug)
 
climberpete
offline
Link
 
Can't punt inside the 30. If your kicker is out of range you need a special input in your OAI to handle this case or it will default to your basic AI
 
TruthHammer
Lead Bugs Mod
offline
Link
 
From the Quirks sticky:
Originally posted by
114: Your team did not punt inside the opponents 30-yard-line even though your OAI specifically says to. This is because you are not allowed to punt within the 30-yard-line. Your team will go for it on 4th down if you have chosen to try and punt.

The text says you're at the 30, but that's a rounded number. You're actually just inside the 30, which is why you're not punting.

This is not a bug.
 
TruthHammer
Lead Bugs Mod
offline
Link
 
Thread moved by moderator.
 


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