Slitherine

quote:

24) When a task force was created, all data was not properly cleared, causing the new task force to have the destination, loading status or speed settings of the previous task force with the same number. Fixed.

• Start with a lot of smallish transports in a port (e.g., Espiritu Santo), with a lot of big units (like U.S. Marine Regiments) to transport.
  
  
• Split the transports into TFs of two or three transports each, with each TF handling one regiment (e.g., TF 201, 202, 203, etc.)
  
  
• Once all the transport TFs have started loading, merge all the transport TFs into one big TF, e.g., TF 201.
  
  
• At a different hex (e.g., Sydney), create a new transport TF (e.g., TF202). You will find that the new TF (with the same ID number as one of the "temporary" TFs you just created and deleted at Espiritu Santo) will have a lot of the same information as the "temporary" TF, including cargo and passengers from Espiritu Santo, is now loading that cargo and Marine units from Espiritu Santo even though the TF is in Sydney Harbor.