I do want to jump in here and make a statement about the philosophy of the game engine development, which has been my philosophy from the beginning, but since it's been awhile since we've had much movement in the game engine development it's not been stated recently and a lot of you may never have heard me say it.

There are two parts to MyFootballNow - the more obvious one is the user interface. That's been the focus of mine for the last several years, because the old UI was dying (and indeed it did die before I was completely ready for it to). The changes in the UI are primarily cosmetic - improving ways to interact with the game data (and by 'game data' I mean both the way you input your plans and the way you view the results of the sim). I'm still pushing changes there throughout the month and am making these monthly updates to let you know what happened.

The second part is the game engine itself. This is a separate system that actually performs the simulations. This code has not beet touched (save for bug fixes) for some time until about last month. But because this is the heart and soul of the game itself, it's significantly more controlled in it's releases. Here's the release process:

1. Work is done on the game engine. There is one league, MFN-1, where those changes are released immediately. When this happens, I'll make an announcement in that forum as to what changed. All other leagues continue to use the stable engine.
2. Feedback is received by users in MFN-1 and the product committee. Once the changes are considered stable (usually after a full season has run in MFN-1 with the changes and everything looks good), I will make a general release. The general release will go this way:
a. I'll make an announcement here that 'game engine version x is released!' All changes in the game engine will be detailed in that announcement.
b. Leagues do NOT start using the new engine right away. They will switch to the new engine after the END OF SEASON stage. That way every league's season completes using the same version of the game engine.
c. If there are UI changes (i.e. new warnings, interfaces, etc) as a part of the game engine update, those will not display on any leagues until those leagues are using the applicable game engine version.

My goal as we get back into the game engine is to make incremental changes, and release much more often. But the rate would be at most once per one or two seasons, so that MFN-1 has plenty of time to beta test the changes.

But rest assured that no changes to game logic, player signing logic, etc, will be made to any existing leagues (except MFN-1) mid-season or without proper announcements.

Can we please get back the option to void rookie contracts before training camp

Is there any chance of either improving the play Overuse Penalty or getting rid of it entirely? Would greatly prefer that a league admin be able to set minimum or max # of active plays and maximum use per game. The AI coach would be triggered to change the play at max use level. I know that there are those who would not like to play the game with those rules, but without a doubt, it would be the best way to both increase variety and challenge in gameplanning along with ensuring compliance and fair play.

If that can happen, I would strongly urge a change in the AI coaches play selection to limit the GL offense to GL or 0-1 yd to go situations only, instead of on 1st and 10, or other inappropriate play situations. Otherwise you get way too many GL play calls, which is one of the reasons RO leagues are much less of a simulation of NFL play, as the GL offense, the 2 TEs, and 311 "autos" the use of the GL defense.

Those are my two major asks, have several minor, but those two would be game changing.

One other thing that I forgot.

End of 2nd qtr, when you have the opposing team pinned in their red zone or inside the 10, would like to see full use of time outs to increase the chance of either getting the ball back at midfield or better and/or getting a sack. Otherwise, that advantage is totally wasted. As it stands, maybe one Time Out is used. Getting the ball with no time outs with 30 seconds left is still better than just letting the clock run out IMO.

Thank you for the detailed response.
Seeking some truth, finding it.
Still have some concerns, but I have less concerns.

All of this originated because there are teams that consistently use the same D plays and also keep any and all of their opponents below 50 ypg rushing.
Clearly, there IS information people are using that is not know to everyone.


The focus of my arguments has always been about transparency.
Although your riposte is admirable and focused, it is still lacks a sharing of clarity, transparency, and the information the community needs to stay current to all of the updates on a week to week basis.

We still want instructions, you focused on me instead of us.
See my PM to you ;)

Also, not cool to drop PMs into the public forums. Not cool.
...but I can play that game should you choose to continue.

I think it's literally no secret to anybody that blitzing stuffs the run for the most part... So no super secret stuff coming from mfn-test.

I get you've an edgy online persona here but you've picked literally the wrong person to target. Went away from what historically works (heavy blitzing) to zone in mfn-test to test changes. Even adopted pass offence to test passing changes. Clearly that's worked out...

Anx if course, since none of those changes are in any of other leagues, not sure how anyone benefits from such super secret knowledge.

You also conveniently ignore the fact that all the logs, stats and games in mfn-test are publicly visible. Even you can see games and analyse... The roadmap is also an excellent source of info as to what's planned.

Now again, as I told you privately, if anyone abused mfn-test, then I'll be the first to call them out. Same with product committee, a concept you were in favour of but is it true you backed out when invited?

Ps, why bump the may update?

Closing this thread, I'll start closing old updates and only keep the newest one active.