User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Is this how auto adjust works now? - NOT A BUG - CLOSED
smittdog101
offline
Link
 
Should have stated it differently in the title, but the % are not even coming close to equating like they did last season.

http://goallineblitz.com/game/game.pl?game_id=1397344

I have 6 running plays in my run package. This is the break down and success of each.

SI Pitch Weak 15% Ran 1 time for 1.5 avg
HB Blast I Form 20% Ran 17 times for 3.76 avg.
SB HB pitch Weak 15% Ran 0 times
HB BLast Pro Set 15% Ran 2 times for 7.25 avg.
HB Sweep Pro Set 20% Ran 3 times for 7.5 avg.
Strong HB Sweep I form 15% Ran 1 time for 33.5 avg

I have auto adjust set to Quickly, like I always have, but it has never come out this lopsided like it has this season.

Any explanation for this.

1 Play is ran only 1 time and it averaged 33.5 yds on the carry?

3 Plays averaged over doubled the HB Blast I form play, but they were called a combined total of only 6 times compared to 17 HB blast that averaged way less?

1 play was called 0 times?

How do you explain this? ######## These were all first down plays and the only runs I had set were in this package for this down. ######## There were no other plays in the package other than the ones listed.

Anyone else noticing this wonkiness with play calling %'s. This is especially critical since the RPP is increased this season as well.
Edited by VolBrian on Oct 4, 2010 10:09:55 (Closed)
Edited by smittdog101 on Oct 2, 2010 15:03:08
Edited by smittdog101 on Oct 2, 2010 15:02:23
Edited by smittdog101 on Oct 2, 2010 15:02:07
Edited by smittdog101 on Oct 2, 2010 14:52:46
 
Forbin
offline
Link
 
3.76 average means that you had "success" on most of those runs. I don't remember exactly what constitutes a successful play on 1st down, but it's gotta be somewhere around 3-4 yards.

That's all auto adjust does. It doesn't measure HOW successful a play was, just whether or not it was a success, based on a predetermined and set amount depending on down.

Like, 3rd down, if you get a first down, it's a success. 1st & 2nd, I forget what Bort said, but he has commented on this in the past.
 
smittdog101
offline
Link
 
Originally posted by Forbin
3.76 average means that you had "success" on most of those runs. I don't remember exactly what constitutes a successful play on 1st down, but it's gotta be somewhere around 3-4 yards.

That's all auto adjust does. It doesn't measure HOW successful a play was, just whether or not it was a success, based on a predetermined and set amount depending on down.

Like, 3rd down, if you get a first down, it's a success. 1st & 2nd, I forget what Bort said, but he has commented on this in the past.


There were a lot of times where it only went for 2.5 yds ( HB Blast I form). I still think it was quite unbalanced considering the other plays were successful as well -1 play.
 
Forbin
offline
Link
 
Originally posted by smittdog101
There were a lot of times where it only went for 2.5 yds ( HB Blast I form). I still think it was quite unbalanced considering the other plays were successful as well -1 play.


Well, you have to consider the odds involved. Technically, anything's possible, but if you rule out extreme probabilities, it's still quite possible to see the results that you saw.

All that's required is for that 1 play to come up a couple times early, and bump the percentage just enough. The first 3 times that play was called it went for 7,7,4 yards. That bumped the percentage up just enough. Nobody knows exactly, but maybe it went from 20% to 40% or something, after those first 3 calls.
 
smittdog101
offline
Link
 
It's just not as consistent as it has been in the past. I have used it since it was implemented and it seems kinda "sticky" this season.
 
VolBrian
Rocky Top
offline
Link
 
I haven't seen any issues out of the auto-adjust at all this season in packages.

Forbin is correct in his assumptions and only a very large sample size showing repetitive skips of high percentage, successful plays would indicate anything that could possibly be called buggy.

Closing as not a bug
 


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