It’s not perfect, and I have no idea what the US AI is doing, but this is through round 5
Round 6
janus test europe g6.tsvg
Round 8
janus test europe g8.tsvg
USA certainly should have been more of a threat, but I played this pretty quickly and so was buying on autopilot and not looking at USA’s turns
@Stucifer said in Units, Mechanics, etc.:
Round 2 - moved 7 units into Holland belgium to retake it from 1 artillery. Should have been 1 inf, 1 artillery, if you want more % use a mech that can move fast afterwards.
[…]
The 3 infantry in W Germany should have moved to Germany. on NCM. Shouldn’t have built in France, it’s another turn away from the front.
What you’re saying all makes sense in the context of the pieces actually in play; I guess I would say that I did these sorts of moves under the assumption that I would have to leave more units in these areas for defense, if I was playing against a tougher opponent/I’m also working from the assumption that Ai Italy won’t have my back at all, and therefore I basically always need to be producing a few units in France, so that I can react to landings in the area.
Part of the reasoning is that in previous games, I’ve had West Germany’s industry get bombed into smithereens for the entire game, and I never felt like I should bother spending the money to repair it; I just assumed from that experience that I’d need to be building in France and “convoying” defensive units out to West Germany for the entire game.
…
I agree that I definitely didn’t need to build all artillery on rd2, but I had already decided to “commit to the bit” for the sake of seeing the experiment through. I stuck with it until the US entered the war, because by then it was already obvious that I needed to switch it up.
About Paris:
The French overshot by almost 2 hits in the first round of combat in your second game. Even so, however, you were still on track to have nearly a 100% chance to conquer the territory and make an IPC profit:
Wait, how’d you do that? Can you please teach me? Thank you!
@SuperbattleshipYamato open up the game history and right click on any line
Should bring up the menu
I recommend only using it at the start of a round or the end of a turn. End of a turn usually duplicates the income command so you’ll have to edit
@Stucifer said in Units, Mechanics, etc.:
I used the “save game at this point (beta)” feature to save the game at the start of round 3 and will play out round 3 and post it.
I tried to open one of the saves you posted, but it gave me an error, saying that it was made in a newer version of TripleA… but when I followed the link to download the new version, I’m pretty sure it led me to the same version I already have.
TripleA in a nutshell, am I right? 🙃
@The-Janus I’m using 2.6 which is considered a pre-release version
you can go to github to download it. Most people that play on the forums use it since 2.5 is not compatible with the updated NodeBB API used by the website.
https://github.com/triplea-game/triplea/releases/tag/2.6.14748
@SuperbattleshipYamato said in Units, Mechanics, etc.:
Wait, how’d you do that? Can you please teach me? Thank you!
Adding a screenshot to make it clear
Open History
Right Click the “Round: X” (whatever start of round you want to save at is)
Use the “Save Game at this point” command
you can also use TripleA to generate board setup charts
and I used the Export Gameboard Picture to print my Path to Victory map I made (league Global 1940 variant)
Can’t seem to do it on my 2.7 version. Maybe it’s not a Mac thing?
Your first German turn was pretty great.
I’ll note that the US actually only had an 83% chance of capturing Rome, lower than what I usually do:
I think the toughest obstacle Germany currently faces is the large number of artillery it has stuck in Moscow. Specifically, that giant stack can’t move fast enough to seize the remaining territory Germany needs to win, while there aren’t enough fast movers to accompish the task. Obviously you were doing an experiment, and I’m glad we now know what happens.
@SuperbattleshipYamato Hmm, not sure. I don’t imagine it’s a Mac issue, but the only Macs I used were in grade school when they still only had 1-button mice…
I haven’t tried 2.7, I think everyone on the league forums is using 2.6 until we start getting more features in 2.7 (say, the battle calculator not populating both sides with your units if you’re hovering over your own territory would be nice)
Really? I like that feature a lot. Much easier than adding each unit.
I agree it’ll be nice as an option.
@SuperbattleshipYamato To clarify I like using the Ctrl+A and Ctrl+D commands, they’re fantastic.
But when you hit Ctrl+B on the version I’m using (2.6.147 something) it adds your units to both the Attackers and Defenders when it opens the Calculator on your own territory.
If I open it up hovering over Crete
Much better than the bug in another version where every single unit was duplicated, but still frustrating.
yea the latest pre has fixed that. Or 2.7+14895 is what I’m using and it works correctly on linux anyway
https://github.com/triplea-game/triplea/releases/tag/2.7.14895
Oh, you mean that. Yeah I don’t like it. Just weird.
@barnee Okay perfect! I downloaded and tried saving a test game and that save file still opens in my 2.6 client. So perhaps I can start sneakily using 2.7 soon!! 🤭
yea I think 2.6 saves will work with 2.7 and vice versa. Just not with 2.5. Some of the new features might not translate if you run it in 2.6 probably.
But for this game, you should be able to play it with 2.7
From my experience, games, at least starting from 2.5, are compatible with newer versions, but not vice versa.
I just played a Europe 1940 game against the Hard AI much like your parameters, except with me controlling Italy as well.
2025-2-16-World-War-II-Europe-1940-2nd-Edition.tsvg
With the exception of some really bad rolls for Italy one turn, the Axis butchered the Allies from beginning to end. Somehow Germany took Moscow on turn 5(!). It was easy strolling after that. Not sure whether the Hard AI was worse than yours, but they really wasted the US mucking around for way too long.
