RHS 4.14 [Eratta; Chinese Army planning]

[CobraAus]

V3.01 for BBO-RAO-RPO posted on download link page

Cobra Aus

[Ron Saueracker]

ORIGINAL: Monter_Trismegistos

ORIGINAL: CobraAus
removal of many ships which serve on off map lines of communications or which move resources essential to economies not required by our production system
Sid

Are you going to delete most of Canadian Navy? It seems that their ships were busy in Eastern Pacific in escort duty for coastal convoys.

That would be wrong. Then all the nations would need to be culled to address this. I have no idea why the map was not divided into sectors and had minimum force levels applied to these sectors (like Kwantung) to simulate such duty as coastal convoys etc.

[el cid again]

ORIGINAL: Ron Saueracker

ORIGINAL: Monter_Trismegistos

ORIGINAL: CobraAus
removal of many ships which serve on off map lines of communications or which move resources essential to economies not required by our production system
Sid

Are you going to delete most of Canadian Navy? It seems that their ships were busy in Eastern Pacific in escort duty for coastal convoys.

That would be wrong. Then all the nations would need to be culled to address this. I have no idea why the map was not divided into sectors and had minimum force levels applied to these sectors (like Kwantung) to simulate such duty as coastal convoys etc.

First, the Canadians were important in "the thousand mile war" (or "the forgotten war") - the campaign in the Aleutians - which I call "the secret war" because it was censored in US publications during the war! Soldiers families didn't believe there was fighting - it isn't in the paper!

Second, the coastal escort is unimportant only when the Japanese are stupid (and historical) - and don't attack unescorted ships in the Eastern Pacific. [There are exceptions - even late in the war - and one strange case has an I boat surface alongside a gigantic commercial schooner - flash a message about how beautiful she is - and go away. The captain owned a sailboat - so writes a friend who survived the war - the I boat didn't make it.]

Third, I do not regard it as wrong for the Allies to send Canadians to the Far East. Canadians were the largest infantry defenders of Hong Kong.
Canadians are very proud of their role in the war - and often when Gen Buckner (as commander Alaska Command) asked for help - they sent more than the USA. Sometimes the US sent nothing - but Canada always sent something.

Alaskans are treated differently than other US citizens in Canada - or at least in the Canadian Northwest. We are regarded as knowing life in the bush (not true of people in Anchorage as a rule) - and customs believes we can cross the Alcan without interrogation which they give to others at the border saying they will attempt it. It also is normal for a Canadian general to be deputy commander - or top dog - one or the other - in Alaskan Command.

[CobraAus]

V3.11 medium upgrade posted on download link page

Cobra Aus

[CobraAus]

V3.2 for RHSCVO-RAO test files posted on download link page (new download provider beening tested)

Cobra Aus

[el cid again]

My first pass test indicates I failed to copy two CVO files correctly into RAO - so while CVO works for Russian ships - RAO does not. I will resubmit.

I also am considering "the CHS solution" - make CVO (and the RPO variant of BBO) "no Russian ships at all" - and the other RHS scenarios with my "cheating fix."

ESO (not released) seems like a lot of fun - a lot more balanced than any previous WITP variant.

[Jo van der Pluym]

ORIGINAL: el cid again

ESO (not released) seems like a lot of fun - a lot more balanced than any previous WITP variant.

What means ESO?

[el cid again]

ORIGINAL: Jo van der Pluym

ORIGINAL: el cid again

ESO (not released) seems like a lot of fun - a lot more balanced than any previous WITP variant.

What means ESO?

Empire Of the Sun - which I guess should be EOS!
It is the name of a board game version of WITP - and it is meant to imply this is the Japan Enhansed Scenario Joe once theorized might be done. There are three separate objectives in doing EOS:

1) It is for those seeking play balance. You cannot be true to history and not have a game unablanced against Japan to a major degree. This is slightly less so - and provides Japan a better than historical chance of setting up an autarky (functional regional economy) to serve as a foundation of defending the Empire from the inevitable counteroffensives.
This is done by assuming DIFFERENT planning, outlined below.

2) It is for those seeking to play the Allies vs AI - so the AI has a better chance of standing up against a human opponent.

3) It is for JFBs - giving them "toys" they otherwise must dream about.

The basis for this - I believe whatever is done must be done in the light of 1941 concepts and politics - is as follows:

1) The IJN told the IJA it would have a very hard time defeating the enemy, so the IJA decided to form an integrated strategy and policy, instead of business as usual;

2) In the context of (1) above, a joint planning committee was established modeled on that used by Gen Yamashita (led by Col Tsuji) for the campaign in Malaya. Pre-existing plans of existing institutions was used rather than ignored, including:

a) Foreign Ministry (and a secular association) planning re forming a genuine "co prosperity sphere" - this planning having no less than Gen Tojo as a fan - but in the end it was ignored; This planning is implimented by the mechanism of apponiting FM officials rather than IJA officers to handle relations within the sphere;

b) Naval planning re building escorts, creating the Grand Escort Command even before the outset of hostilities, building merchant ships, and allocating reasonable resources to these efforts;

c) Implementing plans of the Nakano School (an IJA institution related to intelligence, special operations, grand strategy and spin), specifically including proposals by the students of English speaking nations;

d) Implementing mobilization planning of the Munitions Ministry.

This planning committee changes the command structure to that eventually adopted by Japan, but soon enough to matter. It changes the resources allocated to the commands, and to various institutions, in time to matter. It implements changes to production, soon enough to matter. This committee is formed in July, 1941 (because that is the date of the decision to mobilize) and its major findings are implemented in October, 1941. The committee integrates Army, Navy and civilian planning, and it strikes a deal between Tojo and Yamashita (and the triumverate of generals who actually ran Japan) - Tojo will be the head of state; Yamashita will be the Japanese Zhukov; and a very Japanese system combining Imperial General HQ, the triumverate and the strategic planning committee will call the shots. Japan will seek to divide and isolate its enemies from each other - and to establish a position of strength based on interior lines, control of critical resource areas, and seizing or contesting points needed by its enemies to move resources or supplies critical either to their economies or to any offensive war effort. It also will hope to deny the enemy the opportunity to build bases early in areas too close to critical resources - by seizing those areas and forcing any build up to occur after their recapture. It will do this in the context of a combined arms strategy with air dominance: Tojo himself was air minded - former head of the JAAF - and one of the first Japanese leaders to travel by airplane on a regular basis and is likely to have supported such a proposal. But the foundation arm of Imperial Forces is the infantry - Japan will attempt to bring its superior numbers of troops to bear in a timely way at places that may matter. The IJA mostly sat out WWII - this IJA won't do that.

[Mifune]

"ESO (not released) seems like a lot of fun - a lot more balanced than any previous WITP variant." Cid, so when do the rest of us get to taste that morsel?

[CobraAus]

V3.3 upgrade for CVO posted on download link page

Cobra Aus

[witpqs]

In the latest pwhex.dat file:

There is a low capacity ferry between 39,59 and 40,59. Press the R key and the road that represents the ferry only appears in 39,59 (it runs up to the hex side), not into 40,59.

The hexside between 36,59 and 37,59 - Press the F6 key - is red in 36,59 and green in 37,59. The hexside is actually a different color on each side, look closely and you'll see it.

The hexside between 38,59 and 39,59 - Press the F6 key - is white in 38,59 and blue in 39,59.

[CobraAus]

V3.3 RAO posted on download link page any problems let me know ASAP

Cobra Aus

[el cid again]

ORIGINAL: witpqs

In the latest pwhex.dat file:

There is a low capacity ferry between 39,59 and 40,59. Press the R key and the road that represents the ferry only appears in 39,59 (it runs up to the hex side), not into 40,59.

The hexside between 36,59 and 37,59 - Press the F6 key - is red in 36,59 and green in 37,59. The hexside is actually a different color on each side, look closely and you'll see it.

The hexside between 38,59 and 39,59 - Press the F6 key - is white in 38,59 and blue in 39,59.

Hex 40, 59 has code 229 - trail SW and SE. IF the hexside in question is either of these, then it is coded right.

The other two cases are the sorts of thing I have been fixing in pwhex - dissimilar hex sides. I don't think anyone ever did this on purpose - although theoretically one might if one wished certain effects - I cannot imagine that happening. I will look at those two hexes on a map and see if this is fixed by the latest pwhex file or not?

EDIT: The latter two cases were valid issues. Will be corrected in a moment by issuing a new pwhex file. Also a mess at the SE corner of Borneo - very strange hex side coding. It IS rugged country - land and sea - but nevertheless I am at a loss to explain the coding. I more or less agree with the blocked hex sides - but shifted these slightly - so the art makes sense - and redefined one hex as sea. We had a strange case where you could sail across land to a hex otherwise not accessable!

[el cid again]

ORIGINAL: Mifune

"ESO (not released) seems like a lot of fun - a lot more balanced than any previous WITP variant." Cid, so when do the rest of us get to taste that morsel?

Tomorrow. Issuing the 3.31 series at this moment - just here to see if any erratta were detected since I last visited? 3.31 fixes the Russian ship issues for Russian active scenarios - and restores Houston to two - and fixes C-47s pretending to be float planes in two - and a few other eratta I don't remember. I will now focus on RHSEOS - Empire Of the Sun - and I will be posting some threads for comments - this is a wild one - and we have lots of design freedom here.

[CobraAus]

v3.31 posted for all scenarios on download link page

Cobra Aus

[witpqs]

ORIGINAL: el cid again

ORIGINAL: witpqs

In the latest pwhex.dat file:

There is a low capacity ferry between 39,59 and 40,59. Press the R key and the road that represents the ferry only appears in 39,59 (it runs up to the hex side), not into 40,59.

The hexside between 36,59 and 37,59 - Press the F6 key - is red in 36,59 and green in 37,59. The hexside is actually a different color on each side, look closely and you'll see it.

The hexside between 38,59 and 39,59 - Press the F6 key - is white in 38,59 and blue in 39,59.

Hex 40, 59 has code 229 - trail SW and SE. IF the hexside in question is either of these, then it is coded right.

The other two cases are the sorts of thing I have been fixing in pwhex - dissimilar hex sides. I don't think anyone ever did this on purpose - although theoretically one might if one wished certain effects - I cannot imagine that happening. I will look at those two hexes on a map and see if this is fixed by the latest pwhex file or not?

Actually, I tried to say that these three problems are in the latest pwhex.dat (emailed out within the last couple of days). I agree they must be simple data entry errors as I also cannot imagine these kind of entries being done on purpose. Like the rest of the data set, there was simply so incredibly much data and limited ability to proof read or review it.

Regarding this issue:

Hex 40, 59 has code 229 - trail SW and SE. IF the hexside in question is either of these, then it is coded right.

If I understand you correctly (and if I understand the wacky 'compass' directions on the map), the answer is no - it is the left/west hexside of 40,59.

[CobraAus]

V3.32 micro upgrade all scenarios posted on download link page

Cobra Aus

[el cid again]

OK - The "ferry" (trail) to Jolo City on Jolo Island was not coded properly - and so it is now fixed. However - that brings up another subject - where is Zamboanga????? Anyway - there is a new pwhex file fixing this - and adding some more impassable mountains to New Guinea.
I like the fix just done to Borneo's SE corner. This is about right for the geography. This pwhex can be installed any time - it is a very technical update - but Zamboanga - there is a Navy song I can't sing any more about the place (seems "monkeys" do not refer to jungle creatures, which don't exist there - but was a prejorative way to describe people) - but we don't want to lose it. IJN did a neat little landing there - supported by one light tank - facing a company of troops with a single .50 cal - I have a US Army description of the action (if action it can be called)...

I must be blind - it is there - the ferry runs from Zamboanga to Jolo - and it wasn't running - a left over from stock - when they were in different hexes - and somehow I used the wrong file when creating the ferry. Now Zamboanga and Jolo will share supplies, troops, you name it - but not very fast. Just as it should be.

[CobraAus]

V3.33 Pwhex.dat file posted on download link page Sid's coments above relate to this file

Cobra Aus

[TulliusDetritus]

El Cid Again, maybe this has been answered, but I could not find it. What are the "coolies" for? Aesthetics?

And by the way, I am not a native english speaker, but from what I know "coolie" is a derogatory term (just like "jap" or "cowboy" for that matter). Shouldn't you be avoiding it? "Workers" or any other synonymous would be fine? [;)]