User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > RESOLVED BUGS > QB ran 3 times with rush setting at 0 - RESOLVED BUG #509
Page:
 
GMathiasf
offline
Link
 
Originally posted by VolBrian
This thread is about casual tactics. Not about package play calling percentages and auto adjust or AI percentages and auto adjust.


I'm well aware what the thread is about, but wouldn't the logic be the same. I don't play casual so I don't really know how it's broken up, so I used an example that I'm more comfortable with. Nonetheless, the logic is the same and if auto adjust is the problem, then it's likely because of what I was discussing.

To dumb it down for you into lolcasual speak.

If you set runs to...
80% HB, 20% FB, 0% QB.

With auto adjust on that causes a 10% penalty to a bad play...

One bad HB run should bring HB runs down to 72% with FB at 20% and QB at 0%. To fill the void, there are different options available. I would suggest math should multiply things up to get to 100% Bort likely uses a randomizer involving 92 possible outcomes now instead of 100. 72 of those outcomes should be HB runs, 20 FB runs, therefore a 78% chance of an HB run and a 22% FB run. QB should stay at 0%.

What people are hypothesizing is that the auto adjust logic basically adds indiscriminately to each %, which just doesn't make any sense. So to fill that 8% void, the auto adjust now goes with 3.3% QB, 75.3% HB and 23.3% FB or some other sort of math formula, but the logic is the same.

The point is still the same as what I wrote about. And that is that if the auto-adjust does work this way, that's a bug. 0% should always stay 0%. Auto-adjust should only affect plays or play types that have an assigned %.
Edited by kuaggie on Dec 24, 2010 01:53:43
 
Hukton Vioxx
offline
Link
 
Originally posted by The Avenger
No one especially doesn't care about regular, aren't there enough of the regular owned team whiner threads?


I'm not really seeing whining here...this is a bug whether Bort and Co. thinks its important enough to fix it or not, and it needed to be reported.

0% should mean 0% and if it means anything else there is a bug.
 
VolBrian
Rocky Top
offline
Link
 
Ok, there's enough here and I do suppose there's precedent with the package settings that I'll change this up for a QA look.

Likely a bug
 
Link
 
I could understand auto-adjust making it happen, but our 38 capped team ran a QB rush on the second play of the game after a successful HB rush. No way auto-adjust should have made a QB run happen with that scenerio, right?
http://goallineblitz.com/game/replay.pl?game_id=1482302&pbp_id=7219295
 
GMathiasf
offline
Link
 
Originally posted by stromstarhammer
I could understand auto-adjust making it happen, but our 38 capped team ran a QB rush on the second play of the game after a successful HB rush. No way auto-adjust should have made a QB run happen with that scenerio, right?
http://goallineblitz.com/game/replay.pl?game_id=1482302&pbp_id=7219295


that's a good play. Why are you complaining?

But yah that's pretty clear there that something is wrong. Even if auto-adjust was the culprit, it would be from plays going bad. In this case, the play before was a 4.5 yard run on 1st down, which is solid. I would assume it would be a net zero to the auto adjust.
 
VolBrian
Rocky Top
offline
Link
 
I'll go ahead and bump this up for QA to hash out.

Sent to QA
 
ezra_
You pick
offline
Link
 
we have many more examples of our QB doing this if you need them PM Ezbollah
 
STG
offline
Link
 

I don't recall the game (It was last season), but I distinctly remember watching the PBP and scratching my head.

The scenario was very similar to that of the OP

The team managed to call several QB Rollout plays, yet:

The team 100% had no more that the required 1 play per play type of (1 inside and 1 outside) QB Rushes in it's playbooks
The team was rolling with basic tactics with QB rush % set to "0"
The QB's tactics were set to "Almost Never" for both Running and Scramble
Auto Adjust was 100% turned off

BUG - FIRST VERIFICATION

Ok so I am calling this a bug, but I would prefer this sent to the testers...
Edited by STG on Dec 8, 2010 06:17:56
 
im4ut999
offline
Link
 
Sure would be nice to get this issue fixed.

Today nearly cost me a game with a 2nd down pass...100% run tactics, one pass on 2nd and 8:
http://goallineblitz.com/game/replay.pl?game_id=1486912&pbp_id=8657422

AA turned off, pass should not happen on 1st/2nd down.
 
Hukton Vioxx
offline
Link
 
It also seems to occur with FB rush plays, btw...100% HB runs yields a few carries for QBs and FBs just about every game.
 
ezra_
You pick
offline
Link
 
Thanks for moving this to QA. I was really unhappy with the Admin PMs telling me that my QB was looking for open receivers and not finding them. He never even used his vision lines, and the play call was QB rollout. Thanks!
 
im4ut999
offline
Link
 
Any update on this? Don't want this to fall off the list of fixes needed.....

Really sucks that can't use AA unless you have every skill position capable of running/catching. Can't use it for defense if offensive players are not dual threat.

 
kuaggie
offline
Link
 
K marking this as a bug....bort has always said 100% pass or 100% rush does not actually mean 100% in casual, but I'm P sure he intended your % of who gets the ball to be 100% true. Anyways, forwarding this on
 
im4ut999
offline
Link
 
Originally posted by kuaggie
K marking this as a bug....bort has always said 100% pass or 100% rush does not actually mean 100% in casual, but I'm P sure he intended your % of who gets the ball to be 100% true. Anyways, forwarding this on


I could live with that....pass/run % should take into consideration game situation, to some extent, but it's really bad when a run is called to a passing QB or a blocking FB....at low levels, not a big deal, but as level up, could be a big issue for fumbles or just a negative play....forces disabling AA completely unless you have a team setup to be all positions combo-types.....
 
im4ut999
offline
Link
 
So I guess another season of not being able to use auto adjust in casual.....really sucks that casual is left with these issues that you can't play unless you have everyone able to do everything.....

Is there any idea when this will get looked at?
 
Page:
 


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