Campain Bug
 

Hi guys, I am palying an American campain, I'm part of the asiatic Sqn. Manilla has fallen it's 1941, so I decieded to see if I could bag some transports in Manilla harbour. To my surprise, there's not s ship there, so on the way out I pick up noise from a carg ship, I get close enough to get a good look at it, and it's a Liberty cargo, complete with 5 in gun on the stern, and 20mm Oliekon's, and it's headed for Manilla.
Could this be a corrupt game save ? or a bug ?

Thanks.

Probably a bug. Somebody forgot to radio them about Manila falling, or maybe they are running to pick up refugees.

I'm inclined to say that it's not. I've started a campaign out of Manila much like you and on my way out of the harbor I passed a Japanese merch pulling in. It was December 9th...:doh:

But historically Liberty ships didn't exist for another 2 or so years, and why would an american ship head for a Japanese held harbour ?
I might start over.

These things happen from time to time. Sometimes the game doesn't update
all of the things it should.

I went to Saipan just after it became a refit base and did a refit.
As I was leaving I got "We are taking damage sir"
It seems that the DD I saw paroling the harbor was IJN not American.
The harbor was also full of Jap ships. Sank the DD and all the ships and did another refit and continued on my way. :yeah:

Magic

Had a similar thing happen.
Started a career out of Surabaya in Jan 42.
Picked the start at sea option, and immediately got 'ship spotted'
Was a Japanese Maru heading right for the harbour. All I had to do was submerge and wait.
Very nice start to a career!

Just started a new career out of Manila,sailed out and here's a Maru heading in.
So far this is the only time I've seen this.As you say,a nice start to a patrol :D

Well I just started over, and same area, about the 12th of Dec 41, and I get a convoy contact, merchants, and Agano class CL's, and Akizuki class DD's. :hmmm:

its a bug, not a tech one but a bug in sense someone forgot to do the timelines correct.Aggravating....luckily mods usually correct these issues.

Agreed, a bug implies that something isn't functioning as intended; in this case, it wasn't the functionality that was off, just the historical 'intention' that needed a bit more detail paid to it. ;)