Bombardment
Posted: Thu Mar 20, 2014 1:04 pm
Is there some odd reason why some task forces with the bombardment mission don't carry it out?
I'm playing the Guadalcanal scenario as the Japanese and noticed on a few occasions where bombardment TF's don't carry out that mission.
In one case I had a surface task force that I broke up into 3 bombardment tf's with the mission to bombard at Lunga/Henderson. I was north of Guadalcanal about 8 hexes and used waypoints to move them into the Tulagi hex then to Lunga rather than the defaulted path of moving around Tulagi to the south and approaching Guadalcanal thru the deep water. I knew that distance was too far for a single move.
Unfortunately all 3 TF's stopped in Tulagi and were there at daybreak. Then the next day, they moved into the Lunga hex, did not do any night bombardment and stayed there come the day phase. Retirement was allowed on all 3 TF's, all of the ships had a full ammo load and had plenty of fuel, none were damaged, all TF's were set on mission speed with the slowest ship being 25 knots, and no operational points had been used. I also had these set to return on the same path they took in.
So I did some experimentation with this. I moved the 3 bombardment TF's to a different hex but still 8 hexes from Lunga. I let 2 of the TF's use the defaulted path going south of Tulagi. The 3rd TF I used waypoints to go around the north edge of Tulagi into the shallow water and then hit Lunga. This time the TF using the waypoints stopped at Tulagi while the other 2 bombarded Lunga at night and were 7 or 8 hexes north come daylight.
I ran another test where all 3 used waypoints. 1 went the Tulagi route, one went south using the deep water route and the 3rd used waypoints with one on the shallow water atoll hex just south of Tulagi and then to Lunga. In this case again the Tulagi route stopped while the other 2 bombarded and moved on, although the one that went thru the shallow atoll hex moved 1 hex less when it moved away come daytime.
My last test totally thru everything out the window when I put the fastest ships in the north Tulagi route with waypoints and the others in the southern deep water route and no waypoints. This time all 3 TF's bombarded at night and were long gone come daylight.
So I thought I had it figured out until that last test. Is there any known issue out there with using waypoints next to each other or next to the objective hex that may cause a TF from doing a bombarding mission? Or possibly going thru an enemy base as was the case of the north Tulagi route? Any ideas or insight will be appreciated. A friend and I are hoping to start a campaign game soon and want to work out kinks that might cause undo grief later on.
I'm playing the Guadalcanal scenario as the Japanese and noticed on a few occasions where bombardment TF's don't carry out that mission.
In one case I had a surface task force that I broke up into 3 bombardment tf's with the mission to bombard at Lunga/Henderson. I was north of Guadalcanal about 8 hexes and used waypoints to move them into the Tulagi hex then to Lunga rather than the defaulted path of moving around Tulagi to the south and approaching Guadalcanal thru the deep water. I knew that distance was too far for a single move.
Unfortunately all 3 TF's stopped in Tulagi and were there at daybreak. Then the next day, they moved into the Lunga hex, did not do any night bombardment and stayed there come the day phase. Retirement was allowed on all 3 TF's, all of the ships had a full ammo load and had plenty of fuel, none were damaged, all TF's were set on mission speed with the slowest ship being 25 knots, and no operational points had been used. I also had these set to return on the same path they took in.
So I did some experimentation with this. I moved the 3 bombardment TF's to a different hex but still 8 hexes from Lunga. I let 2 of the TF's use the defaulted path going south of Tulagi. The 3rd TF I used waypoints to go around the north edge of Tulagi into the shallow water and then hit Lunga. This time the TF using the waypoints stopped at Tulagi while the other 2 bombarded Lunga at night and were 7 or 8 hexes north come daylight.
I ran another test where all 3 used waypoints. 1 went the Tulagi route, one went south using the deep water route and the 3rd used waypoints with one on the shallow water atoll hex just south of Tulagi and then to Lunga. In this case again the Tulagi route stopped while the other 2 bombarded and moved on, although the one that went thru the shallow atoll hex moved 1 hex less when it moved away come daytime.
My last test totally thru everything out the window when I put the fastest ships in the north Tulagi route with waypoints and the others in the southern deep water route and no waypoints. This time all 3 TF's bombarded at night and were long gone come daylight.
So I thought I had it figured out until that last test. Is there any known issue out there with using waypoints next to each other or next to the objective hex that may cause a TF from doing a bombarding mission? Or possibly going thru an enemy base as was the case of the north Tulagi route? Any ideas or insight will be appreciated. A friend and I are hoping to start a campaign game soon and want to work out kinks that might cause undo grief later on.
