carrier rules for WWII V3_41

Numetalfan

Hi,

I checked

and this rule:

I could not build a carrier and 2 fighters at once.
I can place the carriers in a SZ next to the factory, but I can't place the 2 new fighters on it.
what is wrong with the properties?

Numetalfan

damn

can someone change vor into for - I can't, stupid mistake

Numetalfan

Tried to place a newly bought fighter on an existing carrier in a Sea zobe next to the factory. That was not possible too.

What has to be changed in the xml?

RogerCooper

@Numetalfan Here are the carrier production properties

   <property name="Produce fighters on carriers" value="true" editable="false">
      <boolean/>
    </property>
    <property name="Produce new fighters on old carriers" value="true" editable="false">
      <boolean/>
    </property>
    <property name="Move existing fighters to new carriers" value="true" editable="false">
      <boolean/>
    </property>
    <property name="Land existing fighters on new carriers" value="true" editable="false">
      <boolean/>
    </property>

Numetalfan

thx alot, but that's how is already is

  <boolean/>
</property>
<property name="LHTR Carrier production rules" value="true" editable="false">
  <boolean/>

Can this be the problem?

What do these Larry Harris tournament rules say? Do they block the normal rules mentioned in the rulebook?

Panther

@Numetalfan I have just tested the wwIIv3-41-map and it works perfectly fine. What exactly does not work when you try it?

2020-9-7-World-War-II-v3-1941.tsvg

Here are the related properties from the xml:

    <property name="Produce fighters on carriers" value="true" editable="false">
      <boolean/>
    </property>
    <property name="Produce new fighters on old carriers" value="true" editable="false">
      <boolean/>
    </property>
    <property name="Move existing fighters to new carriers" value="false" editable="false">
      <boolean/>
    </property>
    <property name="Land existing fighters on new carriers" value="true" editable="false">
      <boolean/>
    </property>
    <property name="LHTR Carrier production rules" value="true" editable="false">
      <boolean/>
    </property>
    <property name="Unit Placement In Enemy Seas" value="true" editable="false">
      <boolean/>
    </property>

Note that the "move-property" is set to "false" and must be set to "false" in this edition.

Numetalfan

I checked those - they are all in my xml.

Even more - I tried the v3-41, there are none of these carrier problems

I checked both xml for differences and found only

in my xml. however, changing it to "false" doesn't change the problem. It must be something else.

Numetalfan

next try:

in the v3

<attachment name="unitAttachment" attachTo="fighter" javaClass="games.strategy.triplea.attachments.UnitAttachment" type="unitType">
<option name="movement" value="4"/>
<option name="carrierCost" value="1"/>
<option name="isAir" value="true"/>
<option name="attack" value="3"/>
<option name="defense" value="4"/>
<option name="canIntercept" value="true"/>
<option name="canEscort" value="true"/>
<option name="airDefense" value="1"/>
<option name="airAttack" value="1"/>
</attachment>

in my xml:

<attachment name="unitAttachment" attachTo="fighter" javaClass="games.strategy.triplea.attachments.UnitAttachment" type="unitType">
<option name="movement" value="4"/>
<option name="carrierCost" value="1"/>
<option name="isAir" value="true"/>
<option name="attack" value="3"/>
<option name="defense" value="4"/>
<option name="canIntercept" value="true"/>
<option name="canEscort" value="true"/>
<option name="airDefense" value="1"/>
<option name="airAttack" value="1"/>
<option name="requiresUnits" value="factory"/>
</attachment>

the difference:
<option name="requiresUnits" value="factory"/>

the idea of this code was to allow to build only in factories, not in other forms of factories, like smaller factories or barracks.

Could it be that this code now forces the fighters only to be build in that country where the factory is located? And not in nearby carriers - in this case this code has to be modified.

beelee

@Panther said in carrier rules for WWII V3_41:

<property name="Move existing fighters to new carriers" value="false" editable="false">
<boolean/>
</property>

try it at false you have true

Numetalfan

*@Panther said in carrier rules for WWII V3_41:

<property name="Move existing fighters to new carriers" value="false" editable="false">
<boolean/>
</property>

try it at false you have true*

That is already corrected - it is not the reason.

</property>
<property name="Unit Placement Restrictions" value="true" editable="false">
<boolean/>

what is this for? what are the effects?

Panther

@Numetalfan A good source for learning about the XML-content is:

https://forums.triplea-game.org/topic/729/xml-option-browser

created by @Mahks.

It directs to

http://www.starlords3k.com/XOB.html

where you can browse for the respective property and option.

Numetalfan

wow,

very cool link - thx alot Panther!

Numetalfan

topic closed.

same spooky thing like my connection problems topic.

once I start a new game there are no more carrier problems,
if I load the saved game instead, all problems show up.

strange but true.

THX to everyone who had useful advice.

topic closed.

ff03k64

I think changes to xml files do not effect save games. I think it has to be new games for the changes to take effect.

wc_sumpton

@Numetalfan

The saved game carries a copy of the xml used to create the game. Any changes made to the xml will not show in a saved game. To test changes you have to always start a new game.

Cheers...