@thedog various reasons;
Create an interesting visual difference between the land and sea areas.
Provide more complex land territories for more interesting and granular borders and front lines.
Make choke points on land more important because it's easier to go around enemy armies.
Provide some incentive to split up land armies, rather than keep them all concentrated in a single territory.
Make it easier for ships to defend a coastline.
Cut down on how many sea territories need to be calculated or programmed.
Subcategories
Recent Posts
-
Thanks. I've been rereading through "Pact of Steel 2" and continue to learn what I can. I'm almost 70 now, so learning is taking longer than it did when I was younger.
It does say in "2" that conditions should precede "any" triggers. It also says that meta-conditions need come after the conditions within (as I figured).
The trick is to only move the conditions and not the triggers, at this point. It'll be a long boring process, but I'll have a better understanding of what everything does.
The code I'm revamping is that of the "Path to Victory" game (that I modified) and not actually the "Oztea" game code. I was just using "Oztea" to know which territories were owned by whom in 1939. A few of the names didn't match and the sea zones were different, but I did get that part done.
It was working on the Politics that are leading me to adjust the conditions. I'm also re-formatting the code as I move it, which I had started doing before but never finished.
Last, but not least, I'm also adding more comments (mostly for my own benefit) so that I have a better idea of what each condition is actually checking.
It also looks like a lot of the conditions can be recoded into for-next loops and I will eventually get around to doing that as well. This is especially true with many of the French conditions as there a plethora of them.
So, thank you again.
-
I've been in the process of revamping my version of "Path to Victory" which I had cloned into "Axis Path to Domination" and "Allied Path to Glory". I'm currently in the process of revamping the former into a "1939 Axis Campaign" using "Oztea 1939 Global" as reference.
The issue I'm running into is that there are condition attachments in a variety of places. So, not knowing Java that well (yet), I was wondering if all the conditions can be organized into one area within the XML file and even sorted into Player Order based on the player to whom they are attached?
I'm pretty sure that the same cannot be done with the Trigger attachments as one trigger can affect another.
No doubt one condition can affect another and their order is important, but shouldn't all of Player 1's conditions precede those of Player 2's?
Perhaps it should be all Player 1's Conditions then Triggers, followed by all Player 2's Conditions and then Triggers.
Again, I don't really know - but there should be some way to keep the code better organized.
-
@beelee @wc_sumpton No sorry, I don't have any further insights.