Receiveing (Gameplay) Sequence errors / issues

Stohrm

I'm currently working on my own WW2 1940 (Axis) scenario via modifying the (world_war_ii_global-master) G40CanadianMod. I have successfully moved all the Axis players (Germans; Italians; Japanese) to the top of the "playerList" and placed their respective "steps" in order as well. Now I'd like to put the Neutral_Axis next followed by the Allies in alphabetical order (except for UK_Pacific which will need remain interlaced with the British for now).

The problem I'm running into is with where one puts the following code:

    <stepProperty name="skipPosting" value="true"/>
  </step>

and such. It's currently following all the Allies' EndTurn steps except for the Russians, the UK_Pacific and the French. The French (still currently the last) is followed by:
<stepProperty name="turnSummaryPlayers" value="ANZAC:French"/>
</step>
<step name="endRoundStep" delegate="endRound"/>
</sequence>
and the UK_Pacific's end turn is followed by
<stepProperty name="turnSummaryPlayers" value="Americans:Chinese:British:UK_Pacific"/>
</step>

So, what are the rules / guidelines regarding these items? This is strictly a local game and it's just me vs the computer; but one never knows. If I ever finish it...

Stohrm

Never mind; as I think I discovered the error of my ways. I was tired and overlooked the difference between the /> 's and the / 's.

Even so, I would like to learn more about coding the sequencing; if anyone has tips and/or suggestions.

Cernel

@Stohrm I cannot understand when and what errors you are getting from anything you are describing.

As long as the "skipPosting" step property goes, that is only for PBEM and PBF, and avoids the other participants getting the turn report. This is properly used only for players that are irrelevant enough or that are going to have their turn reported after some other step, maybe of another player.

After having done the changes you wish, you should PBEM your game, to test it.

For example, from WW2v3-1941:

      <!-- Chinese/Americans Game Sequence -->
      <step name="americanTech" delegate="tech" player="Americans"/>
      <step name="americanTechActivation" delegate="tech_activation" player="Americans"/>
      <step name="americanPurchase" delegate="purchase" player="Americans"/>
      <step name="chinesePurchase" delegate="purchaseNoPU" player="Chinese"/>
      <step name="americanCombatMove" delegate="move" player="Americans"/>
      <step name="americanBattle" delegate="battle" player="Americans"/>
      <step name="americanNonCombatMove" delegate="move" player="Americans" display="Non Combat Move"/>
      <step name="chineseCombatMove" delegate="move" player="Chinese"/>
      <step name="chineseBattle" delegate="battle" player="Chinese"/>
      <step name="chineseNonCombatMove" delegate="move" player="Chinese" display="Non Combat Move"/>
      <step name="americanPlace" delegate="place" player="Americans"/>
      <step name="chinesePlace" delegate="place" player="Chinese"/>
      <step name="chineseEndTurn" delegate="endTurnNoPU" player="Chinese">
        <stepProperty name="skipPosting" value="true"/>
      </step>
      <step name="americanEndTurn" delegate="endTurn" player="Americans">
        <stepProperty name="turnSummaryPlayers" value="Americans:Chinese"/>
      </step>

beelee

@Stohrm said in Receiveing (Gameplay) Sequence errors / issues:

Never mind; as I think I discovered the error of my ways. I was tired and overlooked the difference between the /> 's and the / 's.

Even so, I would like to learn more about coding the sequencing; if anyone has tips and/or suggestions.

I assume you're already aware of "Pact of Steel 2" ? It's xml explains how the xml works. Just in case

pact_of_steel_2.xml

Stohrm

@beelee said in Receiveing (Gameplay) Sequence errors / issues:

I assume you're already aware of "Pact of Steel 2" ? It's xml explains how the xml works. Just in case

pact_of_steel_2.xml

Yes. As I said, I was tired and had missed that simply cutting and pasting doesn't always work properly. Thus there were /> 's where there should only have been > 's and even after I discovered and corrected those (and had it working), I had left out an entire </step> (due to a bad cut & paste, later).

It IS working now and I'm on to the other changes. But, Thank you.

beelee

@Stohrm
Right on. I've made many a blurry eyed mistake myself