Sorry for the delay in getting a new update, took a little longer than I had hoped. Thanks for your patience!

I think I found an issue with the M2M juking with higher rating M2M players getting beat too much, and just deployed a beta update for tonight's game. Basically what to look for here is higher rated M2M players getting beat less frequently on the stutter stepping.

B&R is still way too broken to get a good test: https://mfn1.myfootballnow.com/watch/8581#1556233

Also, it's hard to tell if the tweak did anything with the nerfs still in place and WRs dropping 50% of their potential catches.

Because this update did result in tighter coverage I did increase the catch probability.

Before or after the update?

In this update.

I'm going to try to have a tweak in for tonight's games, I want to make sure what you reported is not the issue I tried to fix still, but I believe it might be.

Thanks for posting that play, that wasn't specifically what I was trying to fix but it was another issue with M2M coverage. I have made an update for tonight's game that addresses that specific issue - where a defender is 5 or so yards off the LOS and is unable to lock onto his assignment.

Is it a M2M problem or is it a B&R problem? It's all over 0.4.3 in all leagues.

General Question: Did you adjust how far over safeties will play? I'm seeing more safeties getting to the sideline.

1) https://mfn1.myfootballnow.com/watch/8588#1557461
a) Shouldn't have been a drop.

2) https://mfn1.myfootballnow.com/watch/8588#1557462
a) I don't get this play. It's a 100 vs 100 M2M / Route roll, and the DB has 20 SP on the WR. But the WR runs away from him like he's standing still.

3) https://mfn1.myfootballnow.com/watch/8588#1557468
a) The bottom DB does some weird things on this play, but he stays with the WR.

4) https://mfn1.myfootballnow.com/watch/8588#1557473
a) What happens here?

5) https://mfn1.myfootballnow.com/watch/8588#1557498
a) QBs are still throwing these awful passes that end up 5-10 yards behind the play when not under pressure.

6) https://mfn1.myfootballnow.com/watch/8588#1557510
a) There are some bad things going on in the play. The DB jerks around while running upfield. He gets in front of the WR to make a play on the ball I guess. Then he teleports behind the WR to make the tackle.

7) https://mfn1.myfootballnow.com/watch/8588#1557513
a) Another bad pass while not under pressure.

8) https://mfn1.myfootballnow.com/watch/8588#1557531
a) I'm not sure how this INT happens.

9)https://mfn1.myfootballnow.com/watch/8588#1557540
a) QB throws it to the DB at the spot where the WR stutters instead of throwing it to the WR.

10) https://mfn1.myfootballnow.com/watch/8588#1557542
a) 100 M2M DB doesn't even try to engage downfield.

It's a M2M problem. It looks like a B&R problem, and I spent a bunch of time looking there for it, but finally found that it's actually M2M.

No, I didn't make any changes specifically for this, but the tweak I made may have impacted how they play.



I'm going to address the drops once the coverage gets fixed. As you have stated, these drops are higher to offset coverage errors. If we can get coverage errors fixed I can remove this protection.



This looks like it was a bite on the stutter, you can see that the DB starts off in the wrong direction and then immediately turns back to the WR. A 100 vs 100 should be a 1% probability that the DB bites.



He would have been left in the dust before this last update. There's some weird rendering with how he turns, but that is what last night's update addressed.



No idea on that one. This is an unrelated bug. It's been reported before, but it's pretty tough to reproduce in a dev environment.



I want to address some of the QB targeting logic. It gets really complicated to calculate especially when the QB throws the ball before the WR's last cut. Definitely still some work to do on this.



That's rendering errors, again the same as #3 - I'm working on making sure the DB is in the right position, but need to adjust his "look at" logic.



Same as #5



That's a linebacker plucking the ball out of the air as it passes by him. Some of this makes me wonder if my pass speed is higher than it should be. The QB has logic to throw over the linebackers but there is logic for him to not see them, if this is rare I'm not overly concerned but if it's happening frequently it needs to be addressed.



I think this may just be another case of the ball not having enough altitude to get past the DB.



That one looks a lot like the issue this update addressed. It doesn't even look like a stutter, what probably happened is that for some reason it didn't trigger the code that I updated.