Page 1 of 1

TF's aborting mission?

Posted: Wed Feb 19, 2003 4:52 am
by ismo
It used to be easy to get enemy transport TF's
to abort their mission by placing surface combat
TF at their destination base. Is this still possible?
I had a powerful TF at Broome and they still
managed to invade it! How do you initiate
surface combat! How do you make them to
abort their invasion?

not easy to trigger surface combat ...

Posted: Wed Feb 19, 2003 1:04 pm
by deVada
Hi !

Generally, know-how in topic of surface combats is well represented in the manual, but it seems that You had not enough preparation points, or the enemy TF just slipped undetected due to poor number of search aircrafts nearby.

In older versions of game, it was completely enough to place a single destroyer in each base in danger and the enemy was unable to land there (during the execution phase, if TF left on ROS in the base he could unload troops manually) until he had a surface combat tf to engage Your destroyer.

Worked fine against AI but it seems that in latest versions this kind of bug is removed ...

If do You not have the manual, send me an email.

Enjoy!
Peter

Posted: Wed Feb 19, 2003 3:39 pm
by Mike_B20
I've experienced the same thing in a game vs the computer AI.
I had 3 surface TF at Timor totalling about 40 ships, including BB's, expecting an invasion fleet of Japs.

The Japs turned up with a CV fleet, BB's and 2 or 3 AP fleets.
My fleets had been sitting in Timor for a few turns with react range of zero.
Most of the AP's sailed straight through my tasforces( one was annihilated by tf's), though intercepted and mauled by air attacks and landed 3 divisions.

Timor was under control of Macarthur's SW Pacific, each TF of mine was commanded by a good surface fleet commander and Macarthur had about 180 pp's. Two of my fleets were under Asiatic fleet command and one under ABDA.

I've seen the message in yellow print 'surface fleet detected at so-and-so yada yada' pop up sometimes when a turn is played with high detail reports but am not sure of the entire message as it displayed too fast. From memory this message was associated with aborted invasions in previous version.