1. Home
  2. Development
Log in to post
Load new posts
  • LaFayetteL

    Unit Scroller Issues & RFC on Changes

    23
    1 Votes
    23 Posts
    6k Views
    TheDogT
    @LaFayette Before I was guessing what happened, but here is a little bit more detail; where letters = Territories and numbers = units in those territories. D2 = Territory "D" with 2 units in it. A1, B1, C1, D2, E2, F1, G1 Say I move the 1st unit in E2, it should return to E2, but it actually goes to D2. If I move the 2nd unit in E2, it should return to F1, but it actually goes to G1.
  • S

    A little help setting up eclipse

    4
    1 Votes
    4 Posts
    926 Views
    LaFayetteL
    @squid_daddy Please take the liberty to update the docs to get them more up to date, fill in any missing details, and generally make them more useful for someone getting started
  • S

    pacific and europe triggered victory

    1
    1 Votes
    1 Posts
    550 Views
    No one has replied
  • LaFayetteL

    Calling Graphic Designers! Need a 'Star' Graphic For Map Quality Rating

    12
    0 Votes
    12 Posts
    2k Views
    LaFayetteL
    @hepps I would love for the ratings to be sorted out and refined. There is an open need for Map Admins to go through and do curation of maps, volunteers needed: https://forums.triplea-game.org/topic/2707/map-curation-rating-maps-categories/1
  • LaFayetteL

    Lock Map Icon on Map

    9
    2
    0 Votes
    9 Posts
    2k Views
    ubernautU
    @lafayette well i think having some kind of directional arrows behind the lock or maybe a map grid under the lock 3d style would have the same effect.
  • RogerCooperR

    Downloaded Maps

    Moved
    7
    0 Votes
    7 Posts
    1k Views
    LaFayetteL
    FWIW, the places that would need a fix are largely in code that will be deleted pretty imminently. That is why the fixes are in queue.
  • TheDogT

    Warning for those upgrading to v2.6+

    1
    1 Votes
    1 Posts
    558 Views
    No one has replied
  • LaFayetteL

    RFC: merging skins with maps

    17
    2 Votes
    17 Posts
    2k Views
    C
    @LaFayette The alternative skin for 270BC is an example of changing also the units. There may be others. Here you can find a map-skin for RSoC that is actually about making the map bigger: https://github.com/Cernelius/red_sun_over_china-big_skin The current map-skin feature allows changing everything in the skin, and that is good. What is not very good is that it obliges you changing everything, so forcing duplication if you don't actually want to change everything. It is true that most map-skins are only about changing the map details, but I think this is beside the point (Of course, some things are more used or useful than others.).
  • C

    TripleA Rules Sets

    15
    1 Votes
    15 Posts
    3k Views
    LaFayetteL
    @LaFayette said in TripleA Rules Sets: What would be ideal is to have a table describing different behaviors by rule set. We are actually on our way there. We have example maps that follow each rule set, all we need to do is to start teasing apart the behaviors that are different and then answer for each map, "does this follow that behavior, yes or no?" If we find that some rule sets are only very slightly different, simpler is better. The 'v3' moniker will be difficult to drop, if we can keep it simple and say "old edition", "revised edition" and "new edition", it could be easier to adopt. At this point though, without knowing what the rule sets actually are, it seems to be a first priority to know which rules are in each rule set before we do much of anything else.
  • LaFayetteL

    Storing Maps as Folders only rather than as either Zip or Folder

    10
    4 Votes
    10 Posts
    2k Views
    djabwanaD
    @Cernel As we unzip a file, we will be doing a lot of checks (are all the required folders there? is there a centers.txt, etc.?) and as part of that process, we could enforce a casing convention. I have a tool that fixes capitalization. When I got image assets from @GenerationKILL sometimes the casing was a bit off, so I would just run this tool and it would conform every unit to a convention like this: Unit-Name.png regardless of the OS and regardless of the original naming. We could implement a similar normalization process at the map parsing level (though it might be hard to get map makers on the same page about which casing convention should be used). https://github.com/jdimeo/triplea-map-tools/blob/master/src/main/java/jdimeo/triplea/util/FixFileNames.java
  • T

    GameData.acquireReadLock usage?

    3
    0 Votes
    3 Posts
    932 Views
    T
    So, would you be ok with removing some locks if it can be shown that the data is actually read only? I'm currently looking at ResourceList which is what GameData#getResourceList returns. The class has only one setter and it is only called during the game parse process and a test method. The data that ResourceList stores is a map of Strings and Resources. And Resource is a value object. ResourceList doesn't appear to need any sort of read lock since I don't see any way for it to change. If I see locks around GameData#getResourceList, can I just remove them? Would you like me to tag Resource and ResourceList somehow (such as @Value) to indicate that they are read-only objects?
  • LaFayetteL

    Replace Console Logging with a File

    25
    2 Votes
    25 Posts
    5k Views
    TheDogT
    @LaFayette Dont forget to add triplea.log to the list of files to uninstall.
  • aardvarkpepperA

    Questions from a know-nothing beginning programmer/developer

    8
    0 Votes
    8 Posts
    2k Views
    LaFayetteL
    That said, is there a particular reason (other than a chunk of code not really necessary to functionality) that save game files don't work that way? Java serialization was once popular, it was an initial design decision to use it, it was somewhat easy. We would actually like for save games to work more like you have described. It's a very large project, that is all, and we have a large backlog of small and large projects that we are working on and collectively there is not that much development labor available. Re: performance requirements These are the wrong things to focus on. First focus on functionality, what are you going to built? What value will it provide, how will it be used? You need a good product for anything else to matter. Then I'd encourage to stop worrying about specs. Simple and well done architectures are fast and perform well. Simple code is usually fast code. Once you have a reasonable design in place and functioning, then you can start analyzing where the performance bottlenecks are and where to go to optimize. It's a ways to get to that point, and once you are there the process is to measure, change, repeat. Humans have generally very bad intuitions for where performance problems will arise. It's also easy to try and fix all performance problems as optimization problems when they are really design problems. One can look at a block of code and wonder "how can I make this faster", and sometimes the right answer is, "how can I avoid needing to execute this in the first place?" That is why keeping things simple and working is very important, it lets you reason about what your code is doing. For example TripleA does a lot of calculations twice, why? Because there are 15 layers of call indirection separating the two which creates several thousands of lines of code in between the duplication. Bottom line OUr time is short in just about every way imaginable. I'm pretty sure and somewhat regrettfully going to say, if you want something that interoperates with TripleA, it's potentially one of and likely all of: untractable and/or a truly huge project We have wanted to for example to allow TripleA to run on web browsers, or phones. That project is probably 3-8 years away from being completed if it were started today.
  • T

    Combine casualty selection dialogs?

    2
    2
    1 Votes
    2 Posts
    931 Views
    TheDogT
    Its a good idea, I like it.
  • T

    AA Auto Casualty documentation?

    1
    1 Votes
    1 Posts
    780 Views
    No one has replied
  • T

    AA and targets with multiple hit points, how many dice?

    8
    0 Votes
    8 Posts
    2k Views
    LaFayetteL
    I think you may have to look at which maps have the combination of properties set to see how it is used. I can imagine a few different variations of how such behavior would be used. Generally, if the intent were to be able to shoot down a multi-hit-point air unit, it would make more sense to me for the AA to do more than 1 damage.
  • T

    When should support be allocated?

    10
    0 Votes
    10 Posts
    2k Views
    LaFayetteL
    Sounds right, though I think this is a simpler way to think about it: before a unit rolls, it looks to see if there is an available support, if so, it consumes that support.
  • T

    Why does all aa attack values must divide into attackAAmaxDieSides?

    5
    0 Votes
    5 Posts
    942 Views
    T
    @alkexr , thanks for those forum posts. It does look like this warning is no longer valid.
  • N

    I would like to start helping out with tripleadevelopment but don't know where to start

    6
    2 Votes
    6 Posts
    2k Views
    N
    @LaFayette said in I would like to start helping out with tripleadevelopment but don't know where to start: Are you familiar with doing feature branches in git? Were you able to compile and run the game from scratch? No to both of those. I guess I need help.
  • MirkoBrunerM

    Implementing UI Visual

    Moved
    32
    1 Votes
    32 Posts
    10k Views
    MirkoBrunerM
    @RoiEX I have read your specs, Issue seems to be closed at least for now. How do we proceed from that? Any Idea? I have already my questions about your navigations and other annotations. Regards @RoiEX .

Recent Posts

  • RogerCooperR
    RogerCooper

    @Kindwind On round 3 the Germans spent more money on purchases than they had.

    read more
  • KindwindK
    Kindwind

    @RogerCooper Some. I moved over to a local LLM using Fable. Here is a log file. I ditched my rust engine. Everything is in working order now I think.

    ========================================================================
    TRIPLEA-LLM GAME STATEMENT (both sides where logged)
    Account: ? side vs ? model ?
    Game id: eval-56cb5c6b-3329-4682-8126-455bc6fc53da
    Opened: 2026-07-22 18:14 Rounds: ? Duration: ?s
    Result: winners = none (round cap)

    ROUND 1 ------------------------------------- RUSSIANS (ALLIES / WeakAi)
    BALANCE BROUGHT FORWARD ...................................... PU 24
    PURCHASE 3 x infantry .......................................... - 9
    PURCHASE 2 x artillery ......................................... - 8
    PURCHASE 1 x armour ............................................ - 5
    BALANCE AFTER PURCHASE ....................................... PU 2
    COMBAT Karelia S.S.R. -> West Russia (1 x fighter, 3 x infantry) << ATTACK
    COMBAT Archangel -> West Russia (3 x infantry, 1 x armour) << ATTACK
    COMBAT Caucasus -> West Russia (3 x infantry, 1 x artillery, 1 x armour) << ATTACK
    COMBAT Russia -> West Russia (1 x fighter, 3 x infantry, 1 x artillery, 2 x armour) << ATTACK
    NONCOM West Russia -> Archangel (2 x fighter)
    NONCOM Soviet Far East -> Yakut S.S.R. (2 x infantry)
    NONCOM Novosibirsk -> Kazakh S.S.R. (2 x infantry)
    NONCOM Yakut S.S.R. -> Novosibirsk (2 x infantry)
    NONCOM Kazakh S.S.R. -> Caucasus (2 x infantry)
    NONCOM Evenki National Okrug -> Russia (2 x infantry)
    NONCOM Buryatia S.S.R. -> Yakut S.S.R. (2 x infantry)
    PLACE Russia: 3 x infantry, 2 x artillery, 1 x armour

    ROUND 1 ----------------------------------- GERMANS (AXIS / llm-triplea)
    BALANCE BROUGHT FORWARD ...................................... PU 40
    PURCHASE 7 x infantry .......................................... - 21
    PURCHASE 3 x armour ............................................ - 15
    BALANCE AFTER PURCHASE ....................................... PU 4
    COMBAT Eastern Europe -> Belorussia (1 x fighter, 2 x infantry, 1 x armour)
    COMBAT Germany -> Belorussia (1 x bomber, 1 x fighter, 1 x armour)
    COMBAT Eastern Europe -> West Russia (1 x fighter, 1 x infantry, 1 x armour) << ATTACK
    COMBAT Norway -> West Russia (1 x fighter) via Norway > Karelia S.S.R. > West Russia << ATTACK
    COMBAT Germany -> West Russia (2 x infantry, 1 x armour) << ATTACK
    COMBAT Southern Europe -> Ukraine S.S.R. (2 x infantry, 1 x artillery, 1 x armour)
    NONCOM Germany -> Western Europe (1 x infantry)
    NONCOM Southern Europe -> Western Europe (1 x infantry)
    NONCOM 5 Sea Zone -> 7 Sea Zone (2 x submarine, 1 x transport, 1 x destroyer)
    NONCOM Germany -> 7 Sea Zone (1 x infantry) << LOAD
    NONCOM 7 Sea Zone -> Western Europe (1 x infantry) << UNLOAD
    NONCOM Southern Europe -> 7 Sea Zone (1 x infantry) << LOAD
    NONCOM 7 Sea Zone -> Western Europe (1 x infantry) << UNLOAD
    NONCOM Germany -> Ukraine S.S.R. (1 x armour) via Germany > Eastern Europe > Ukraine S.S.R.
    NONCOM Belorussia -> Ukraine S.S.R. (1 x infantry)
    NONCOM Ukraine S.S.R. -> Belorussia (1 x fighter)
    NONCOM Western Europe -> 7 Sea Zone (1 x fighter) << LOAD
    NONCOM 7 Sea Zone -> 6 Sea Zone (1 x fighter)
    NONCOM 6 Sea Zone -> 5 Sea Zone (1 x fighter)
    NONCOM 5 Sea Zone -> Eastern Europe (1 x fighter) << UNLOAD
    NONCOM Belorussia -> Eastern Europe (1 x bomber, 1 x infantry)
    NONCOM Germany -> Eastern Europe (1 x infantry)
    NONCOM Ukraine S.S.R. -> Eastern Europe (1 x fighter)
    NONCOM Ukraine S.S.R. -> Belorussia (1 x fighter, 1 x infantry, 1 x artillery)
    PLACE Germany: 1 x armour
    PLACE Germany: 1 x armour
    PLACE Germany: 1 x armour
    PLACE Germany: 1 x armour
    PLACE Southern Europe: 1 x armour
    PLACE Southern Europe: 1 x armour
    PLACE Southern Europe: 1 x armour
    PLACE Southern Europe: 1 x infantry

    ROUND 1 -------------------------------------- BRITISH (ALLIES / WeakAi)
    BALANCE BROUGHT FORWARD ...................................... PU 30
    PURCHASE 3 x infantry .......................................... - 9
    PURCHASE 2 x artillery ......................................... - 8
    PURCHASE 1 x armour ............................................ - 5
    PURCHASE 1 x transport ......................................... - 8
    BALANCE AFTER PURCHASE ....................................... PU 0
    COMBAT United Kingdom -> 2 Sea Zone (2 x infantry) << LOAD
    COMBAT 2 Sea Zone -> 6 Sea Zone (1 x battleship, 1 x transport, 2 x infantry) via 2 Sea Zone > 3 Sea Zone > 6 Sea Zone
    COMBAT United Kingdom -> Germany (1 x bomber) via United Kingdom > 6 Sea Zone > 5 Sea Zone > Germany << ATTACK
    COMBAT Anglo Egypt -> Libya (1 x fighter, 1 x infantry, 1 x armour) << ATTACK
    NONCOM Germany -> Karelia S.S.R. (1 x bomber) via Germany > 5 Sea Zone > Karelia S.S.R.
    NONCOM Libya -> Anglo Egypt (1 x fighter)
    NONCOM Union of South Africa -> Kenya (1 x infantry)
    NONCOM Persia -> Caucasus (1 x infantry)
    NONCOM India -> Persia (3 x infantry)
    NONCOM Trans-Jordan -> Persia (1 x infantry)
    NONCOM 1 Sea Zone -> 3 Sea Zone (1 x transport) via 1 Sea Zone > 2 Sea Zone > 3 Sea Zone
    NONCOM 15 Sea Zone -> 33 Sea Zone (1 x destroyer) via 15 Sea Zone > 34 Sea Zone > 33 Sea Zone
    NONCOM 13 Sea Zone -> 9 Sea Zone (1 x battleship) via 13 Sea Zone > 12 Sea Zone > 9 Sea Zone
    NONCOM 35 Sea Zone -> 33 Sea Zone (1 x carrier, 1 x fighter, 1 x transport, 1 x destroyer) via 35 Sea Zone > 32 Sea Zone > 33 Sea Zone
    NONCOM 40 Sea Zone -> 42 Sea Zone (1 x submarine, 1 x transport) via 40 Sea Zone > 41 Sea Zone > 42 Sea Zone
    NONCOM United Kingdom -> 3 Sea Zone (1 x artillery) << LOAD
    PLACE 6 Sea Zone: 1 x transport
    PLACE United Kingdom: 3 x infantry, 2 x artillery, 1 x armour

    ROUND 1 ---------------------------------- JAPANESE (AXIS / llm-triplea)
    BALANCE BROUGHT FORWARD ...................................... PU 30
    PURCHASE 2 x infantry .......................................... - 6
    PURCHASE 1 x armour ............................................ - 5
    PURCHASE 1 x transport ......................................... - 8
    BALANCE AFTER PURCHASE ....................................... PU 11
    COMBAT Japan -> 60 Sea Zone (2 x infantry) << LOAD
    COMBAT 60 Sea Zone -> 59 Sea Zone (1 x transport, 2 x infantry)
    COMBAT 59 Sea Zone -> China (2 x infantry) << AMPHIBIOUS ASSAULT
    NONCOM 50 Sea Zone -> 59 Sea Zone (1 x carrier, 1 x fighter)
    NONCOM 59 Sea Zone -> 60 Sea Zone (1 x transport, 2 x infantry)
    NONCOM 50 Sea Zone -> 60 Sea Zone (1 x destroyer)
    NONCOM Japan -> 60 Sea Zone (1 x fighter) << LOAD
    NONCOM 59 Sea Zone -> 60 Sea Zone (1 x transport)
    NONCOM Japan -> 60 Sea Zone (2 x infantry) << LOAD
    NONCOM 60 Sea Zone -> 59 Sea Zone (1 x transport, 2 x infantry)
    NONCOM 59 Sea Zone -> 60 Sea Zone (1 x transport, 2 x infantry)
    NONCOM 60 Sea Zone -> 59 Sea Zone (1 x transport)
    NONCOM 59 Sea Zone -> 60 Sea Zone (1 x transport, 2 x infantry)
    NONCOM 60 Sea Zone -> 59 Sea Zone (1 x transport, 2 x infantry)
    NONCOM Japan -> 59 Sea Zone (1 x fighter) << LOAD
    NONCOM 59 Sea Zone -> 60 Sea Zone (1 x transport, 2 x infantry)
    NONCOM 60 Sea Zone -> 61 Sea Zone (1 x transport, 2 x infantry)
    NONCOM 61 Sea Zone -> Manchuria (2 x infantry) << UNLOAD
    NONCOM China -> Manchuria (2 x fighter)
    NONCOM 50 Sea Zone -> 49 Sea Zone (1 x carrier, 1 x fighter, 1 x destroyer)
    NONCOM 49 Sea Zone -> 60 Sea Zone (1 x carrier, 1 x fighter, 1 x destroyer)
    PLACE French Indochina: 1 x infantry
    PLACE China: 1 x transport
    PLACE Manchuria: 1 x infantry

    ROUND 1 ------------------------------------ AMERICANS (ALLIES / WeakAi)
    BALANCE BROUGHT FORWARD ...................................... PU 42
    PURCHASE 4 x infantry .......................................... - 12
    PURCHASE 2 x armour ............................................ - 10
    PURCHASE 2 x transport ......................................... - 16
    PURCHASE 1 x artillery ......................................... - 4
    BALANCE AFTER PURCHASE ....................................... PU 0
    COMBAT Eastern United States -> 10 Sea Zone (2 x infantry, 1 x artillery, 1 x armour) << LOAD
    COMBAT 10 Sea Zone -> 12 Sea Zone (2 x transport, 2 x infantry, 1 x destroyer, 1 x artillery, 1 x armour) via 10 Sea Zone > 11 Sea Zone > 12 Sea Zone
    COMBAT 12 Sea Zone -> Algeria (2 x infantry, 1 x artillery, 1 x armour) << AMPHIBIOUS ASSAULT
    NONCOM Sinkiang -> Kazakh S.S.R. (2 x infantry)
    NONCOM Central United States -> Mexico (2 x infantry)
    NONCOM 52 Sea Zone -> 54 Sea Zone (1 x carrier, 1 x submarine, 1 x fighter) via 52 Sea Zone > 55 Sea Zone > 54 Sea Zone
    NONCOM 55 Sea Zone -> 20 Sea Zone (1 x battleship, 1 x transport) via 55 Sea Zone > 54 Sea Zone > 20 Sea Zone
    NONCOM 20 Sea Zone -> 10 Sea Zone (1 x destroyer) via 20 Sea Zone > 19 Sea Zone > 10 Sea Zone
    PLACE 10 Sea Zone: 2 x transport
    PLACE Eastern United States: 4 x infantry, 1 x artillery, 2 x armour

    ROUND 2 ------------------------------------- RUSSIANS (ALLIES / WeakAi)
    BALANCE BROUGHT FORWARD ...................................... PU 28
    PURCHASE 3 x infantry .......................................... - 9
    PURCHASE 2 x artillery ......................................... - 8
    PURCHASE 2 x armour ............................................ - 10
    BALANCE AFTER PURCHASE ....................................... PU 1
    COMBAT West Russia -> Ukraine S.S.R. (9 x infantry, 2 x artillery, 2 x armour) << ATTACK
    COMBAT Caucasus -> Ukraine S.S.R. (2 x infantry) << ATTACK
    NONCOM Novosibirsk -> Kazakh S.S.R. (2 x infantry)
    NONCOM Yakut S.S.R. -> Novosibirsk (4 x infantry)
    NONCOM Kazakh S.S.R. -> Caucasus (2 x infantry)
    NONCOM Russia -> West Russia (5 x infantry, 2 x artillery, 1 x armour)
    PLACE Russia: 3 x infantry, 2 x artillery, 2 x armour

    ROUND 2 ----------------------------------- GERMANS (AXIS / llm-triplea)
    BALANCE BROUGHT FORWARD ...................................... PU 37
    PURCHASE 7 x infantry .......................................... - 21
    PURCHASE 2 x armour ............................................ - 10
    BALANCE AFTER PURCHASE ....................................... PU 6
    COMBAT Belorussia -> West Russia (2 x infantry, 1 x armour) << ATTACK
    COMBAT Germany -> West Russia (1 x armour) via Germany > Karelia S.S.R. > West Russia << ATTACK
    COMBAT Eastern Europe -> West Russia (1 x bomber, 1 x fighter) via Eastern Europe > Belorussia > West Russia << ATTACK
    COMBAT Balkans -> West Russia (1 x fighter) via Balkans > Ukraine S.S.R. > West Russia << ATTACK
    COMBAT Belorussia -> Ukraine S.S.R. (1 x fighter, 1 x infantry, 1 x armour) << ATTACK
    COMBAT Germany -> Ukraine S.S.R. (1 x armour) via Germany > Eastern Europe > Ukraine S.S.R. << ATTACK
    COMBAT Southern Europe -> Ukraine S.S.R. (2 x infantry, 1 x artillery) << ATTACK
    COMBAT Belorussia -> Karelia S.S.R. (2 x infantry) << ATTACK
    COMBAT Eastern Europe -> Karelia S.S.R. (1 x infantry, 1 x artillery) << ATTACK
    COMBAT Germany -> Karelia S.S.R. (1 x infantry) << ATTACK
    COMBAT Balkans -> Karelia S.S.R. (2 x infantry) via Balkans > Eastern Europe > Karelia S.S.R. << ATTACK
    COMBAT Southern Europe -> Germany (3 x infantry)
    NONCOM Germany -> Eastern Europe (2 x infantry, 2 x armour)
    NONCOM Southern Europe -> Balkans (2 x infantry, 1 x artillery)
    NONCOM Western Europe -> Southern Europe (4 x infantry, 2 x armour)
    NONCOM West Russia -> Belorussia (2 x fighter)
    NONCOM Ukraine S.S.R. -> Belorussia (1 x fighter)
    NONCOM 7 Sea Zone -> 8 Sea Zone (2 x submarine, 1 x transport, 1 x destroyer)
    NONCOM 8 Sea Zone -> 7 Sea Zone (2 x submarine, 1 x transport, 1 x destroyer)
    NONCOM 7 Sea Zone -> 6 Sea Zone (2 x submarine, 1 x transport, 1 x destroyer)
    PLACE Germany: 1 x infantry
    PLACE Southern Europe: 1 x armour
    PLACE Germany: 1 x infantry
    PLACE Southern Europe: 1 x infantry
    PLACE Germany: 1 x infantry
    PLACE Southern Europe: 1 x infantry
    PLACE Southern Europe: 1 x infantry
    PLACE Germany: 1 x infantry

    ROUND 2 -------------------------------------- BRITISH (ALLIES / WeakAi)
    BALANCE BROUGHT FORWARD ...................................... PU 31
    PURCHASE 3 x infantry .......................................... - 9
    PURCHASE 1 x armour ............................................ - 5
    PURCHASE 2 x transport ......................................... - 16
    BALANCE AFTER PURCHASE ....................................... PU 1
    COMBAT United Kingdom -> 6 Sea Zone (1 x infantry, 1 x armour) << LOAD
    COMBAT United Kingdom -> 3 Sea Zone (1 x infantry) << LOAD
    COMBAT 6 Sea Zone -> 2 Sea Zone (1 x transport, 2 x infantry) via 6 Sea Zone > 3 Sea Zone > 2 Sea Zone
    COMBAT 6 Sea Zone -> Western Europe (1 x infantry, 1 x armour) << AMPHIBIOUS ASSAULT
    COMBAT 9 Sea Zone -> 8 Sea Zone (1 x battleship)
    NONCOM Kenya -> Belgian Congo (1 x infantry)
    NONCOM Persia -> Caucasus (4 x infantry)
    NONCOM Caucasus -> Ukraine S.S.R. (1 x infantry)
    NONCOM Libya -> Anglo Egypt (1 x infantry, 1 x armour)
    NONCOM 42 Sea Zone -> 22 Sea Zone (1 x submarine, 1 x transport) via 42 Sea Zone > 25 Sea Zone > 22 Sea Zone
    NONCOM 3 Sea Zone -> 6 Sea Zone (1 x transport, 1 x infantry, 1 x artillery)
    NONCOM 33 Sea Zone -> 27 Sea Zone (1 x carrier, 1 x fighter, 1 x transport, 2 x destroyer) via 33 Sea Zone > 28 Sea Zone > 27 Sea Zone
    PLACE 6 Sea Zone: 2 x transport
    PLACE United Kingdom: 3 x infantry, 1 x armour

    ROUND 2 ---------------------------------- JAPANESE (AXIS / llm-triplea)
    BALANCE BROUGHT FORWARD ...................................... PU 43
    PURCHASE 1 x transport ......................................... - 8
    PURCHASE 1 x infantry .......................................... - 3
    PURCHASE 1 x armour ............................................ - 5
    BALANCE AFTER PURCHASE ....................................... PU 27
    COMBAT Japan -> 61 Sea Zone (2 x infantry, 1 x artillery, 2 x armour) << LOAD
    COMBAT 61 Sea Zone -> 60 Sea Zone (1 x transport, 2 x infantry, 1 x artillery, 2 x armour)
    COMBAT 60 Sea Zone -> Manchuria (2 x infantry, 1 x artillery, 2 x armour) << UNLOAD
    NONCOM China -> French Indochina (2 x infantry)
    NONCOM Manchuria -> French Indochina (2 x fighter) via Manchuria > China > French Indochina
    NONCOM 59 Sea Zone -> 36 Sea Zone (1 x carrier, 2 x fighter, 2 x transport, 4 x infantry) via 59 Sea Zone > 60 Sea Zone > 36 Sea Zone
    NONCOM 51 Sea Zone -> 36 Sea Zone (2 x infantry) via 51 Sea Zone > 50 Sea Zone > 49 Sea Zone > 36 Sea Zone
    NONCOM Japan -> 51 Sea Zone (2 x armour) << LOAD
    NONCOM 51 Sea Zone -> Wake Island (2 x armour) << UNLOAD
    PLACE China: 1 x infantry
    PLACE French Indochina: 1 x infantry
    PLACE Kwantung: 1 x infantry
    PLACE Manchuria: 1 x infantry
    PLACE 60 Sea Zone: 1 x transport
    PLACE 60 Sea Zone: 1 x transport

    ROUND 2 ------------------------------------ AMERICANS (ALLIES / WeakAi)
    BALANCE BROUGHT FORWARD ...................................... PU 41
    PURCHASE 4 x infantry .......................................... - 12
    PURCHASE 1 x armour ............................................ - 5
    PURCHASE 2 x artillery ......................................... - 8
    PURCHASE 2 x transport ......................................... - 16
    BALANCE AFTER PURCHASE ....................................... PU 0
    COMBAT Eastern United States -> 10 Sea Zone (3 x infantry, 1 x artillery) << LOAD
    COMBAT 10 Sea Zone -> 12 Sea Zone (2 x transport, 3 x infantry, 1 x destroyer, 1 x artillery) via 10 Sea Zone > 11 Sea Zone > 12 Sea Zone
    NONCOM Kazakh S.S.R. -> Caucasus (2 x infantry)
    NONCOM Algeria -> Libya (2 x infantry, 1 x artillery, 1 x armour)
    NONCOM 54 Sea Zone -> 19 Sea Zone (1 x carrier, 1 x submarine, 1 x fighter) via 54 Sea Zone > 20 Sea Zone > 19 Sea Zone
    NONCOM 12 Sea Zone -> 10 Sea Zone (2 x transport, 1 x destroyer) via 12 Sea Zone > 11 Sea Zone > 10 Sea Zone
    NONCOM 20 Sea Zone -> 10 Sea Zone (1 x battleship, 1 x transport) via 20 Sea Zone > 19 Sea Zone > 10 Sea Zone
    NONCOM Eastern United States -> 10 Sea Zone (1 x infantry, 2 x armour) << LOAD
    NONCOM 12 Sea Zone -> Algeria (3 x infantry, 1 x artillery) << UNLOAD
    PLACE 10 Sea Zone: 2 x transport
    PLACE Eastern United States: 4 x infantry, 2 x artillery, 1 x armour

    ROUND 3 ------------------------------------- RUSSIANS (ALLIES / WeakAi)
    BALANCE BROUGHT FORWARD ...................................... PU 30
    PURCHASE 1 x infantry .......................................... - 3
    PURCHASE 4 x artillery ......................................... - 16
    PURCHASE 2 x armour ............................................ - 10
    BALANCE AFTER PURCHASE ....................................... PU 1
    COMBAT Ukraine S.S.R. -> Eastern Europe (9 x infantry, 2 x artillery, 2 x armour) << ATTACK
    COMBAT West Russia -> Karelia S.S.R. (2 x infantry, 2 x artillery, 2 x armour) << ATTACK
    NONCOM Novosibirsk -> Kazakh S.S.R. (4 x infantry)
    NONCOM Kazakh S.S.R. -> Caucasus (2 x infantry)
    NONCOM Caucasus -> Ukraine S.S.R. (2 x infantry)
    NONCOM Russia -> West Russia (3 x infantry, 2 x artillery, 2 x armour)
    PLACE Russia: 1 x infantry, 4 x artillery, 2 x armour

    ROUND 3 ----------------------------------- GERMANS (AXIS / llm-triplea)
    BALANCE BROUGHT FORWARD ...................................... PU 41
    PURCHASE 11 x infantry ......................................... - 33
    PURCHASE 2 x artillery ......................................... - 8
    PURCHASE 2 x armour ............................................ - 10
    BALANCE AFTER PURCHASE ....................................... PU -10
    COMBAT (no attacks declared)
    NONCOM 7 Sea Zone -> 6 Sea Zone (1 x submarine, 1 x transport, 1 x destroyer)
    PLACE Germany: 1 x infantry, 1 x armour
    PLACE Germany: 1 x infantry
    PLACE Germany: 1 x infantry
    PLACE Germany: 1 x infantry
    PLACE Germany: 1 x infantry
    PLACE Germany: 1 x infantry
    PLACE Germany: 1 x infantry
    PLACE Germany: 1 x armour
    PLACE Germany: 1 x infantry
    PLACE Southern Europe: 1 x infantry
    PLACE Southern Europe: 1 x infantry
    PLACE Southern Europe: 1 x infantry
    PLACE Southern Europe: 1 x infantry
    PLACE Southern Europe: 1 x infantry
    PLACE Southern Europe: 1 x infantry

    ROUND 3 -------------------------------------- BRITISH (ALLIES / WeakAi)
    BALANCE BROUGHT FORWARD ...................................... PU 38
    PURCHASE 3 x infantry .......................................... - 9
    PURCHASE 2 x artillery ......................................... - 8
    PURCHASE 2 x transport ......................................... - 16
    PURCHASE 1 x armour ............................................ - 5
    BALANCE AFTER PURCHASE ....................................... PU 0
    COMBAT United Kingdom -> 6 Sea Zone (3 x infantry, 2 x artillery, 1 x armour) << LOAD
    COMBAT 2 Sea Zone -> 6 Sea Zone (1 x transport, 2 x infantry) via 2 Sea Zone > 3 Sea Zone > 6 Sea Zone
    COMBAT 6 Sea Zone -> Norway (6 x infantry, 3 x artillery, 1 x armour) << AMPHIBIOUS ASSAULT
    COMBAT 8 Sea Zone -> 7 Sea Zone (1 x battleship)
    NONCOM Belgian Congo -> Anglo Egypt (1 x infantry)
    NONCOM Caucasus -> Ukraine S.S.R. (4 x infantry)
    NONCOM Ukraine S.S.R. -> Eastern Europe (1 x infantry)
    NONCOM Anglo Egypt -> Trans-Jordan (1 x infantry, 1 x armour)
    NONCOM 27 Sea Zone -> 17 Sea Zone (1 x carrier, 1 x fighter, 1 x transport, 2 x destroyer) via 27 Sea Zone > 23 Sea Zone > 17 Sea Zone
    NONCOM 22 Sea Zone -> 12 Sea Zone (1 x submarine, 1 x transport) via 22 Sea Zone > 17 Sea Zone > 12 Sea Zone
    PLACE 6 Sea Zone: 2 x transport
    PLACE United Kingdom: 3 x infantry, 2 x artillery, 1 x armour

    ROUND 3 ---------------------------------- JAPANESE (AXIS / llm-triplea)
    BALANCE BROUGHT FORWARD ...................................... PU 59
    PURCHASE 1 x carrier ........................................... - 16
    PURCHASE 2 x transport ......................................... - 16
    PURCHASE 1 x submarine ......................................... - 8
    PURCHASE 1 x destroyer ......................................... - 12
    PURCHASE 1 x infantry .......................................... - 3
    PURCHASE 1 x armour ............................................ - 5
    BALANCE AFTER PURCHASE ....................................... PU -1
    COMBAT Japan -> 60 Sea Zone (1 x infantry, 1 x artillery, 1 x armour) << LOAD
    COMBAT 60 Sea Zone -> 57 Sea Zone (1 x transport, 1 x infantry, 1 x artillery, 1 x armour)
    COMBAT 57 Sea Zone -> 61 Sea Zone (1 x transport, 1 x infantry, 1 x artillery, 1 x armour)
    COMBAT 61 Sea Zone -> Manchuria (1 x infantry, 1 x artillery, 1 x armour) << UNLOAD
    NONCOM Wake Island -> 51 Sea Zone (3 x infantry) << LOAD
    NONCOM 51 Sea Zone -> 52 Sea Zone (1 x battleship, 1 x submarine, 1 x transport, 1 x destroyer, 3 x infantry)
    NONCOM 52 Sea Zone -> 57 Sea Zone (1 x transport, 3 x infantry)
    NONCOM 57 Sea Zone -> Manchuria (3 x infantry) << UNLOAD
    NONCOM China -> Manchuria (4 x infantry)
    NONCOM 51 Sea Zone -> 52 Sea Zone (1 x carrier, 2 x fighter)
    NONCOM 52 Sea Zone -> 57 Sea Zone (1 x carrier, 2 x fighter)
    NONCOM 57 Sea Zone -> Manchuria (1 x carrier, 2 x fighter) << UNLOAD
    NONCOM French Indochina -> Manchuria (2 x fighter, 2 x infantry) via French Indochina > China > Manchuria
    NONCOM 51 Sea Zone -> 50 Sea Zone (1 x battleship, 1 x submarine, 1 x destroyer)

    ========================================================================
    CLOSING SUMMARY: 3 rounds on statement, 58 decisions, 22 retries
    read more
  • B
    beelee

    @VictoryFirst

    I don't think Properties are desired from a Engine coding standpoint. That is my understanding anyway. Dan addressed it above I believe.

    Edit
    So would want to limit their use

    read more
  • VictoryFirstV
    VictoryFirst

    @RogerCooper Thanks. IIRC, I think WWI 1914 also has defending submarines that can retreat.

    @Cernel I think it's probably possible to implement a more customizable defensive retreat feature in TripleA, with a bunch of Game properties. Map-makers could decide themselves if they want to implement A&A-based retreat rules or come up with their own. It could be easily expanded by creating more properties.

    The A&A retreat system might be silly, but I think it's even more silly to ignore it completely and make it not supported. Players that want to play A&A, want to play A&A, and not with altered/changed rules that might make more sense (not speaking for everyone here, of course there are people who like to play with house rules. But at least, the original rules should be supported).

    read more