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.

This league has just begun! Because this is a new league, it will be a few days before the allocation draft begins (the countdown timer above shows when the first pick will fire). This is a great time to get a team as you will be able to build it from scratch! If you don't want to wait for the draft, though, check to see if there is a team in an established league that you can take over.

NOTE: As of the last sim, this league was under the minimum 20% capacity. Invite your friends to join MyFootballNow to keep this league alive! Then send them to this league to become the owner of a team! The league will expire at 8/01/2025 8:00 am.

League Forums

Main - Bug Box

Broken Coverage

By Ares

7/19/2017 1:29 am

https://private75.myfootballnow.com/gamecenter/view/1415#264029

Not sure whether this is just a broken play, and thus working as intended, or if something broke in the code (but I'm leaning towards the latter). #22 is in man coverage versus the RB and just stands twirling rather than cover him. For the record, he has 96/96 man coverage ability (https://private75.myfootballnow.com/player/1041) and a pass key was called against that play. So there's really no reason he should be caught flat flooted like that, especially not against a player with 22/22 route running.

My thought is that the DB was following the original route tree design for the play, which is a curl route. However the QB threw early due to pressure; the RB adjusted to the pass and continued running straight, but the DB remained stuck following the original curl? This is my only hypothesis, but either way, it almost certainly shouldn't have happened.

Re: Broken Coverage

By punisher

7/19/2017 4:54 pm

Ares wrote:

https://private75.myfootballnow.com/gamecenter/view/1415#264029

Not sure whether this is just a broken play, and thus working as intended, or if something broke in the code (but I'm leaning towards the latter). #22 is in man coverage versus the RB and just stands twirling rather than cover him. For the record, he has 96/96 man coverage ability (https://private75.myfootballnow.com/player/1041) and a pass key was called against that play. So there's really no reason he should be caught flat flooted like that, especially not against a player with 22/22 route running.

My thought is that the DB was following the original route tree design for the play, which is a curl route. However the QB threw early due to pressure; the RB adjusted to the pass and continued running straight, but the DB remained stuck following the original curl? This is my only hypothesis, but either way, it almost certainly shouldn't have happened.

here is that RB Johnny Pruitt ( https://private75.myfootballnow.com/player/711 ) with 22 route running

anyway you won the bug/glitch of the week honor again = https://private75.myfootballnow.com/forums/thread/1/848?page=1&x=5ToWvzalXH#5424