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
 
Originally posted by SteelersInsider

It is hitting the bomb it out play.

But what is your bomb it out play?? That is your answer. That is where you made a mistake.

what play is your bomb it out play?

receiver: ??
long/med/short: ??

run/pass/kick: (we know this one is set to pass)



Use Basic Gameplan for receivers (mostly WR, medium TE, small HB, adds up to 100%).
Long pass.
Pass play.

Please enlighten all of us moronic noobs about how a long pass play set to the WR, TE, or HB translates correctly (ie, not a bug or glitch) into a 60+ yard FG.
 
Link
 
Originally posted by Zurai
Originally posted by SteelersInsider


It is hitting the bomb it out play.

But what is your bomb it out play?? That is your answer. That is where you made a mistake.

what play is your bomb it out play?

receiver: ??
long/med/short: ??

run/pass/kick: (we know this one is set to pass)



Use Basic Gameplan for receivers (mostly WR, medium TE, small HB, adds up to 100%).
Long pass.
Pass play.

Please enlighten all of us moronic noobs about how a long pass play set to the WR, TE, or HB translates correctly (ie, not a bug or glitch) into a 60+ yard FG.



Take notes:

This is EXACTLY why so many people are having problems:

So your long pass option will sometimes call long WR pass (ok), long HB pass (ok), then it will sometimes try to call long TE pass (WHICH DOESN'T EXIST!!).

When it goes to that option, it will go to the next input that matches or if no other inputs match, then it goes to basic CPU intelligence which means that it will kick a FG if it is within the kicker's range.

THIS IS EXACTLY A PERFECT EXAMPLE OF WHY SOMETIMES A PLAY WORKS AND SOMETIMES IT DOESN'T - USER ERROR.

 
tmarze
offline
Link
 
Don't take what any of these guy's are saying as a personal attack,let these guys aide you in finding what is going wrong.
Last edited Oct 15, 2008 12:26:16
 
Mightyhalo
offline
Link
 
Originally posted by SteelersInsider
Originally posted by Zurai

Originally posted by SteelersInsider



It is hitting the bomb it out play.

But what is your bomb it out play?? That is your answer. That is where you made a mistake.

what play is your bomb it out play?

receiver: ??
long/med/short: ??

run/pass/kick: (we know this one is set to pass)



Use Basic Gameplan for receivers (mostly WR, medium TE, small HB, adds up to 100%).
Long pass.
Pass play.

Please enlighten all of us moronic noobs about how a long pass play set to the WR, TE, or HB translates correctly (ie, not a bug or glitch) into a 60+ yard FG.



Take notes:

This is EXACTLY why so many people are having problems:

So your long pass option will sometimes call long WR pass (ok), long HB pass (ok), then it will sometimes try to call long TE pass (WHICH DOESN'T EXIST!!).

When it goes to that option, it will go to the next input that matches or if no other inputs match, then it goes to basic CPU intelligence which means that it will kick a FG if it is within the kicker's range.

THIS IS EXACTLY A PERFECT EXAMPLE OF WHY SOMETIMES A PLAY WORKS AND SOMETIMES IT DOESN'T - USER ERROR.



User error looks to be the case and since he acted like such an ass I am happy to help.
 
Nixx
offline
Link
 
Originally posted by SteelersInsider
So your long pass option will sometimes call long WR pass (ok), long HB pass (ok), then it will sometimes try to call long TE pass (WHICH DOESN'T EXIST!!).


I think this is a problem with how Bort programmed the AI.

If someone inputs 'pass', 'long', and 'follow basic AI' for the target, then the AI should be smart enough to only choose long passes, and then choose a primary target. It shouldn't pick the primary target first, then realize there is no play for that target and default back to the basic AI.

This is a bug.
 
RAPB
offline
Link
 
So here's the list of "forbidden" settings:

outside run - pitch/sweep + FB
outside run - pitch/sweep + QB
outside run - pitch/sweep + "use basic settings" // as long as FB or QB got any carries
outside run - off-tackle + FB
outside run - off-tackle + QB
outside run - off-tackle + "use basic settings" // as long as FB or QB got any carries
goal line + QB
goal line + "use basic settings" // as long as QB got any carries
medium pass + HB
medium pass + FB
medium pass + "use basic settings" // as long as HB or FB got any passes
pass + long + TE
pass + long + FB
pass + long + "use basic settings" // as long as TE or FB got any passes
pass + "use basic settings" + HB // as long as you call any medium passes
pass + "use basic settings" + FB // as long as you call any medium or long passes
pass + "use basic settings" + TE // as long as you call any long passes
Last edited Oct 15, 2008 14:56:19
 
Link
 
Originally posted by Nixx
Originally posted by SteelersInsider

So your long pass option will sometimes call long WR pass (ok), long HB pass (ok), then it will sometimes try to call long TE pass (WHICH DOESN'T EXIST!!).


I think this is a problem with how Bort programmed the AI.

If someone inputs 'pass', 'long', and 'follow basic AI' for the target, then the AI should be smart enough to only choose long passes, and then choose a primary target. It shouldn't pick the primary target first, then realize there is no play for that target and default back to the basic AI.

This is a bug.



someone should be smart enough to realize that they called a play that doesn't exist and then figure out what happened.

It is like a for x = 1 to 10 loop that goes to 11. Is the 11 input a "bug"? No. It just doesn't fit the criteria of the loop and moves on to the next line of the program.

Not a bug at all.

Just curious..... What did you all think happened when you called a play that didn't exist (like pass to the TE deep)?
 
Zurai
offline
Link
 
Originally posted by Mightyhalo

User error looks to be the case and since he acted like such an ass I am happy to help.


Care to explain how "100% punt" is "user error" then? I'm willing to accept Steelerinsider's explanation for the 2nd quarter FG - but that's just a separate bug, not a 'working as intended', IMO. That explanation does not apply to either of the 4th quarter FGs that the AI tester says should have been punts.
Last edited Oct 15, 2008 17:13:38
 
Zurai
offline
Link
 
Originally posted by SteelersInsider
It is like a for x = 1 to 10 loop that goes to 11. Is the 11 input a "bug"? No. It just doesn't fit the criteria of the loop and moves on to the next line of the program.

Not a bug at all.


Actually, if a for loop that's only intended to go to 10 gets an x=11, that IS a bug. You obviously don't program for a living. The counter on For loops are rarely if ever open to user input, so if there's errant data, it's the programmer's fault.

Originally posted by
Just curious..... What did you all think happened when you called a play that didn't exist (like pass to the TE deep)?


Just curious ... why do you think the ability to call a play that doesn't exist isn't a bug?
 
wombat killer
offline
Link
 
Originally posted by SteelersInsider
Originally posted by Zurai

Originally posted by SteelersInsider



It is hitting the bomb it out play.

But what is your bomb it out play?? That is your answer. That is where you made a mistake.

what play is your bomb it out play?

receiver: ??
long/med/short: ??

run/pass/kick: (we know this one is set to pass)



Use Basic Gameplan for receivers (mostly WR, medium TE, small HB, adds up to 100%).
Long pass.
Pass play.

Please enlighten all of us moronic noobs about how a long pass play set to the WR, TE, or HB translates correctly (ie, not a bug or glitch) into a 60+ yard FG.



Take notes:

This is EXACTLY why so many people are having problems:

So your long pass option will sometimes call long WR pass (ok), long HB pass (ok), then it will sometimes try to call long TE pass (WHICH DOESN'T EXIST!!).

When it goes to that option, it will go to the next input that matches or if no other inputs match, then it goes to basic CPU intelligence which means that it will kick a FG if it is within the kicker's range.

THIS IS EXACTLY A PERFECT EXAMPLE OF WHY SOMETIMES A PLAY WORKS AND SOMETIMES IT DOESN'T - USER ERROR.



You think it is a user error that it gives you the option of calling a long TE pass and one doesn't actually exist? You are clearly just arguing to listen to yourself.
 
Link
 
Originally posted by wombat killer
Originally posted by SteelersInsider

Originally posted by Zurai


Originally posted by SteelersInsider




It is hitting the bomb it out play.

But what is your bomb it out play?? That is your answer. That is where you made a mistake.

what play is your bomb it out play?

receiver: ??
long/med/short: ??

run/pass/kick: (we know this one is set to pass)



Use Basic Gameplan for receivers (mostly WR, medium TE, small HB, adds up to 100%).
Long pass.
Pass play.

Please enlighten all of us moronic noobs about how a long pass play set to the WR, TE, or HB translates correctly (ie, not a bug or glitch) into a 60+ yard FG.



Take notes:

This is EXACTLY why so many people are having problems:

So your long pass option will sometimes call long WR pass (ok), long HB pass (ok), then it will sometimes try to call long TE pass (WHICH DOESN'T EXIST!!).

When it goes to that option, it will go to the next input that matches or if no other inputs match, then it goes to basic CPU intelligence which means that it will kick a FG if it is within the kicker's range.

THIS IS EXACTLY A PERFECT EXAMPLE OF WHY SOMETIMES A PLAY WORKS AND SOMETIMES IT DOESN'T - USER ERROR.



You think it is a user error that it gives you the option of calling a long TE pass and one doesn't actually exist? You are clearly just arguing to listen to yourself.



You guys obviously don't remember a few seasons ago where the only choices we really had were the % run and % pass.

Now Bort gives us hundreds of different options and all people do is complain that some of them don't work or that some of the controls aren't 100% user friendly.

The game is 4,000 times better, but he is making all the changes himself. He is only 1 man. He has a wife and a kid. He has to eat and sleep also. I imagine he might also have some friends. He can't fix everything immediately. He is well aware that the game isn't close to being perfect but he is working hard to fix things.

Either Bort can write a detailed guide of 4,000 things that aren't working right now and what will happen if you call each of them, and what plays vision works poorly in.......or by all the time and effort put into doing that could be put into the game and by then, he could have half of them solved.

A much easier way is for all of us just to experiment, note the things that aren't working to support in a PM or a thread here......and Bort will put it on his list.

It doesn't do the game any good to keep whining that something is broken. You know it, I know it, Bort knows it. What do you want to happen??? It is on his list.

You know the rule, if it is too broken for you to play, then stop playing. The game is clearly labeled Beta. Accept the things that aren't finished or at least don't demand that they are fixed immediately. Bort knows all.
 
Link
 
Originally posted by tmarze
Don't take what any of these guy's are saying as a personal attack,let these guys aide you in finding what is going wrong.


 
Zurai
offline
Link
 
Originally posted by Zurai
Care to explain how "100% punt" is "user error" then? I'm willing to accept Steelerinsider's explanation for the 2nd quarter FG - but that's just a separate bug, not a 'working as intended', IMO. That explanation does not apply to either of the 4th quarter FGs that the AI tester says should have been punts.


 
wombat killer
offline
Link
 
Originally posted by SteelersInsider


Either Bort can write a detailed guide of 4,000 things that aren't working right now


That is called a bug. This is the bug forum. What is your problem?
 
Zurai
offline
Link
 
Originally posted by SteelersInsider
A much easier way is for all of us just to experiment, note the things that aren't working to support in a PM or a thread here......and Bort will put it on his list.


What the HELL do you think this thread is if not "noting things that don't work properly and posting it in a thread here"?

Jesus, you need mental help.

Oh, and:

Originally posted by Zurai
Care to explain how "100% punt" is "user error" then? I'm willing to accept Steelerinsider's explanation for the 2nd quarter FG - but that's just a separate bug, not a 'working as intended', IMO. That explanation does not apply to either of the 4th quarter FGs that the AI tester says should have been punts.
Last edited Oct 16, 2008 16:59:52
 
Page:
 


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