Originally posted by Mango Fandango
Look here's the issue, and perhaps I am clearly not making myself clear. And I'll-slooooowly-type-metaphor-free.
Human error is always likely to occur, especially by someone who is very new to the interface.
So when a play is called for Short distance, no matter whether it's a pass or run or whatever, the short distance play should override the pass/run inputs. Why? Because protecting Short is important. Distance first. Always.
If there are no suitable plays that match the tag for short and pass, for example, then the AI should dial up the most likely short playcall first, not what's the next best thing for Pass/Run. Why? Because protecting Short is important. Distance first. Always.
See where my logic is left behind? So the tactics screen is exactly how I describe it.
Unengaging. Unyielding. UnFun.
It needs overhauling for n00bs, newbs, rookies and casual gamers. It's currently a sh** fest.
I've said it in Discord, and I'll say it here, I can't wait for GLB3. And I hope that they sort out distance priorities first and foremost on defense. Why? Because protecting Short is important. Distance first. Always.
Oh-oh-oh and while I am making suggestions - as unlikely as I'll be heard - I suggest that the developers of GLB buy Stobie's software and pay him handsomely. Then integrate the software into GLB2.
GLB2 Scout is a pay-to-win premium DLC. I had to buy a season's worth to spot the errors in my playcalling. It doesn't stop the errors, cos I'm clearly cr** at understanding the intent behind Passing is more important than distance, but at least I could spot the error right there and then.
If you call for short, and have no short pass plays in the book, you want it to go for an inside run play, outside? run plays have no distance and you didn't have a short pass play selected.
You forgot to put a short pass play in 2WR, so when you asked it to pull a short pass play from 2 wide, what is your solution to what it should do when asked there?
The only other logical solution would be to ignore your % on plays you don't have a tag for, which would require re-writing the entire thing to accomplish as it's going to have to examine your playbook to determine which tags are and aren't in there each time before it starts anything else to determine which of your inputs to ignore. Then it would override things the other way though, as in if you had a play call for 80% pass long and 20% outside run and forget to tag a play pass long - well then you're looking at the outside run defense 100% of the time.
Either way doesn't solve the problem of you not having a play selected for 2 WR short pass, the game has to select another play for you from somewhere - you didn't give it one to run in that situation.