The new user interface is in preview!

Want to check it out? Click here! (If you don't like it, you can still switch back)

The draft is underway!

Click here to go to your war room, or visit the war room item in the draft menu.

League Forums

Main - General MFN Discussion

Re: Pass Blocking needs improvement

By setherick
1/31/2016 2:38 pm
jdavidbakr wrote:
Right now the QB might check down to a short route on a long pass play if he reads a blitz or gets under pressure, but if a long pass play is called that is the first priority - so yes, he waits for his #1 option before checking to his next options.


OK - Looks like it's time for me to remove all of my long passing plays then. If I have to wait for a WR to get down field 20 yards before starting on a second read, I'll be sacked almost every play with the way OL/DL code works now.

Re: Pass Blocking needs improvement

By Webster922
1/31/2016 2:39 pm
How long he stays in the long zone should be determined by how much pressure he's under.

Re: Pass Blocking needs improvement

By sealbc
1/31/2016 2:42 pm
A qb in the nfl gets the ball out in less then 8 sec.If they are holding it longer it is never good sign before a sack takes place.This may also be why we are getting more sacks.The qb is holding the ball too long.

Re: Pass Blocking needs improvement

By setherick
1/31/2016 2:43 pm
jdavidbakr wrote:
setherick wrote:
The easiest way I could think to make it work programmatically would be to split the field into three zones - long, intermediate, short. The QB checks to see if a WR has reached the long zone, if not checks the intermediate zone for open WRs, if not checks the short zone. Then cycle back through.


That's an interesting thought, I will take that into consideration. The question remains, though, how long should the QB stay in the long zone on a long pass? If it's so short then he'll always throw shorter passes.


Here are some immediate considerations: Number of long routes, pressure, down and distance, game situation (losing, half, etc.), WR/CB match ups (not sure how to make that not be performance intensive). I'll have to give it some additional thought.

----

I've thought about this for a bit now. It seems like the easiest way to do this programmatically would be to add a parameter to the down and distance in gameplanning. So on first and medium, you might say scan long zone for a short period of time. But on third and long, you might say scan long zone for a long period of time.
Last edited at 2/01/2016 4:50 pm