NOTICE: This league is using the BLEEDING EDGE game engine. For more information, click here.

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)

League Forums

Main - Bug Box

Change Primary Receiver on PA TE Drag

By setherick
5/28/2016 7:35 am
I'm calling this a bug because of how badly the passing code works right now. The primary receiver on the PA TE Drag needs to be changed to the TE3.

This play could be devastatingly effective at the goal line, but right now it just sucks.

Examples just from this spin

1) QB fakes the hand off. Looks right at the wide open TE who finishes running his route with NO ONE WITHIN FIVE YARDS OF HIM , but refuses to throw the ball. Then the QB does the run to the sideline to get sacked: https://fakepigskin.myfootballnow.com/gamecenter/view/1867#333657

2) Same game. Same result. Except this time there is NO ONE WITHIN 40 YARDS of the open TE by the time the QB gets sacked: https://fakepigskin.myfootballnow.com/gamecenter/view/1867#333816

3) Different game. Same result: https://mfn13.myfootballnow.com/gamecenter/view/2128#388144

Until the QB actually looks to more than one receiver at a time, plays like this are useless when they could be the best situation specific plays in your book.

Re: Change Primary Receiver on PA TE Drag

By NeoEclipse
5/28/2016 6:21 pm
I don't agree that this is a bug, but it does raise an interesting question. The WR1 is not always the primary route on a given play. How does the read progression logic flow in this sim? Does it always start from WR1 and work down to WR5, or do some plays have a different progression, maybe starting with the slot. I play Madden and one nice thing is that the primary route is always highlighted. I wish we could see the read progression in my playbook; this could also help out with override subs if I wanted to sub in my WR1 in the slot, for instance.

Re: Change Primary Receiver on PA TE Drag

By setherick
5/28/2016 6:47 pm
NeoEclipse wrote:
I don't agree that this is a bug, but it does raise an interesting question. The WR1 is not always the primary route on a given play. How does the read progression logic flow in this sim? Does it always start from WR1 and work down to WR5, or do some plays have a different progression, maybe starting with the slot. I play Madden and one nice thing is that the primary route is always highlighted. I wish we could see the read progression in my playbook; this could also help out with override subs if I wanted to sub in my WR1 in the slot, for instance.


From what I know the QB chooses the primary WR at random based on the number of receivers running the route distance that the play calls for. Once the QB chooses his primary target, he stays on that target while that receiver runs his route to completion. Only once the primary receiver has run his route to complete does the QB look for another receiver. This is why QBs refuse to throw underneath routes that are wide open on long passing plays but throw in triple coverage down the field.

This is why I'm calling this a bug. Because the QB is never going to look at the wide open TE on this play even though that TE gets open 90% of the time.
Last edited at 5/28/2016 6:49 pm