Warrior General Games

Ok... having a strange AI issue. The last two games a play happened that should not have happened. 2 different AI's... situation very similar. My side of the field... 1st quarter... 4th and long. Tested on both AI's and the result is always PUNT. Tested right after the game and it still says PUNT. In the game... no punt.

http://glb.warriorgeneral.com/game/replay.pl?game_id=2941366&pbp_id=787233

There is no way in hell I would RUN on 4th and 10 (damn lucky we made it) on MY SIDE of the field. I've already PM'd support (DD knows) about the first one... now re-PM'd on the second one. But if anyone else has had this happen to them, I'd like to know what's happening. Is the test messed up? I'm using the replay parameters to run the test to be sure. Still says PUNT.
Any help or input appreciated. Thanks.

(P.S. Almost forgot to add this in as well. Both times (so far) that this 'bug' has happened it was the very 1st 4th and long situation. After that 'mistake' every subsequent similar

i've seen that a bunch of times over the years. some times it would forgo the punt, other times a FG. the ai tester would always show the appropriate play.

Every single time I thought I had an Ai bug, there ended up being a conflict somewhere above it in the Ai ladder.

The Ai tester isn't perfect, because it's so finicky. There's so many inputs, and variables... Like the output for the 21 yard line could be different than the one for the 20

Originally posted by TJ Spikes
Every single time I thought I had an Ai bug, there ended up being a conflict somewhere above it in the Ai ladder.

The Ai tester isn't perfect, because it's so finicky. There's so many inputs, and variables... Like the output for the 21 yard line could be different than the one for the 20

I'm actually using a very simplified AI (as opposed to my previous highly complicated ones where there were 12 inputs just for 3rd down.) What is funny is this. In both games, later in the same quarter when faced with the same situation, it punted as it was supposed to. If it had been a bad AI Input/Output then it should've kept having the same issue when confronted with the same situation and it did not. Even stranger is it has ONLY happened on the first event (first 4th down and long on my side of the field in the 1st quarter). Since the exact same Input/Output exists in the second and 3rd quarters as well, logically it should occur there as well... but it doesn't. Anyways... that's why the confusion, TJ. I mean, knowing my 1st 3 quarters are pretty much carbon copies of each other (at least when it comes to down and distance Inputs and Outputs... packages may vary greatly) then why the 'One Time Only'? (Oh, and BTW, in both incidents the distance to the 1st down and spot on the field were different as well... although still both 4th and too long and on my side of the field.)

Def not a bug

You've almost certainly tried all of these things, but in an attempt to be helpful:

-have you verified that the actual input you think should be selected is getting selected. You can do a "test and show unmatched" just to make sure your AI is flowing to the right place

-if you have an input named "punt", have you verified that within that input you are actually choosing to punt? If you have an input named punt but have not chosen an action, the tester will show "punt()" where if you have an input named punt and have chosen punt as the action then it will show punt(punt)

-have you made sure you are running the AI you expect to run? I know that sounds like a stupid mistake, but you can have a default AI set up to run on scrimmages that is different from the normal "default" AI. I assume you're using the calendar to get around this, but still

I know this isn't your first rodeo and you've likely been down all these paths, but since you're one of the few people who really tried to be helpful on the forums, I thought I should at least attempt to return the favor!

good luck

Originally posted by TJ Spikes
Every single time I thought I had an Ai bug, there ended up being a conflict somewhere above it in the Ai ladder.

The Ai tester isn't perfect, because it's so finicky. There's so many inputs, and variables... Like the output for the 21 yard line could be different than the one for the 20

Not a conflict but...

Originally posted by SeattleNiner
Def not a bug

Yeah... cannot express about how damn stupid I feel right about now. After going through every single AI... and every single INPUT... and every single OUTPUT... several times... I finally found the problem.
The INPUT was fine... everything was as it was supposed to be... and the OUTPUT was correctly labeled... but it seems I had a bad case of HUA and had forgotten to select 'Type Of Play' (in this case, Punt) in that ONE AI... in that ONE quarter... in that ONE situation... in that one INPUT... in that ONE OUTPUT.
I had even looked in those places and simply hadn't seen it missing (the play selection). Lordy... my brain hurts now. Of course this explains why, when tested (repeatedly), it said 'PUNT' where it should have... it just didn't do that because I hadn't TOLD it to. Support (meaning DD) has been informed so they can call off the bug hunt. It was just me that was buggy.

This... is why... so many OC's end up in institutions. O_o

Pretty sure every OC has done that at least once.

Can't say I've ever had a problem with my DAI's. From experience, all of these bugs have been user errors in the end

glad you found it!