Remember the flowchart I did before?
Maybe also add “attacker retreat” as a full box, with explanation of what is permitted and what is not permitted? Unless this is more detail then you intended with the flow chart.
Thanks for your suggestion.
My aim was to create a game aid to regulate the flow of a combat. The initial motivation was to solve many confusions around submarines’ surprise attack and destroyer’s anti-sub ability. However, I encountered another problem when I was trying to map Step 5. Press Attack or Retreat into my flowchart. Step 5. Press Attack or Retreat (rulebook p.9) has been designed as a conditional loop. Nevertheless, these two conditions are not equal. Condition A is purely a condition, whereas Condition B involves retreat resolving. Therefore, I chose to restructure the flow: splitting Step 5 into mutiple condition checks, combining retreat resolving into Step 6. Since the combat is over once the attacker decides to retreat, there is nothing illogical to merge retreat resolving into Step 6. Conclude Combat. It is the best compromise I can think of.
To accommodate your suggestion, simply detail Step 6. Conclude Combat will do. However, as you mentioned, Step 6 has more things than my original flowchart can catch. As simple as caputring a territory may involve capturing, liberating, capital liberating, capital occupied by enemy, exchanging vitory city token, or achieving/failing national objectives. I will need a new flowchart to list all these possible outcomes.