@Ramon I believe by default tech dice use the dice sides specified on the top of the XML (by default 6). So if you want to give tech a dice of 4, you'd be changing the dice sides that regular combat units use as well. If you want tech to be rolled with 4 dice sides and the other rolls with 6 dice sides, I think theoretically it would possible, but would it would be insanely complicated and require the use of a user action phase with a lot of nested triggers/conditions. Also, some of the stuff you want to implement that is currently not possible can be made possible by making changes to the engine. So if you'd like to see this happen, feel free to post a feature request here: https://github.com/triplea-game/triplea/issues (click on "New Issue" and select the top option "Feature Request")

@ubernaut cloudflare is comprehensive, IIRC you can toggle it so any new IP needs to do a captcha style challenge first. If we get attacked for real, then setting up cloudflare would likely be the only thing to restore the forum. OTOH, our data is what most people really want, I doubt very many really want to simply DDOS TripleA

Step 8 Balancing the Game Balancing Axis & Allies style games is a difficult task. For example in V3-1941 the Allies are ahead in every measure, but the game is reasonably balanced. Production 120 to 58 Starting PU 113 to 58 Units 124 to 105 TPV 696 to 645 Objectives 12 to 6 This is typical of A&A games, that units and TPV are close between the sides. However income obviously matters in the long run. Furthermore, vulnerable territories of the Status Quo players may actually work to the benefit of the Aggressor. As a starting formula I have: Production x 3+ Starting PU's + Units + TPV - vulnerability penalty - delayed entry penalty The vulnerability penalty is x3 the income of vulnerable territories + factories in vulnerable territories. A territory is vulnerable if they are owned by Status Quo country that is active at the game start and that is adjacent to an Aggressor country that is active the game start. The delayed entry penalty is 10% of the TPV for each turn past 1 of delay. To balance the game additional units (and starting PU's) are added to the aggressors if they are behind and additional income to the lead status quo power if they are behind. Units will be randomly added to territories with a weighting equal to value+1. The chance of a specific unit will be proportional to the inverse of its cost. In either case units will have the build caps equal to 120/cost to prevent ridiculous builds by the AI.

Played only a little bit. Will retake the save tomorrow.

@LaFayette Right Arm I been seeing the spinning circle a bit more frequently ever since the Big June update. I know the other site gets hammered pretty hard sometimes. I think Djensen got some counters but sometimes they still get through.

Updated to 2.63 [image: Screenshot from 2026-09-25 20-20-09.png]

@craigviau Nice you got it working xml work can be frustrating, unless you were born with a large amount of patience I try to look at it as a puzzle anymore, as opposed to wanting to throw my computer down the driveway lol PactofSteel2 xml is still the best information source, next to wc

@beelee I would suggest erasing the flags which is easy to do in Paint. There is no reason to have flags in unit images, as you can turn flags on with View/Flag Display/Small.

@TheDog thanks

@Cernel The torus environment eliminates 'back wall' defenses and allows more kingdom interactions. The map in this way is infinitely scroll-able. The torus is also an observer point of view that the inhabitants cannot see. Try dragging the map. It's just a continuous land mass with each kingdom at its center.

Thanks! Tidied up that first section to make it current.

@lafayette @ubernaut We have Success

@TheDog said: Would your super-dupa placementAnyTerritory fix Thanks for the thought. This hack helps with the placement of factory/construction type units which were not placed by the AI's normal purchase-placement routine. Here the problem is with purchasing, which the AI is not doing because the AI does not find when to start a simulated purchase. Without creating a purchase, there is nothing to place. For my testing, replacing "placeNoAirCheck" with "place" does allow the AI to make purchases but this does not seem to work for @rogercooper. I'm not replacing the delegate "NoAirCheckPlaceDelegate" with the "PlaceDelegate" as there would be no change in my testing. So maybe @rogercooper could test if changing both the name and delegate makes any difference. Cheers...

@ptt196 The Triple AI has has some tweaks over the past couple of years, but it is really up to the map maker to squeeze the most out of the AI. See here if you fancy improving your favoured map. https://forums.triplea-game.org/topic/3743/how-to-make-a-map-ai-friendly WW2 wise 1941 Global Command Descision will give a good game, as its AI has been tweeked. https://forums.triplea-game.org/topic/3326/1941-global-command-decision-official-thread

@beelee Thank you for your reply. I have also crossposted on AxisandAllies.org, as you've suggested, although I might not have posted in the right place for maximum visibility. The setup I'm workign it is the tournament setup for 1942 2nd edition, the one that starts the German bomber in Ukraine rather than Germany where it is in out of box. As Panther says, there are some rule discrepancies, like carriers not being able to hold allied fighters. At the present level that bots play, those aren't so relevant. We are at the point where we are trying to get the program to not hang important units without good reason, and to not play either over aggressive or over passive.