Here's something new and different. My QB freaks out and throws to a blocking TE: https://beta87.myfootballnow.com/watch/745#137029

The RB didn't stay home to block so the QB didn't have him to freak out and throw the ball to. Is the QB trying to "ground" the ball on these plays or is this just bad dump off logic still.

It may be him trying to ground the ball, I am suspicious that there is a logic flaw that is causing the player to still make the catch.

Can you address the passes to blockers? By itself, it's annoying. When it results in a pick six, well, then I have no words: https://mfn1.myfootballnow.com/watch/7113#1285527

But this is probably the best one I've seen ever: https://agent86.myfootballnow.com/watch/889#159160

The RB is being pushed way out of the play and the QB keeps looking at him even though he has a clear running lane until the QB gets to the sideline and then he finally runs.

The second play reminds me that I haven't mentioned that QBs are no longer running the ball, again. They are running to the sideline before they start running upfield even when they have clear running lanes and no one is open.

(Not that I'm sure JDB is even following the MFN-1 threads.)

Yes, I have code in testing that is addressing it, but still massaging it so that it's not causing issues before releasing it to beta. I'm actually doing a pretty extensive rewrite to the QB logic to address his reads/timing, didn't intend it to go as deep as it's going but I think the end result is going to be a good upgrade.

Awesome. I look forward to testing it.

EDIT: Speaking of testing, I have 8 picks in rounds 4 and 5, so bring on the updates to draft classes. :)

Are lightweight players still be getting a speed bonus? Or why do WRs make the best RBs?

I've been drafting RBs and turning them into WRs and playing them as hybrid players for a while, and I know that others have been turning all RBs into WRs to get their weight down for a long time. This made a lot of sense in v 0.3.x - although I didn't completely buy in because I didn't see a big difference between 215-220 and 198 (which is where ALL receivers end up).

But I'm seeing a bigger difference now in 0.4.2. Here's two examples:

1) Blackfly's Harry Ngo: https://mfn1.myfootballnow.com/player/13269
a) The rookie speedster is averaging 8 ypc

2) My player Kenneth Hewitt: https://mfn1.myfootballnow.com/player/11646
a) I drafted this guy when I ran Detroit to be the ultimate utility player. But I noticed that he plays better at RB when he's listed as a WR.

How tied to weight is speed still? I know that the player card is now accurate in terms of how fast the player is, but how do the calculations work. Will a 95 SP player at 198 pounds still be faster than a 95 SP player at 225 pounds?

I’ve noticed that break tackle isn’t as important as I once thought. It is for the tough yards, but running out of the three wide sets or plays where they just need to get to the corner doesn’t taken much advantage of that. So, depending on how those players are used and when their runs are called can make all the difference. 95 speed is 95 speed, no matter the weight. Fatigue may differ though.

It kind of depends on game play. Speed is most important for RBs -- <70 is going to struggle to make more than 2.0 yards per carry. Second most important is Avoid Fumble unless you can stand your RB fumbling 10-12 times a season (this can sometimes be worth it).

If you are going to run outside a lot and want a home run hitter, then Ball Carry is probably more important than Break Tackle.

However, if you're a run inside team, then Break Tackle and Strength are more important. Also remember that Speed is a bonus to Break Tackle whereas Ball Carry is the ability to maintain Speed over time.

Are there going to be any updates to the draft obfuscation and/or player pool for the next draft?

We are closing in on the trade deadline for this year.

Thanks

There are supposed to be changes to the draft pool, but I'd like to know exactly what they are going to look like.