RHS 3.3 Series Released (Russian ships will refuel where they exist)

[el cid again]

After extensive testing, RHS has divided into two file sets:

Russian Passive Files: RHSCVO and RHSRPO (a version of BBO) have NO Russian ships, normal command and base definitions, and work exactly as stock Scenario 15 does.

Russian Active Files: RHSBBO, RHSRAO (a version of CVO), and RHSPPO (a version of BBO with lots of political points) work with a gimmick in place to permit Allied ships to refuel in Russian ports - note the word ALLIED ships - not just Russian ships. These files also have Russian ships in them. These files may have problems with AI controlled Allies or Allied subs - because the AI may think the Russian ports are safe to use - when they may not be. So I do not recommend them for AI controlled Allies - not much of a loss since Joe thinks the AI cannot control the Allies in any case. But to the degree it can - it may be worse with these files.
Fair warning.

[el cid again]

The testing has failed. It has shown some promise - so I will try again.
EDIT: This is an out of date post: It took correction of port command as well as port flag to fix.


BUT in the meanwhile I will convert RHSCVO (and the RHSRPO variation of RHSBBO) to a form WITHOUT Russian ships. These scenarios will be very like scenario 15 - CVO simply a translation of it with different planes and ships - RPO a variation with more original thinking in ship production planning - or like CHS. These scenarios will NOT attempt to make Russian ships work - and they will be issued in the next hour - at 3.3 level.

RHSBBO, RHSRAO, RHSPPO and soon RHSEOS will attempt to solve the Russian ship refueling issue:

I have them TRYING to refuel now: the option is present instead of greyed out; the ships expend ops points executing the refueling - they just don't get any fuel. But I have a theory...

[el cid again]

Uploading now to key list. Cobra will post presently. There are now 5 released RHS scenarios - and no unresolved technical issues - except one involving pwhex file for two hex sides. [The map is full of such issues - and it may be our pwhex file has fewer than any other - but it will never have none. Nor is it always clear how each hex should be coded? But comments are welcome and pwhex revisions will occur from time to time as better interpretations become obvious. Pwhex revisions have no effect on scenario files - and can occur in the middle of any game.]

pwhex revision 3.2 releasing now fixing these issues. Similarly, some eratta are fixed in 3.2 level micro updates. Mostly making Japanese ships appear that otherwise did not because of bogus sink dates. Seems if you copy a ship with ANY sink date the editor ALWAYS writes a false field! Be warned if you mod - check the sink date ANY time you copy a ship to a different file.