The MW5 save game editor doesn't always display the correct approximate year in the game time line.
Not all save files have the year 3015 as their starting point. You can start in career mode in a different year. For example, you can start a new career game (or import previous progress) in DLC4 (Rise of Rasalhague), which begins on 1 January 3031. This is reflected in the header of the Campaign.json file as "StartConditionId": "MWStartConditionsAsset:CareerMode_DLC4_Start". The days elapsed seem to be relative to this start condition only.
So, when I open my saved game with a game date of 3 Dec 3036 and days elapsed of 2163 in the editor, the editor incorrectly shows the approximate year as 3020.
I don't know if this StartConditionId, or similar, is embedded in the saved game files, but it's certainly found in the Campaign.json file in the same folder. If you can read it from either of those locations and adjust the approximate year shown in the editor accordingly, that would be an improvement.
The MW5 save game editor doesn't always display the correct approximate year in the game time line.
Not all save files have the year 3015 as their starting point. You can start in career mode in a different year. For example, you can start a new career game (or import previous progress) in DLC4 (Rise of Rasalhague), which begins on 1 January 3031. This is reflected in the header of the
Campaign.jsonfile as"StartConditionId": "MWStartConditionsAsset:CareerMode_DLC4_Start". The days elapsed seem to be relative to this start condition only.So, when I open my saved game with a game date of 3 Dec 3036 and days elapsed of 2163 in the editor, the editor incorrectly shows the approximate year as 3020.
I don't know if this
StartConditionId, or similar, is embedded in the saved game files, but it's certainly found in theCampaign.jsonfile in the same folder. If you can read it from either of those locations and adjust the approximate year shown in the editor accordingly, that would be an improvement.