Describe the bug
Task force movement orders that are to be executed upon receipt arbitrarily have their start date set to [ON Jan 01 001 AT 00:00] instead of the actual date the order was issued. This has a knock-on effect of giving Movement order ETAs that are 497 years in the past.
To Reproduce
Steps to reproduce the behaviour:
Start a minor powers game with a 1 day turn timer
Give a taskforce a movement order that will last longer than 1 day that is to start immediately upon receipt
After cycling the turn over, view the orders issued to the taskforce.
Expected behaviour
Set the starting time of the orders to the time the orders were received.
Attachments
Order is issued 03 September. The ETA is correct when issuing the order.
Viewing the order 1 day later. The start date is 01 Sep 001 at 00:00. The ETA also appears to be 18:43 that same day despite the orders taking 1day 18hrs, is there an off by one error in the ETA calculation? or is this a product of the ship being 1 day into its movement order?
Describe the bug Task force movement orders that are to be executed upon receipt arbitrarily have their start date set to [ON Jan 01 001 AT 00:00] instead of the actual date the order was issued. This has a knock-on effect of giving Movement order ETAs that are 497 years in the past.
To Reproduce Steps to reproduce the behaviour:
Expected behaviour Set the starting time of the orders to the time the orders were received.
Attachments Order is issued 03 September. The ETA is correct when issuing the order.
Viewing the order 1 day later. The start date is 01 Sep 001 at 00:00. The ETA also appears to be 18:43 that same day despite the orders taking 1day 18hrs, is there an off by one error in the ETA calculation? or is this a product of the ship being 1 day into its movement order?
