BS!!!
We are going for the winning score and my runner goes the wrong way? You can't let this stand. We were poised to win and then this happened?
http://mfn7.myfootballnow.com/watch/274#57381

Must have been one scary defender on that play! Brutal stuff! Any way to just sim a FG attempt?

This is a terrible bug that I think I have fixed in the next engine - just so you all know, it's come up I think 3 times in the various leagues here, and I have a server that is running a full season every day and it has taken me forever to track this bug down because it only happens once every 5-6 seasons. But I believe it's been fixed in the 0.2.1 engine.

I would love to have an equitable way to fix this game - right now though I don't know of one. There is always the probability that he could have fumbled and the FG attempt never happen, or that the FG could have been missed, or even that the ensuing kickoff could have been returned for a TD or at least into FG range for the win the other way. The other thing to think about is the games that are lost because of a terrible call - i.e. that pass interference penalty with the Packers and Seahawks back in 2012 - where once the game is played any mistakes by the refs, even if it can be proven would have changed the outcome of the game, don't do so. The only way I can think to fix it equitably would be to roll back the league to re-sim the entire week, but that wouldn't be fair to the other 30 teams not affected by this game.

Believe me, I'm as unhappy with this as any of you - I just don't see a good way to fix it for this game.

Ouch, that could cost them the division perhaps, or even a playoff spot.
That's a tough way to lose :(

An injustice, no doubt.

Speaking of bad refs calls, in MFN-7 San Diego lost a squeaker to Cleveland 10-6. With 1:35 left in the game, San Diego is leading 6-3. Cleveland is at the SD 3 yd line, second and goal. Cleveland scores from the 3 but is flagged for holding on the play. The next play for Cleveland starts from the SD 5 yd line. So the holding call cost Cleveland a whole 2 yds. Cleveland then scores from the 5. Why the ball was spotted at the SD 5 is a mystery to me. Might have cost SD home field in the playoffs. Great game otherwise.

Wow, that is an interesting one - I've never seen that before. I'll definitely investigate it.

I think there are a lot of instances where holding is counted from spot of foul on here. I know if you hold in the endzone on offense its a safety but I cant recall seeing any other instances in NFL where it is counted from spot of foul. I always thought it was 10 yards from previous line of scrimmage.

There is a bug with holding that has been fixed in 0.2.1. It was from the spot of the ball instead of the spot of the foul.

Ugh... As Cleveland in that League, I completely missed that one.

Turrible refs. Absolutely turrible.

I'm having bugs come up as well. Sad, but it seems like more are appearing as each week goes by... :-(