@husky81 Hi husky Welcome to the site. You may want to check the A&A site https://www.axisandallies.org/forums/. They have specific threads for each game or most anyway. Might find some saves there. Could also go to the lobby and ask the guys that play there if you could use some of their saves. I forget which one 42 online is but Revised gets played a lot in the lobby. Good Luck

@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.

@captain0 Apologies for the late reply. A few more land/ sea territories would be great. I agree, but Im no map-maker, I will have to wait for someone to offer. . do you think there is an issue with the stacking restrictions on the old 2 hit tanks? As they are 2HP, there max stack is 5s, So you have to move the ones nearer the objective first, then the rear TT/echelons after the nearer ones. This principle applies to all stacking in the map. PT boats were considered, but decided against, Bomber-Tac does a similar but has a more versatile role. . enemy factories are destroyed on capture and you can only build light industry on non sovereign territory? Again considered, but for simplicity, kept as is. I was conscious that a lot of complexity was going into the map and that it might be too much for players to take in. . Also do you think the Russian player should be immune to Winter as they were more better prepared for it historically. True they were, but again for simplicity kept simple for both Germany/Russia. The Russians do have a lot of Siberian troops/ Inf-Elite that are 'immune' to the effects of winter, so as a player spam them in the north. . Maybe also a Rasputitsa effect could block all movement on the Eastern front (all player) for one turn after Winter. Tried a variant of that, the Germans kept on losing in the north, it was so hard to balance, so removed for simplicity. . they have to manually enter the quantity as there is no selector arrow for the box like other units. Yes, this is a know problem with the TripleA look & feel, FlatLaf, if it bugs you try this; Game> Engine settings> UI theme tab> change FlatLaf Dark to Metal or Nimbus

@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

Closed my host. wirkey volunteered to play it tomorrow though, so I'll push the upload sometime after that game if everything works well and I don't notice anything else to tweak. (I made a bunch of fixes and tweaks and such other than what at this topic.)

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

@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.

@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")

@pgsquig I am a non-graphic non-artist I use this https://greenfishsoftware.org/gfie.php Crop those images above, then paste them into greenfish and shrink them into 48x48px or 72x54px or whatever size you want.

@TheDog thanks

@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

@GREGOREK said: Is a Frontier change the only way to change the cost of a unit? Define the unit multiple times with different names per cost, then use trigger to change the frontier or productionRule. Yes. Cheers...

@Petiantone the server has already been switched. your link goes to a page that says it can't be reached [image: Screenshot from 2026-09-13 11-17-44.png] Are you AI

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.