Game Engine Beta Discussion: Gameplay Updates for 4.7

And he still took the sack! Wow!

The PA Rollout could use a look, this is becoming common in the current version:

https://mfn1.myfootballnow.com/watch/21804#3979306

Players who are significantly injured during a game need to be pulled. Way too many times (including today) I've had a RB injured early in the game play at half speed or less for the rest of the game, becoming an absolute liability to the offense. A coach would never allow it.

I'm presuming the player is pulled based upon fatigue, since that's the standard player rotation method, and that a player also pulled IF ruled out, ie based upon the injury type.

Sounds like the two approaches need to be merged.

Wow, some of the QB actions definitely don't look good at all. Thanks for those plays. I'll see if I can get a beta update in time to have a few games between. I'll also look at the safety reaction time logic in run key, they should be anticipating the run in that situation.

As for the version numbers, I just want to indicate that things are changing, but communicate that each change will be iterative and much more frequent than they have been. To be honest, we're not in version 4.6, we're actually in version 0.4.6 but no one thinks of it that way so 4.7 is going to drop that initial zero. In my professional life in general as well I've started having much smaller changes qualify for the first level minor version and have only used the next layer for bug fixes.

Will we be seeing version 4.7.1, 4.7.2 for bug fixes or will it only be jumps between 4.7, 4.8, 4.9 etc?

Would changes like zone improvements, passing improvements currently planned for 4.7 ALWAYS be a minor release going forward, ie 4.x? Analysing play data for an engine would be skewed otherwise.

( For those tech minded, the API provides league current season and game engine used; as a consequence, you can then map individual game data to a specific game engine. Useful as a data analytics process to assess changes, I guess. )

• 4.7.1, 4.7.2, etc. (patch versions) cover fixes we identify and must implement in the current release. For example, the 32-bit integer salary cap issue was a bug fix; resolving something that causes the engine to crash would be a bug fix; but something like an adjustment to zone coverage—unless it’s an egregious issue—would not be a bug fix.
• A bug fix would be rolled out to all leagues immediately, whereas the minor version numbers (4.7, 4.8, etc.) are actual releases that contain iterative improvements.
• Anything that intentionally alters the logic in the simulation would be a minor version update.
• Minor versions will be rolled into the leagues as their seasons end; a minor version would never be applied to a league mid-season (with the exception of MFN-TEST).
• The major version (4.7, 5.0, etc.) would be used on significant milestones or architectural refactors.

Wanted to let you all know that for week 13 I have made some changes to address the QB pocket movement and blocking logic. However, doing this did impact sack rate as well as rushing (obviously just the blocking impacted rushing) so I had to work a bit on getting that back to where it was before this fix. Please report any continued issues especially around these things as we finish out the season. If something comes up I'll try to deal with it before the end of the season so we can hopefully get a full season of untouched simming in 2079.

In that instance, will that be reflected on both the league home page and in the api or will only X.Y be displayed?

If you're analysing plays against engines, then need to know the engine being used for each game. Wondering if it's sufficient to just consider X.Y versions for that analysis, probably would be.

Structures looking at would be league -> league_seasons, where league_seasons has the leageid, season number ie 2048 and game engine 4.6. If the major.minor versions never change within a season, then that should be fine - otherwise would have to add game engine on a week be week basis onto games.

There should never be anything in a X.Y.Z release that will change any analysis, those will always be the X.Y releases. The bugfix versions are visible in the roadmap but won't be visible in the API or league footers.