User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Bug when YTG have a 0.5 in the equation
Denman
offline
Link
 
The current Offensive AI will not allow me to call a play using 0.5 as part of the yardage information. Instead, it rounds the number up. For example, if I put in a play for 3rd down and between 0.5 and 3 yards to go, and I update the AI (or save it as a separate file), the game rounds up the 0.5 to a 1.

This would not be a big deal, except when my team is at 3rd down with 0.5 yards to go. Then the AI puts in a random play (typically the rarely effective pitch / sweep).

If the game is going to use .5 in its algorithms, then it should allow .5 yards to go to be included in Offensive and Defensive AIs.

This should be fixed before season 6.

Thanks for your assistance.
 
cosmoxl
offline
Link
 
why not just use 0 instead of 0.5?
 
Denman
offline
Link
 
I simplified the problem for discussion purposes.

My principle concern was when I set defenses or offenses at specific yards to go, for example 2nd and short = between 1 and 3 to go for first down, 2nd and medium = between 4 and 6 to go for first down.

You cannot plan for 1 to 3.5 to go, although the game recognizes the scenario of 3.5 YTG. So what do you do? put 2nd and short = between 0 and 4 to go for first down (to account for 3.5 YTG), and 2nd and medium = between 4 and 6 to go for first down? That only shifts the problem to what happens when the scenario is 4 YTG. Then which play is called?

The solution appears simple. It should be made for continuity's sake.
 
the_legenol
offline
Link
 
Originally posted by Denman
That only shifts the problem to what happens when the scenario is 4 YTG. Then which play is called?


whichever output is highest on the AI. I agree it's a little counter-intuitive, but i don't think it's worth bort's time to change it right now.
 
Denman
offline
Link
 
Here are examples.

The Offensive AI does not have any pitch sweep plays in it for this particular game.

Pitch / sweep #1 = http://goallineblitz.com/game/replay.pl?game_id=206302&pbp_id=10777207

Pitch / sweep #2 = http://goallineblitz.com/game/replay.pl?game_id=206302&pbp_id=10777827

The only commonality between the plays is that YTG was X.5. In fact, given the number of scenarios that are X.5 in YTG, the game should either not recognize the X.5 YTG or allow teams to account for X.5 YTG.
 
Cruzi
offline
Link
 
Originally posted by Denman

My principle concern was when I set defenses or offenses at specific yards to go, for example 2nd and short = between 1 and 3 to go for first down, 2nd and medium = between 4 and 6 to go for first down.


Change 2nd & Medium to 3-6 ytg. Problem solved.
 
Gyuri1
offline
Link
 
I think the biggest problem with this bug occurs in the "and Goal" situation, as you can't differentiate in the oAI between "and Goal" and 0 yards to go. So, if you want to make sure you go for it on, say, 4th and inches from the opponent's 4 yard you have to set up your AI so that it will also have you go for it on 4th and Goal from the opponent's 4 yard line.
 
GoldenBoy7
offline
Link
 
My God you people will do anything and everything to give Bort a pass! If the FU**#NG sim takes in account .5 when running the sim, then why can't the OCs and DCs be able to use .5 when gameplanning? Why do you have to go out of your way to do fixes and work arounds to get something to work like it should? It might not be a "bug", but it's an issue and it certainly affects the game!

/rant
 
Link
 
Originally posted by Gyuri1
I think the biggest problem with this bug occurs in the "and Goal" situation, as you can't differentiate in the oAI between "and Goal" and 0 yards to go. So, if you want to make sure you go for it on, say, 4th and inches from the opponent's 4 yard you have to set up your AI so that it will also have you go for it on 4th and Goal from the opponent's 4 yard line.


Bort said he thought that bug was fixed. If someone has an example of it recently, please start another thread and link to it in this one.

I've been scared to try and have just been kicking the FG's instead unless it is a end of game situation.

I'm very interested to see if anyone has a recent example (last 3 games?)
 
Gyuri1
offline
Link
 
I didn't know that Bort though it was fixed.

I have also been game planning in fear of it and just kick FGs instead.
 
RMiller517
offline
Link
 
Thread locked by moderator.
 


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