Warrior General Games

So, I checked every single package that is contained within my AI (No plays are called in any way on any input besides through packages) and in no instance is there anywhere where I call the play "Overload" out of the Single Back formation where the TE is set to pass block...All of them he is set to "Use Basic Settings"

Yet, 4 times in one game, the TE is held in to block on the play.

I knew there was a tactic around here somewhere for this, and I found it, on the AI page, and clearly it shows I had chosen "Do not allow the QB to auidble the TE" or w/e...

So my question is, is this like a known bug?

Has anyone had this issue before?


I have never once had an issue with this before in years of playing, but also, I have only really coordinated at the peewee level, and I can't honestly remember ever holding a TE in to block, or having seen it on my replays...

I'm so confused.

Edit: I also noticed that on some plays within my packages the "TE" assignment is grayed out and won't let me select it, while others are not, at first glance I thought it was just that a TE in the progressions locked out the ability to keep them in to block, but then I saw that it certainly doesn't appear that way...

So I'm really leaning towards a bug here.

Originally posted by Stoned Beaver
So, I checked every single package that is contained within my AI (No plays are called in any way on any input besides through packages) and in no instance is there anywhere where I call the play "Overload" out of the Single Back formation where the TE is set to pass block...All of them he is set to "Use Basic Settings"

Yet, 4 times in one game, the TE is held in to block on the play.

I knew there was a tactic around here somewhere for this, and I found it, on the AI page, and clearly it shows I had chosen "Do not allow the QB to auidble the TE" or w/e...

So my question is, is this like a known bug?

If it's set to "Use Basic Settings," wouldn't that mean it's using your team's basic settings?

For your team, click on Tactics, and then Basic Offense, and then scroll down to the Pass Play Calling section. You'll see settings there for "TE Pass Block Left Pct," TE Pass Block Right Pct," and "TE Run Route Percentage." I'm guessing you have something entered in one of the TE Pass Block settings.

One other way to be sure is this... in all of your packages, instead of setting the TE Assignment to "Use Basic Settings," set it to "Run Route" instead. That way there's no possible way the TE can do anything other than running a route.

When the assignment is greyed out, it means they are either on the custom route progression
or they are the primary receiver as the play is set up and which hasn't been customized; in either case
they can't have that box changed as they must run the route- at least that is how it usually works if not bugged

THere are a couple places you have to look. First of all the AI you are using itself. Then every play
and every play in every package. First thing i would do though is go to the Basic Settings page,
scroll all the way to the bottom, and check there. You wouldn't think so many of the "basic settings"
would still apply when you are using custom AI, but many seem to. Make sure those are set to never as well,
and then check just above there in Pass Settings to make sure those are set 100% TE run route, as Novus mentioned

I've now confirmed for sure its bugged, going to try to just remake the packages from scratch.

Originally posted by Stoned Beaver
I've now confirmed for sure its bugged, going to try to just remake the packages from scratch.

O.U.C.H.

Originally posted by Stoned Beaver
I've now confirmed for sure its bugged, going to try to just remake the packages from scratch.

Did you check your team's basic settings? (See post above.)

If I had a dime for every time a GLB player said something *must* be a bug and it was actually an incorrect entry in some obscure and overlooked setting somewhere in their team tactics or AI, I could buy GLB. Sometimes it is a bug, of course, but the vaaaaaaast majority of the time, it's not a bug.