League Forums

Main - League Help

Re: WR's vs DB's

By Beercloud
1/11/2018 3:21 am
GrandadB wrote:
GG Skins, its a good example for any MFN owner/managers that are not aware about what happens when you have more than a 10 mismatch in speed btw the WRs and CBs, in addition to the opposing team having a good OL, and good QB, as Washington does. That mismatch results in long passes for TDs. In the Skins/Pack game it resulted in 6 TDs. 3 TDs by WR1 McClain (91 sp), 2 of them were fly or go patterns (straight) both over 80 yds. vs CB1 Kay (76) (15 speed differential). 2 were to WR2 Glick (95 sp) on fly patterns vs CB Rose (85 sp) (10 sp diff).

It is very important to be aware of the speed matchups between WRs & CBs. In the MFN 1 forum, posted by JDB.....

jdavidbakr wrote:
The biggest impact for M2M skill is an opposition to a WR's route running skill. When a WR makes a cut, the sharpness of the cut in determined by his route running skill, and the ability of the DB to cut with him is determined by the M2M skill. On fly routes the M2M skill and route running skill are not really used, in those cases it does boil down to speed.

If you dont have any DBs with at least 85+ speed, you are in trouble when you face a team with 2 or more WRs with 90+ speed (like Washington) and they throw a lot of fly routes on long pass plays, in addition to having effective pass blocking. You will get burned. The only other strategy is to either blitz heavy and try to get more pressure on the QB or use more deep zone coverages, 3 & 4 man. I have not tried that approach with the zones, and heavy blitzing using 2LBs and/or DBs has been significantly reduced in the latest game version, anyone had success with using 3 & 4 Deep Zone coverages? If there is no way to compensate for the speed differentials, then it becomes another game exploit. cheers, gdb


Until 0.4.3 is released (I hope soon), it's impossible to think about Speed and go routes without thinking about your DB's B&R rating when you're playing M2M. I have notes for how to game plan for M2M, but haven't taken the time to write them out. [Here's the beta league thread about me complaining about this: https://mfn1.myfootballnow.com/forums/6/1444?page=1#8768]

setherick wrote:
I noticed that CBs were getting burned badly on plays when they were supposed to be in tight man coverage. As someone who runs a lot of Cover 5 on early downs and while run blitzing, this bothered me a lot. This was happening more frequently in the beta leagues because the QB would throw the ball as soon as the WR broke free of the CBs cover. On closer inspection, this mostly happened when the CB came up to jam the WR at the line.

This observation led me to tracking down this post by JDB:

jdavidbakr wrote:
Rotor wrote:
Does this rating matter, do bump & run influence the outcome of pass plays (how, slowing the route progression?) I never saw a corner "press his receiver on the line" and they invariably start several yards from him but maybe I don't interpret correctly what I see. Thanks in advance for your input!


There is a decision that your CBs make to decide whether to play off the WR or play close and bump and run. Usually this decreases with faster WR's so the CB doesn't get beat; you'll know if the CB is playing bump and run because he'll be right on the LOS when the play starts.

B&R will slow the pattern down (depending on the WR's B&R avoidance) because the WR's velocity is interrupted. This potentially could give the DL a bit of extra time before the WR completes his route. So it doesn't have a huge impact, but may tilt the scales slightly on some plays.


So with all of that, I have added B&R back to my CB and WR weights. In fact, I've started looking at B&R as being more important than M2M because the effects of bad B&R are disastrous in the code being tested. I still consider these weights in a testing phase, but they seem to be working in that I give up fewer long passes because the CB missed the jam at the line.
Last edited at 1/11/2018 3:23 am

Re: WR's vs DB's

By Mcarovil
1/11/2018 10:03 pm
These are all very good points to consider when gameplanning and also drafting to a degree but the one constant in MFN is Speed speed speed. Still so very important. Thanks for the post.

Re: WR's vs DB's

By DocK
1/12/2018 10:32 am
I have a question about WR/DB interaction, but figured it would be best to consolidate it here.

Last game I got whooped by the Jags (GG) and gave up some really long TDs to the same WR several times.

Knowing my DBs are slow and **** and that the Jags have fast and good WRs, my gameplan was to go m2m with help from my good safeties over the top. To be fair, most (all?) of the examples I will show did not have safety help. I must've given too much weight to blitzing plays and the sim engine picked the "no safety help" plays out of my gameplan hat at inopportune times. Whoops.

Nevertheless, my question is about WR/CB dynamics in the engine. My atrocious m2m corner (https://paydirt.myfootballnow.com/player/464) who clearly should not have been on the field (or on the team, haha) got burned on these three plays by this guy (https://paydirt.myfootballnow.com/player/1168), and in all of them it looked like my CB just stopped (both players always at bottom of the screen):

https://paydirt.myfootballnow.com/watch/846#152049
https://paydirt.myfootballnow.com/watch/846#152065
https://paydirt.myfootballnow.com/watch/846#152077

And in this one, he just stops and leaves the WR wide open without any contact:
https://paydirt.myfootballnow.com/watch/846#152048

Is this the game's way of saying "he got burned by a better player"? How is my CB stopping explained? I expect a horrific m2m corner to get crushed by a good WR 1-on-1, but am trying to understand if this is how the game represents that.
Last edited at 1/12/2018 10:33 am

Re: WR's vs DB's

By Pernbronze
1/12/2018 10:15 pm
DocK wrote:
I have a question about WR/DB interaction, but figured it would be best to consolidate it here.

Last game I got whooped by the Jags (GG) and gave up some really long TDs to the same WR several times.

Knowing my DBs are slow and **** and that the Jags have fast and good WRs, my gameplan was to go m2m with help from my good safeties over the top. To be fair, most (all?) of the examples I will show did not have safety help. I must've given too much weight to blitzing plays and the sim engine picked the "no safety help" plays out of my gameplan hat at inopportune times. Whoops.

Nevertheless, my question is about WR/CB dynamics in the engine. My atrocious m2m corner (https://paydirt.myfootballnow.com/player/464) who clearly should not have been on the field (or on the team, haha) got burned on these three plays by this guy (https://paydirt.myfootballnow.com/player/1168), and in all of them it looked like my CB just stopped (both players always at bottom of the screen):

https://paydirt.myfootballnow.com/watch/846#152049
https://paydirt.myfootballnow.com/watch/846#152065
https://paydirt.myfootballnow.com/watch/846#152077

And in this one, he just stops and leaves the WR wide open without any contact:
https://paydirt.myfootballnow.com/watch/846#152048

Is this the game's way of saying "he got burned by a better player"? How is my CB stopping explained? I expect a horrific m2m corner to get crushed by a good WR 1-on-1, but am trying to understand if this is how the game represents that.


jbd answered this before in something I read. If a player in coverage is bad at his type of coverage he can "stumble" which is the stop.

Re: WR's vs DB's

By DocK
1/13/2018 10:41 am
Pernbronze wrote:
DocK wrote:
I have a question about WR/DB interaction, but figured it would be best to consolidate it here.

Last game I got whooped by the Jags (GG) and gave up some really long TDs to the same WR several times.

Knowing my DBs are slow and **** and that the Jags have fast and good WRs, my gameplan was to go m2m with help from my good safeties over the top. To be fair, most (all?) of the examples I will show did not have safety help. I must've given too much weight to blitzing plays and the sim engine picked the "no safety help" plays out of my gameplan hat at inopportune times. Whoops.

Nevertheless, my question is about WR/CB dynamics in the engine. My atrocious m2m corner (https://paydirt.myfootballnow.com/player/464) who clearly should not have been on the field (or on the team, haha) got burned on these three plays by this guy (https://paydirt.myfootballnow.com/player/1168), and in all of them it looked like my CB just stopped (both players always at bottom of the screen):

https://paydirt.myfootballnow.com/watch/846#152049
https://paydirt.myfootballnow.com/watch/846#152065
https://paydirt.myfootballnow.com/watch/846#152077

And in this one, he just stops and leaves the WR wide open without any contact:
https://paydirt.myfootballnow.com/watch/846#152048

Is this the game's way of saying "he got burned by a better player"? How is my CB stopping explained? I expect a horrific m2m corner to get crushed by a good WR 1-on-1, but am trying to understand if this is how the game represents that.


jbd answered this before in something I read. If a player in coverage is bad at his type of coverage he can "stumble" which is the stop.


Thanks! I figured there was some explanation for the mechanic. Good to know moving forward.

Re: WR's vs DB's

By Beercloud
1/13/2018 11:20 pm
I think he also said that they can bite on play action. Especially if their play familiarity is weak for the play chosen. I'm not sure how intelligence plays into this if any. With exception how quick a player learns a play.