Yeah I'm not saying I'm actually running the slider at zero, just that it maybe should be an option if you were completely indifferent to which RB got the rush.
I just don't want my FB to run the ball. He's to block or catch. I'll put in FB rushes if I want him to rush.
I've played with the slider for two seasons now and some games, it's just my RB's running while others (at the same setting) my FB gets an equal share of the rushes. That's in the low-mid-thirties.
I'm simply suggesting a way to say "However we do this, I'll choose the play if I want my FB to run the ball."
He's not in the RB part of the depth chart, he shouldn't run the ball, unless it's a designated FB rush (or WR Jet Sweep, if that was to ever be implemented)
...won't be worrying about any FB dive plays... ;) If a back cannot run, he is not a back.
Re: Rotational backfield
by
CrazySexyBeast
@
7/08/2019 4:58 pm
Smirt211 wrote:
CSB, it had nothing to do with you or your thoughts on over-rides which pretty much mirror mine.
It's because a user went toxic.
Aye. I feel we have been flailing around in the sea of "HEY LOOK!" (Jealuk?) Meh. :P
Making sure that the blocking FB is overriding at his own position tires him and makes him less available as a substitute RB. Sometimes I have this same situation with a TE that's fairly useless as a WR, but a great 6th blocker. I use overrides with those guys.
Just a facet that takes a bit of practice to apply. As with any thing else, it does become habit. Fortunately, over rides are not an every spin thing once established. You got this. Tarq is spot on, I do have a couple sets where I use a speedy TE with crazy run block as a FB, and in some spots, a crazy good catching FB in the TE position. Over rides allow us GMs to do what the real NFL does in a lot of ways. I like this aspect a ton.
