Every contract I've ever had, I have gotten this message.
Until recently they all were accurate / made sense.
At the start of my recent (1st ever) Garrison Duty contract, however, I had ~10 days on the planet before the contract started, and I thought "hey this is pretty cool, giving us time to unload the dropship(s) and un-mothball our units in a calm and orderly manner. Okay."
But my very next contract is an Objective Raid and the same thing is happening again. On the day the contract was initially "supposed to" start, I got the message again, but the calculation was grossly off. Again, I am going to have ~10 days on the planet before the contract will officially start. What seemed kinda cool and flavorful for a Garrison Duty contract makes absolutely no sense for an Objective Raid. YES, I know I can GM-Edit the mission. That isn't the point. I've never had this before and now I've gotten it twice in a row. Am I just going to have to edit the start date of all future contracts in this campaign? Was this bug already known? (build 49.15) Or maybe something else is going on here that I am just not aware of??
