User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Big bug checked by Offense AI tester - The Punt that wasn't called
Page:
 
Ken1
offline
Link
 
1:30 4th & 10.5 OPP 40 Felix Rice rush to the right (2 yd gain) (turnover on downs) [tackle: That'l LeaveA'mark]

That was in the first quarter, with a lead.

I figured I'd be punting there, and if somehow I did go on 4th and 10.5, it sure wouldn't be with an inside run.

Offense AI tester:

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

Possible Outputs
100% Punt (punt)

So, pretty big bug here.
 
Xiong Yoshi
offline
Link
 
Check energy settings.. seems every week I respond the same way. If your energy setting is too high - it won't kick.


Admittedly, 1st Quarter - doesn't really seem an energy issue unless the Punter is playing some other position .. I didn't look that deeply.
Last edited Oct 2, 2008 14:49:12
 
Firenze
offline
Link
 
99.99% chance it's human error.
 
Mike Rogers
Lead Tester
offline
Link
 
Ken want me to take a look and verify???
 
19MC67
offline
Link
 
http://goallineblitz.com/game/forum_thread.pl?thread_id=1157069
 
Ken1
offline
Link
 
Originally posted by Mike Rogers
Ken want me to take a look and verify???


If you can, then sure.
 
Ken1
offline
Link
 
Originally posted by Xiong Yoshi
Check energy settings.. seems every week I respond the same way. If your energy setting is too high - it won't kick.


Admittedly, 1st Quarter - doesn't really seem an energy issue unless the Punter is playing some other position .. I didn't look that deeply.


So basically, it decided that the punter was too tired?

It won't happen if I set punter settings to 10/0 or something?
 
Mike Rogers
Lead Tester
offline
Link
 
Sure I have time, gimme GM for a minute or two and I'll verify for those obvious problems etc.


 
Mike Rogers
Lead Tester
offline
Link
 
Originally posted by Ken1
Originally posted by Xiong Yoshi

Check energy settings.. seems every week I respond the same way. If your energy setting is too high - it won't kick.


Admittedly, 1st Quarter - doesn't really seem an energy issue unless the Punter is playing some other position .. I didn't look that deeply.


So basically, it decided that the punter was too tired?

It won't happen if I set punter settings to 10/0 or something?


I have very very rarely seen this in an established team, but it happens quite a bit on a newbie team where their punting often, and the punter has basic stamina (never added any SP).

 
Ken1
offline
Link
 
Originally posted by Mike Rogers
Sure I have time, gimme GM for a minute or two and I'll verify for those obvious problems etc.




GM with offense access offer sent, and you can ignore the first entry that I put in to try to get around the bug. Probably wouldn't have done anything anyway, but-- hell, delete it if you want and verify with that entry deleted.
 
Mike Rogers
Lead Tester
offline
Link
 
Hmmmm....

(Took a while because of site lag)

Strictly speaking it should have been fine.

Your inputs tell it very clearly to Punt in that exact situation.

And the AI tester brings it up.

100% Punt.

But you have several inputs higher in the order that have a 5 out of 6 similarity, would that be enough to make them work???

Especially as at least one is a Qtr 1 specific and 'Overides the above inputs'???
Maybe the Qtr 1 5 out of 6 is out-weighing the all Qtrs 6 out of 6???

Shouldnt do, and if it did it should be consistent through that game, (And any other with those settings)
Last edited Oct 2, 2008 15:39:41
 
Mike Rogers
Lead Tester
offline
Link
 
PS deleted you first entry to test the AI,
 
Mike Rogers
Lead Tester
offline
Link
 
Here is the 1st Qtr inputs result (Not going to say the name in public)

Matched Time Remaining? Yes
Matched Down? No
Matched Spot? Yes
Matched Yards to Go? Yes
Matched Score? Yes
Matched Special Sit? Yes

Would the fact that its a 1st Qtr specific play and it matches the time activate it, even though its not the right down?
I wouldnt think so.

Then moving down the AI checker for 'Unmatched we have these two...(Again name hidden to hide tactics)

Matched Time Remaining? Yes
Matched Down? Yes
Matched Spot? Yes
Matched Yards to Go? No
Matched Score? Yes
Matched Special Sit? Yes


Matched Time Remaining? Yes
Matched Down? Yes
Matched Spot? No
Matched Yards to Go? Yes
Matched Score? Yes
Matched Special Sit? Yes

As they all have outputs that match what happened it could be any of them firing.

But no obvious mistakes there to see, but it is a very complex Playbook.
Last edited Oct 2, 2008 15:49:37
 
Ken1
offline
Link
 
Originally posted by Mike Rogers
Hmmmm....

(Took a while because of site lag)

Strictly speaking it should have been fine.

Your inputs tell it very clearly to Punt in that exact situation.

And the AI tester brings it up.

100% Punt.

But you have several inputs higher in the order that have a 5 out of 6 similarity, would that be enough to make them work???

Especially as at least one is a Qtr 1 specific and 'Overides the above inputs'???
Maybe the Qtr 1 5 out of 6 is out-weighing the all Qtrs 6 out of 6???

Shouldnt do, and if it did it should be consistent through that game, (And any other with those settings)


Maybe what I need to do is put back in the one you took out to test it, which will basically say to always punt anytime I'm not behind, not in FG range, and it's 4th and 10+. When all of those things are true, my various "go for it" instructions should never activate (and of course 5 of 6 should never activate anything, anyway).

And even if a "go for it" one did, anything with 4th and more than 10 yards to go would be a pass.
 
Mike Rogers
Lead Tester
offline
Link
 
Yeah and if your going to have Qtr specific inputs them have that as a qtr specific input as well to safeguard it all.

Sounds silly and tedious, but there is no other reason it happened.

I am just wondering about the conflict between two inputs...

Especially as its really 6 out of 7 for both, as the Qtr specific has the right Qtr while the Generic one doesnt?


 
Page:
 


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