New Sticky Note

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: This kind of stuff needs to be addressed

By WarEagle
12/29/2017 8:09 am
setherick wrote:

In the next major release, QB fatigue will be adjusted to kick in at 40 passes, which makes things a lot better, but it's still not great.


It shouldn't "kick in" at all based on number of pass attempts. At least not unless it gets to an unreasonable number, like 60 +

Re: This kind of stuff needs to be addressed

By setherick
12/29/2017 8:17 am
WarEagle wrote:
setherick wrote:

In the next major release, QB fatigue will be adjusted to kick in at 40 passes, which makes things a lot better, but it's still not great.


It shouldn't "kick in" at all based on number of pass attempts. At least not unless it gets to an unreasonable number, like 60 +


Not saying it should. Only explaining the situation. With coverage as bad as it is, QB fatigue is the only thing preventing QBs in all leagues from completing 70-85% like they are in the beta leagues. Even mediocre QBs.

EDIT: This actually needs some more explanation of why it's so horribly broken and why convoy QB systems are so dominant. Right now, it's insanely easy to hold teams to ~1.0 YPC during a game by run blitzing. This makes teams very dependent on the pass. But since QB fatigue is effed right now in non-beta leagues, teams that try to pass hit a wall and fall apart in the middle of games. Since they can't run, and eventually the QB stops hitting receivers, you see offense grind to a halt. This is why owners have been convoying QBs. You don't hit the same wall, and the offense can continue to move the ball after the QB starts hitting the fatigue wall.
Last edited at 12/29/2017 9:55 am

Re: This kind of stuff needs to be addressed

By vcr5150
12/29/2017 10:53 am
setherick wrote:
vcr5150 wrote:
So my Cleveland team in League 85 played a computer team. We were 5-2, the computer team was 2-5. My QB is rated 92 out of 93. During the 1st half, my QB had a stat line of 12-19 257yards 1int 2TD.

Then in the 2nd half, the computer team must have made some amazing adjustments. My QB's 2nd half stat line was 3-17 44yards 1int and 4 sacks.


It's not halftime adjustments, it's QB fatigue. In the non-beta leagues, QB fatigue is effed. It kicks in around 20 passes, which is why you see QBs fall apart in the second half of games if you throw the ball at all in the first half. It's what has led to the explosion of the convoy QB system.

In the next major release, QB fatigue will be adjusted to kick in at 40 passes, which makes things a lot better, but it's still not great.


Thanks for taking the time to respond. I just want to add that I have the max fatigue to pull a QB set at 60 for that league - and the backup never played a down. If the fatigue would have made that QB reduced to garbage, wouldn't the backup at least make an appearance?

Re: This kind of stuff needs to be addressed

By vcr5150
12/29/2017 12:19 pm
Also, in another league I had another high rated QB totally fall apart in the 2nd half against a computer run team. It was game one of the season, and the computer team has won 4-6 games the past few seasons so they are no juggernaut.

I have never seen such a drop off between halves against a player run team as I have now twice in a span of a couple days against computer controlled teams. Might just be a coincidence - curious to hear if anyone else is experiencing it.

Re: This kind of stuff needs to be addressed

By vcr5150
1/12/2018 2:27 pm
Once again, a game against a computer run team has my QB crapping out in the 2nd half. 1st half he was 10-16 for 129 yards and a TD. In the 2nd half he was 7-24 35 yards and an INT.

I NEVER see this kind of polarity in games with a team run by a person - it is ALWAYS against a computer run team.

Re: This kind of stuff needs to be addressed

By punisher
1/12/2018 3:34 pm
vcr5150 wrote:
Once again, a game against a computer run team has my QB crapping out in the 2nd half. 1st half he was 10-16 for 129 yards and a TD. In the 2nd half he was 7-24 35 yards and an INT.

I NEVER see this kind of polarity in games with a team run by a person - it is ALWAYS against a computer run team.



that game was this game


box score = https://cust35.myfootballnow.com/box/4163
game log = https://cust35.myfootballnow.com/log/4163
game center = https://cust35.myfootballnow.com/watch/4163#747026


vcr5150 is Seattle = https://cust35.myfootballnow.com/team/16
Computer is Houston = https://cust35.myfootballnow.com/team/14


that QB was this guy = https://cust35.myfootballnow.com/player/6535


Houston won 16-10 over Seattle.


it is the 8th midweek for Custom 35
Last edited at 1/12/2018 3:35 pm

Re: This kind of stuff needs to be addressed

By amalric7
1/14/2018 5:20 pm
A 34-18 lead with just over two minutes to go...lost in overtime.

TD (PAT failed), successful onside kick
TD, successful onside kick (same player!)
FG

WTH??

Re: This kind of stuff needs to be addressed

By punisher
1/14/2018 9:16 pm
amalric7 wrote:
A 34-18 lead with just over two minutes to go...lost in overtime.

TD (PAT failed), successful onside kick
TD, successful onside kick (same player!)
FG

WTH??



that game is this game


box score = https://mfn7.myfootballnow.com/box/5476
game log = https://mfn7.myfootballnow.com/log/5476
game center = https://mfn7.myfootballnow.com/watch/5476#1050036


Baltimore = https://mfn7.myfootballnow.com/team/9
New York (A) = https://mfn7.myfootballnow.com/team/8


Baltimore win 37-34 in overtime over New York (A)

Re: This kind of stuff needs to be addressed

By vcr5150
2/02/2018 12:27 pm
Another bad loss to a computer run team. My team just kicked a go-ahead field goal with under 2 minutes and a 3 point lead. Then this play happens:

https://mfn74.myfootballnow.com/watch/2500#459348

UGH!!!
Last edited at 2/02/2018 12:29 pm

Re: This kind of stuff needs to be addressed

By MasonBronos
2/02/2018 12:29 pm
He should've been tackled