I'm going to class this as a Technical issue, because I don't know where else this fits. I reported this last year, but I don't know if it was too late in the cycle to do anything about it. I've only tested this on Yearly and Monthly, but I'd assume its also a case with any amount of time, where a Leap Year Day falls between the Last Save Date and the Target Date. As an example, lets say that I want the game to save every year on June 10th, so most European Competitions are complete, and the UCL, UEL and UECL haven't reset yet. If my last Save Date was June 10th but between that date and June 10th in the next year, there's a Leap Day, Feb 29th, on Yearly, as an example, it seems to count 365 days, but doesn't factor in the Leap Day, so the save happens on June 9th and that becomes the new Target Date for saving. I was running an experiment where I had to go about 50 years on the future, and my Regular Save Date of June 10th, has slipped to, I think, May 31st, or a date close to that.
If the Save System does Auto Saves by counting days, the simplest way to fix this might be to write code that doesn't increment that counter if the In Game Date comes back as February 29th.
Recommended Comments
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now