User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > BUG - Offensive AI not being followed
Page:
 
Zurai
offline
Link
 
At three different occasions in my latest game ( http://goallineblitz.com/game/game.pl?game_id=146783&mode=pbp ), my team opted to kick 60+ yard field goals. However, at NONE of those points are we supposed to kick field goals. Here are the three FGs, with the output that the Offensive AI Tester is telling me SHOULD have been followed:

0:14 left in 2nd qtr, losing by 14, ball on Opp 46.5, 1st and 10:
Possible Outputs
95% Bomb it out (pass)
5% Medium Air (pass)

7:07 left in 4th qtr, losing by 11, ball on Opp 46.5, 4th and 1.5:
Possible Outputs
100% Punt (punt)

2:57 left in 4th qtr, losing by 11, ball on Opp 45.5, 4th and 5:
Possible Outputs
100% Punt (punt)


On none of those occasions was a FG even in the output list of the appropriate input.
 
InRomoWeTrust
Lead Mod
offline
Link
 
Do you have any FG inputs, and if so, where are they located on your lists? Remember that quarter specific inputs are overrides towards the general ones.
 
Zurai
offline
Link
 
Originally posted by Mat McBriar
Do you have any FG inputs, and if so, where are they located on your lists? Remember that quarter specific inputs are overrides towards the general ones.


Like I said, I already ran these through the AI tester. The AI tester said the FG inputs did not match.
 
RAPB
offline
Link
 
Try to test again today as your kicker got full energy back. FG range changes as the kicker gets tired.
 
Link
 
send me the appropriate GM title, a PM, and a link to the play that was a mistake and I'll find your problem in 5 minutes
 
robelder
offline
Link
 
Do you have it set to follow my settings exactly? Do you have auto adjust off? If not, then the GLB gods still have some control over your outputs.
 
Zurai
offline
Link
 
Originally posted by RAPB
Try to test again today as your kicker got full energy back. FG range changes as the kicker gets tired.


Same results.
 
Link
 
Originally posted by SteelersInsider
send me the appropriate GM title, a PM, and a link to the play that was a mistake and I'll find your problem in 5 minutes


 
Zurai
offline
Link
 
I already know my problem: The AI isn't doing what it says it itself says it's supposed to do. Auto-adjust was off, max FG range is set to 58 yards, and the game still chose to kick 62+ yard FGs even though the AI tester says FGs aren't even an option in any of the circumstances.
 
Link
 
I think reporting bugs should be a betting game.

If you think you have an error, you have to put up 300 FP (at least). If you are correct, you get 600 FP's back for finding the error.

If you are wrong, then you lose those 300 FP for wasting everyone's time.

I think if that was the process people wouldn't be so quick to run here and waste Bort's time every time the AI didn't do what they wanted it to.

All teams should also be required to have 2 other members to look at the code before they are allowed to post here.

Just my thoughts. 99% of things posted here are user error. 100% of the people thought they were real bugs though.

 
Link
 
Originally posted by Zurai
I already know my problem: The AI isn't doing what it says it itself says it's supposed to do. Auto-adjust was off, max FG range is set to 58 yards, and the game still chose to kick 62+ yard FGs even though the AI tester says FGs aren't even an option in any of the circumstances.



1.) We don't know if you inputted into AI tester correctly

2.) We don't know what the dropdown settings are under those outputs. For all we know, they could be blank. If even one of them is blank or wrong, then it goes back to standard CPU AI - which would be: "if it is within the K's range then kick it"
 
NotRippedYet
offline
Link
 
Originally posted by Zurai
I already know my problem: The AI isn't doing what it says it itself says it's supposed to do. Auto-adjust was off, max FG range is set to 58 yards, and the game still chose to kick 62+ yard FGs even though the AI tester says FGs aren't even an option in any of the circumstances.


What are all of your settings under your input for FG?
Time:
Ball Spot:
Down:
Circumstance:
 
Zurai
offline
Link
 
Originally posted by SteelersInsider
1.) We don't know if you inputted into AI tester correctly
Are you seriously trying to imply that I can't do simple data entry correctly, any of the three times I've run these through the AI tester? Get a grip.
Originally posted by
2.) We don't know what the dropdown settings are under those outputs. For all we know, they could be blank. If even one of them is blank or wrong, then it goes back to standard CPU AI - which would be: "if it is within the K's range then kick it"
Yes, you do know what the dropdown settings are under those outputs, unless you're also accusing me of lieing in the original post. The AI tester's output includes both the name of the output selected AND what type of play it is. In the cases of my plays, the dropdown selected were pass/pass, punt, and punt, respectively.
Originally posted by NotRippedYet
What are all of your settings under your input for FG?
Time:
Ball Spot:
Down:
Circumstance:
I have 5 different FG triggers (2 general, 3 quarter-specific).
General 1
Time: N/A
Ball Spot: Between Opp 5 and Opp goal
Down: 4th
Circumstance: Within FG Range, winning by between 4 and 9

General 2
Time: N/A
Ball Spot: Between Opp 40 and Opp goal
Down: 4th
Circumstance: Within FG Range

2nd Quarter
Time: 30 seconds remaining
Ball Spot: Anywhere
Down: Any
Circumstance: Within FG Range

4th Quarter
Time: 40 seconds remaining
Ball Spot: Anywhere
Down: Any
Circumstance: Within FG Range, losing by 0-3

Overtime
(Identical to 2nd Quarter, but no time limit)


Before you go, "AHA! The 2nd quarter input matches the actual play in game!", 63.5 yards is out of my K's range according to the AI tester and according to every previous attempt he's ever had. The longest the game's ever had him attempt was a 59 yarder back before FG distances were nerfed (although he did complete a 58 yarder this season). Also, that doesn't address the two 4th quarter punts at all, because neither of them were within the time limit either.
 
Link
 
let's not focus on the FG triggers. That obviously isn't causing this. It is not hitting ANY of your triggers for anything and triggering the CPU to decide on it's own. It will then kick on 4th down if it is within range. That is what is happening.

Can you list *all* the details of the inputs that you think should have been triggering on those instances?

 
Link
 
Bomb it out for instance-

what is the exact play call there under bomb it out?
 
Page:
 


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