Matrix Games Forums

I was hoping that you could bring him back from v1.21 save game. By the way,
your Tom and Jerry; which one is programmer and which one computer bug...LOL[:D]

Can't leader pool be re-written? Like when my COL Yamashita's sub comes back home, i could
replace him with someone more willing to help allied war effort[;)]

which one is programmer and which one computer bug

The little guy is the programmer [;)]

Can't leader pool be re-written?

The *only* reason I keyed in on this one so fast is the leader that got replaced on the Pike was not a real leader, it's one of the game generated ones. These made up leaders are all invented when the game starts so no two games are identical.

I think I have been able to create the disappearing leader. What I did was start scenario 15 on non-historical as the allies. The only move I made was to create an air combat TF with the saratoga and assign Spruance to it. I set the home port to LA and made the destination LA. I set the TF to non-disband. I then ran the game until the Saratoga reached LA. Once in LA I then set the TF to auto-disband and ran the turn. The next turn I then create a new air combat TF with the saratoga, but spruance is not on the list of available commanders. I have run the turn twice and both times spruance is not on the list of available commanders. Maybe he got assigned to a different task force by the computer, but I have been unable to find him. I hope this helps.

No, you have uncovered a completely different bug actually.

Frag, doesn't that whole auto-disband creature - I mean, "feature" - need to be consigned to File 13?

Does the 'auto-disband' problem only affect 'real' TF commanders or ship commanders too if they act as TF commanders as well?
I use the 'auto-disband' option often for ships/TFs I transfer to a new home base or damaged ships/TFs assigned to a repair facility. And for this kind of TFs I usually do not assign separate TF commanders.

I lost all good adrmirals in april japan campaign
I do not saver often and has no save "before"[:@]

I just started a new game and I already have multiple subs in minelaying TF's.
To avoid the above mention bug, should I seperate them only in port, or disband them?

I haven't pinned down exactly where it goes wrong, but it seems to steal commanders only when there are other TF's in the same hex when you do the split.

Take careful notes of who's who, do your splits, run that turn and see who is who. You will not see the change until the turn is actually run.

If they didn't change, you are good to go.

Split the TF's by taking out the ships that are *not* the TF commander (the one with the # beside it).

So they can be split at sea, but the flagship needs to be the remaining sub in the original TF?
Are only sub TF's affected?

It appears to be sub related in that particular caes. Save before you do the split and check each sub after you have ended the turn. If they all show the original leaders, you are ok. I can't give you the exact details.

Will this affect A.I. TF's?
Does the A.I. use auto-disband?

no ... they don't just expensive leaders