Back to start

[Mongol_Horde]

I had a fragment of some Australian brigade kicked out of Samarinda, marching through the jungle to Banjamasin for a couple of days.
The bulk of that brigade had been moved out to Kendari, and I wanted those guys to return home. Sent a TF to Kendari, loaded the troops, and set course to Darwin.

When checking the fragment after the turn - the fragment had become the parent unit (more support squads than any fragment on any ship of the TF) and reset their marching orders.

Another two more weeks in the jungle for the diggers.....

- known bug?

- fixed in AE?

[jwilkerson]

ORIGINAL: Mongol_Horde

I had a fragment of some Australian brigade kicked out of Samarinda, marching through the jungle to Banjamasin for a couple of days.
The bulk of that brigade had been moved out to Kendari, and I wanted those guys to return home. Sent a TF to Kendari, loaded the troops, and set course to Darwin.

When checking the fragment after the turn - the fragment had become the parent unit (more support squads than any fragment on any ship of the TF) and reset their marching orders.

Another two more weeks in the jungle for the diggers.....

- known bug?

- fixed in AE?

THere were dozens of fragment issues in WITP - most we fixed not all. Some of the ones not fixed in WITP may have ported over to AE - though the system changed a bit. We have continued to fix fragment issues - a substantial rework was done for the recently release patch 04.

[Mongol_Horde]

I understand from previous posts of the AE team that functions dealing with LCU fragments are spread all over the code.

Thus the above scenario might be yet another test case...


The good news: when the TF unloaded the troops at Darwin and the band played Waltzing Matilda, the troops on Borneo became a fragment again - but kept their milage [:)]


I did not check their leader, but will blame the issue on the 2nd Lieutenant with a map who assumed command on the way out of Samarinda. [:D]