Warrior General Games

Here's the story, in a specific situation my AI keeps calling a FB sweep every so often. I have tested the AI to this exact situation, even down to seconds left in the quarter, and the only thing that should be called is a package that contains 4 different pass plays. What could be happening here? the package and the input are both using quickly adjust but this shouldn't matter as last sim I rolled a FB sweep on the 2nd drive in the 1st quarter.

I probably wouldn't notice if it wasn't happening on a 3rd and long scenario

There's an Ai bug somewhere.

I'm famous for forgetting to set matching distance outputs, after I edit the Ai a few times. Like I'll have an old 0-2 yards, and then add a new 3-7 or something--so that if it's actually 2.5 yards in game, the Ai shits itself, and finds something useless to do.

The other big thing is some other input is set wrong so that's it's intruding when it isn't supposed to be. Like maybe a Down input is set to Between 1 & 4, instead of 3 & 3.

Another fun one, is when you change packages, and the name in the Ai doesn't update. So you look for the bug 15 times, and everything looks fine until you actually click on the package.

good luck.

I'm guilty of the down input between 1 and 4 input screw-up all the time.

I tested the AI to the exact scenario of the incorrect play and only have the 1 intended package fire off in the test. The package is set as intended

Originally posted by nytsud2
I tested the AI to the exact scenario of the incorrect play and only have the 1 intended package fire off in the test. The package is set as intended

the only way someone could help you is if they can look at it. if you make me a GM with OC privileges and tell me via PM all the details, I could take a look at it if you want. no guarantees, but usually a fresh set of eyes helps.

It'll also help to have replays, and multiple examples in different games. The more data you have, the easier it is to find the common denominator.

As someone who had some of "the" most complicated AI's I can only give you what I know.

EVERYTHING matters when trying to diagnose a faulty situation. Quarter, Time on clock, down and distance, Score... everything. It's so easy to miss one tiny thing and not get an accurate report.

When building an AI always remember it reads from the top down. So let's say you want a FG setup for the 2nd quarter where you would like a try from extra long if it's the last play in the quarter (before the half). Here's how you would need to set it up;

#1 It would need to be the 1st INPUT of the 2nd Quarter so it gets read first. Realize you have normal FG settings in that same quarter and they would need to come AFTER this.

#2 Set time to whatever remaining seconds you think is correct (I used 15 seconds).

#3 Down set to any and distance set to what you think is the absolute max for your kicker. Remember... if time is left after kick and you tried a 75 yard FG you're giving your opponent a free FG try closer than what yours is... if you miss.


I could go on but you get the main idea. NOW... we've established the parameters... lets screw it up. So you note in the next game that you had a chance to get in a late 50 yard FG try in the 2nd quarter, before the half expired, but it didn't fire.
It could be easy as you didn't put the INPUT above the other INPUTS... especially the other FG inputs. In that case, it would not fire. Or it could be you set the time settings too tight and instead of kicking a FG the game tried to run one more play... only to run outta time. Or you might have set down to 4th only by accident... or maybe distance was forgotten. There are SO many ways to screw it up and I've done them all I'm pretty sure. A few of my "OAI isn't working" posts are scattered around here... likely some time back.
And Sluggy is right... get a second set of eyes on your AI... it >really< does help.

GREAT to see Theo have the energy for marathom posts again!!

OP, if you give me a link to the ghost play and access to your AI, I'm sure I can find the issue.

As lolz as it sounds, the AI error checker misses errors.