Slitherine

quote:

ORIGINAL: richlove

Very cool! I built a similar spreadsheet when trying to figure out whether I could use AP / AK groups to invade places in '42. Worked reasonably well.

=[@[APs allocated]]*550+[@[xAPs allocated]]*250

=[@[AKs allocated]]*550+[@[xAKs allocated]]*250

=[@[Possible one day troop unload]]/[@[Troop Load]]

=[@[Possible one day cargo unload]]/[@[Cargo Load]]

quote:

ORIGINAL: richlove

Sure. Like I said, I use this spreadsheet to help build Amphibious TFs w/ APs / xAPs and AKs / xAKs (in other words, before true assault shipping hits the scene). I load one unit per TF, so I know exactly where each unit goes, all w/ the goal to unload everything in one turn. It seems to work; occasionally there's some MotSup left behind on D+1. It helps to use one type of ship per unit (all APs instead of APs + some xAPs).

Anyway:

For each unit, enter values in columns H-K - you need to keep track of what ships you have available for the operation, and this is where you allocate them.

Columns L and M calculate how much can be unloaded in one turn:
Column L:

=[@[APs allocated]]*550+[@[xAPs allocated]]*250

Column M:

=[@[AKs allocated]]*550+[@[xAKs allocated]]*250

Those #s come from "6.3.3.3.2.1 OVER THE BEACH" in the manual. Looking at that, I realize that I have a buffer for APs and AKs, but not xAPs or xAKs.

Columns N and O compare the troop load and cargo load to the computed fields to see if it's theoretically possible to unload them all in one turn:
Column N:

=[@[Possible one day troop unload]]/[@[Troop Load]]

Column O:

=[@[Possible one day cargo unload]]/[@[Cargo Load]]

If both are > 1 for the unit, it should be possible. I am happy to share the .xlsx, if requested.

quote:

ORIGINAL: zuluhour

Why is there no head scratching smiley???

quote:

ORIGINAL: witpqs

Thanks!

So, you don't bother calculating the amount of load needed (considering the ships' capacity reduction due to amphibious loading) because you are always way over due to calculating number of ships required for one-day unload? Makes sense. And for cases where there is no shock attack, since the ratio is giving you a days-to-unload, so if <2 they should all unload in 2 days, and so on.

quote:



I should incorporate something to account for that, but I might express it differently. One of the problems is with larger ships when you really need/want to use all the assault shipping you have - the larger ships might not unload in one day unless they are under-loaded, especially if CD fire and such is chewing up ops points (air attacks, whatever).

What is column E, Grouping?

quote:


I don't recall seeing the '@' used that way before. Is it pretty universal or specific to the spreadsheet you are using? Is that Excel? I'm going to see if it works in LibreOffice. If so, it would simplify my code a tiny bit and make it less brittle if I can refer to the header text instead of the column number.

quote:

ORIGINAL: richlove

quote:

ORIGINAL: witpqs

Thanks!

So, you don't bother calculating the amount of load needed (considering the ships' capacity reduction due to amphibious loading) because you are always way over due to calculating number of ships required for one-day unload? Makes sense. And for cases where there is no shock attack, since the ratio is giving you a days-to-unload, so if <2 they should all unload in 2 days, and so on.

Mostly correct. I think the ratio is backwards; if it's .5 to 1 it'll take 2 days to unload.
Ah, right. If you flip it around it will directly give you "days to unload".
A nice side effect of loading this way is that you land a LOT of supplies w/ all that spare space.

quote:



I should incorporate something to account for that, but I might express it differently. One of the problems is with larger ships when you really need/want to use all the assault shipping you have - the larger ships might not unload in one day unless they are under-loaded, especially if CD fire and such is chewing up ops points (air attacks, whatever).

What is column E, Grouping?

Your ops points observation is a good one. Maybe you could adjust the 'unload per day' amount down to reflect the reduced time to unload in the face of air attack?
I wouldn't really know what guess to make. I just double-checked the manual and APA/AKA nominally unload 3,000 points per phase (manual erroneously says "turn") so even big ones 'should' unload all in one day (2 phases). But very often they do not even without air attacks, just shore fire. I haven't really paid attention to which ships wind up still unloading (at day's end) in what situations so I'll have to start watching that.

What I did do was make the percentage for the calculation be read in from the config text file, so a player can make their own decision or even change it for different situations.

Grouping was just for me to help organize my operation. IIRC, I didn't have enough lift, so I had to send two waves (aka groups).

quote:


I don't recall seeing the '@' used that way before. Is it pretty universal or specific to the spreadsheet you are using? Is that Excel? I'm going to see if it works in LibreOffice. If so, it would simplify my code a tiny bit and make it less brittle if I can refer to the header text instead of the column number.

It's Excel, and it refers to the column of a defined table. IDK if there's a similar concept in LibreOffice.
They do, haven't used it. I did find you can turn on a settings to automatically search for column headers. Then you just put the column header in single quotation marks, for example: 'Troop Load' * 1.3 and voila! Very nice, but I can't do something that might require someone to figure out settings on their spreadsheet, or is not a pretty universal markup. I'll just have to stick with the column letters. But in any spreadsheets I make by hand it will help. Thanks!

quote:

ORIGINAL: witpqs

https://drive.google.com/folderview?id=0ByVleYydeDVcQW5NVFc4V0g1Qkk&usp=sharing

There are four files there, you need three of them. Download the .exe and both .txt files. The .py file is optional, in case you want to see the source code.

One of the text files is a configuration file, the other is the documentation. Read that, and give things a try.

quote:

ORIGINAL: RangerJoe

This is a very informative and entertaining AAR. I recently purchased the game and I am still trying the scenarios. But I have a question about China. Since it appears that a lot of the restricted units in China are reacting to your push through Indochina, would it be possible to pound any garrison in Chungking and then paradropping enough forces to defeat the Japanese there? That should bring back the rest of the Chinese Army and cause trouble for Japan.

quote:

ORIGINAL: witpqs

quote:

ORIGINAL: RangerJoe

This is a very informative and entertaining AAR. I recently purchased the game and I am still trying the scenarios. But I have a question about China. Since it appears that a lot of the restricted units in China are reacting to your push through Indochina, would it be possible to pound any garrison in Chungking and then paradropping enough forces to defeat the Japanese there? That should bring back the rest of the Chinese Army and cause trouble for Japan.

Welcome!

An interesting idea! And BTW Chengtu acts as a backup to Chungking for arrival of units.

I get decent recon on Chungking and Chengtu most of the time, but what I have no idea about is the level of fortifications. They've had plenty of time to build, so figuring on level 5 or 6 is reasonable provided those were seen as worthwhile to spend the resources (engineers and supply) on. In case you haven't come across it, the fortification level modifiers are like this.

Level = Effect
1 = +10%
2 = +25%
3 = +50%
4 = +75%
5 = +100%
6 = +125%
7 = +150%
8 = +175%
9 = +200%

So basically the defense would get doubled on account of fortifications if I am right about the forts that have been built.

Paratroopers often get dropped with no supply (need lots of extra airplanes to get supply too), and that means fighting at 25% effect. It all comes out to mean that you have to drop a fairly substantial force, because only one or two days of bombing won't wear the defense down far enough. And a longer bombing campaign alerts the defense and they can bring in reinforcements, AA & fighter CAP (both VERY bad for paratroopers, too!), and so on. Transport planes can only drop paratroopers within their normal range, which complicates matters a little more.

Chungking is stronger as I recall, but I've seen Chengtu go down to >6,000 troops in 2 units. Probably still too strong to pull it off. But the opportunity might still come. I'll be watching!

quote:

ORIGINAL: Roger Neilson 3

Which version is the 'newest' one?

Roger

quote:

ORIGINAL: Roger Neilson 3

Ok that's fine, that's the one I use. I just had a thought maybe a new version had 'sneaked' out.

Roger

quote:

ORIGINAL: Roger Neilson 3

Cannot really tell from that snippet what is going on with the spreadsheet - sorry.

Roger

quote:

ORIGINAL: Roger Neilson 3

Its very early morning here and one of my cats is sitting on my arm as I try to type..... What is T Min Att and E Min Att?

Roger

quote:


--------------------------------------------------------------------------------

Ground combat at Surat Thani (51,68)

Allied Deliberate attack

Attacking force 24578 troops, 414 guns, 282 vehicles, Assault Value = 1113

Defending force 12649 troops, 127 guns, 63 vehicles, Assault Value = 159

Allied engineers reduce fortifications to 0

Allied adjusted assault: 247

Japanese adjusted defense: 209

Allied assault odds: 1 to 1 (fort level 0)

Allied Assault reduces fortifications to 0

Combat modifiers
Defender: terrain(+), experience(-)
Attacker:

Japanese ground losses:
331 casualties reported
Squads: 46 destroyed, 27 disabled
Non Combat: 0 destroyed, 21 disabled
Engineers: 0 destroyed, 2 disabled
Guns lost 18 (7 destroyed, 11 disabled)

Allied ground losses:
134 casualties reported
Squads: 0 destroyed, 12 disabled
Non Combat: 0 destroyed, 4 disabled
Engineers: 0 destroyed, 4 disabled

Assaulting units:
Gardner's Horse Regiment
26th Indian Division
20th Indian Division
3rd Carabiniers Regiment
5th Indian Division
3rd (Special Force) Division

Defending units:
112th Infantry Regiment
11th/A Division
2nd INA Gandhi Regiment
11th/C Division
29th Army
32nd Field AA Battalion


--------------------------------------------------------------------------------

Ground combat at 60,51 (near Chiang Mai)

Allied Deliberate attack

Attacking force 21954 troops, 394 guns, 242 vehicles, Assault Value = 483

Defending force 10628 troops, 43 guns, 0 vehicles, Assault Value = 241

Allied adjusted assault: 312

Japanese adjusted defense: 19

Allied assault odds: 16 to 1

Combat modifiers
Defender: terrain(+), leaders(+), disruption(-), morale(-), supply(-)
Attacker: fatigue(-)

Japanese ground losses:
712 casualties reported
Squads: 3 destroyed, 56 disabled
Non Combat: 0 destroyed, 2 disabled
Engineers: 0 destroyed, 1 disabled

Allied ground losses:
103 casualties reported
Squads: 0 destroyed, 6 disabled
Non Combat: 0 destroyed, 3 disabled
Engineers: 0 destroyed, 2 disabled

Assaulting units:
23rd Indian Division
17th Indian Division

Defending units:
29th Division


--------------------------------------------------------------------------------

Ground combat at 59,53 (near Chiang Mai)

Allied Deliberate attack

Attacking force 13157 troops, 145 guns, 73 vehicles, Assault Value = 367

Defending force 9554 troops, 16 guns, 7 vehicles, Assault Value = 229

Allied adjusted assault: 190

Japanese adjusted defense: 10

Allied assault odds: 19 to 1

Combat modifiers
Defender: terrain(+), leaders(+), disruption(-), fatigue(-)
morale(-), supply(-)
Attacker:

Japanese ground losses:
849 casualties reported
Squads: 3 destroyed, 82 disabled
Non Combat: 0 destroyed, 4 disabled
Engineers: 0 destroyed, 0 disabled

Allied ground losses:
537 casualties reported
Squads: 2 destroyed, 75 disabled
Non Combat: 1 destroyed, 10 disabled
Engineers: 0 destroyed, 0 disabled

Assaulting units:
1st Burma Brigade
2nd Burma Brigade
2/17 Dogra Battalion
2/15 Punjab Battalion
22nd (East African) Brigade
14th LRP Brigade

Defending units:
53rd Division


--------------------------------------------------------------------------------

quote:


--------------------------------------------------------------------------------

Ground combat at 62,66 (near Pakse)

Allied Bombardment attack

Attacking force 3033 troops, 46 guns, 18 vehicles, Assault Value = 93

Defending force 1860 troops, 3 guns, 0 vehicles, Assault Value = 19

Assaulting units:
11th Airborne/C Division

Defending units:
2nd Ind.Mixed Brigade
33rd Division


--------------------------------------------------------------------------------

quote:


--------------------------------------------------------------------------------

Ground combat at Ternate (78,102)

Allied Deliberate attack

Attacking force 4402 troops, 178 guns, 101 vehicles, Assault Value = 100

Defending force 3267 troops, 7 guns, 0 vehicles, Assault Value = 36

Allied adjusted assault: 84

Japanese adjusted defense: 1

Allied assault odds: 84 to 1

Combat modifiers
Defender: terrain(+), leaders(-), disruption(-), experience(-)
supply(-)
Attacker:

Japanese ground losses:
150 casualties reported
Squads: 0 destroyed, 17 disabled
Non Combat: 1 destroyed, 2 disabled
Engineers: 0 destroyed, 0 disabled

Allied ground losses:
9 casualties reported
Squads: 0 destroyed, 1 disabled
Non Combat: 0 destroyed, 0 disabled
Engineers: 0 destroyed, 0 disabled

Assaulting units:
31st Infantry Regiment
134th Field Artillery Battalion
131st Field Artillery Battalion
147th Field Artillery Battalion
260th Field Artillery Battalion
148th Field Artillery Battalion
205th Field Artillery Battalion
871st Aviation Engineer Battalion

Defending units:
12th Garrison Unit


--------------------------------------------------------------------------------

quote:

ORIGINAL: witpqs

quote:

ORIGINAL: Roger Neilson 3

Its very early morning here and one of my cats is sitting on my arm as I try to type..... What is T Min Att and E Min Att?

Roger

I think I put this in the notes - must if I didn't - 'T' for troop, 'E' for equipment, they are the minimum number of attack type transports to unload the unit in one day, as calculated by that unload factor that is in the config file. 3000 by default, but you can change it in that config text (same place you change the bases) and whatever number you put in there will be used in the spreadsheet.

The abbreviation 'Att' for Attack might be a poor choice because the player might use the number for xAKL (250 instead of 3000) if they want.

Also, I used (as that default) what I believe is the number for one Phase, while the number for a Day ought to be 2 x Phase. I did this to account for ops point usage by other factors, such as shore fire. It would be great if the group can arrive at a better number.