TripleA Turn Summary: Germans round 4 TripleA Turn Summary for game: World War II Revised LHTR, version: 1.4.1 Game History Round: 4 Purchase Units - Germans Germans buy 3 armour, 3 infantry and 1 submarine; Remaining resources: 1 PUs; Combat Move - Germans 1 submarine moved from 5 Sea Zone to 6 Sea Zone 1 bomber moved from Germany to 6 Sea Zone 1 fighter moved from Germany to 6 Sea Zone 1 armour moved from French Equatorial Africa to Belgian Congo Germans take Belgian Congo from British 1 armour moved from Belgian Congo to Italian East Africa Germans take Italian East Africa from British 1 infantry moved from Anglo Egypt to 15 Sea Zone 1 infantry and 1 transport moved from 15 Sea Zone to 13 Sea Zone 1 infantry moved from Southern Europe to 14 Sea Zone 1 infantry moved from Southern Europe to 14 Sea Zone 2 infantry and 1 transport moved from 14 Sea Zone to 13 Sea Zone 3 infantry moved from 13 Sea Zone to Algeria 1 infantry moved from Libya to Algeria 1 battleship moved from 15 Sea Zone to 13 Sea Zone 1 armour moved from Germany to Balkans 1 armour moved from Germany to Balkans 1 armour moved from Germany to Balkans 1 armour moved from Germany to Balkans 1 infantry moved from Eastern Europe to Balkans 1 fighter moved from Eastern Europe to Balkans 1 armour moved from Eastern Europe to Balkans 1 infantry moved from Eastern Europe to Belorussia Combat - Germans Battle in Algeria Germans attack with 4 infantry Americans defend with 2 armour and 2 infantry Germans roll dice for 1 battleship in Algeria, round 2 : 0/1 hits, 0.67 expected hits Germans roll dice for 4 infantry in Algeria, round 2 : 1/1 hits, 0.67 expected hits Americans roll dice for 2 armour and 2 infantry in Algeria, round 2 : 1/1 hits, 1.67 expected hits 1 infantry owned by the Germans and 1 infantry owned by the Americans lost in Algeria Germans roll dice for 3 infantry in Algeria, round 3 : 0/1 hits, 0.50 expected hits Americans roll dice for 2 armour and 1 infantry in Algeria, round 3 : 1/1 hits, 1.33 expected hits 1 infantry owned by the Germans lost in Algeria Germans roll dice for 2 infantry in Algeria, round 4 : 0/1 hits, 0.33 expected hits Americans roll dice for 2 armour and 1 infantry in Algeria, round 4 : 2/1 hits, 1.33 expected hits 2 infantry owned by the Germans lost in Algeria Americans win with 2 armour and 1 infantry remaining. Battle score for attacker is -9 Casualties for Germans: 4 infantry Casualties for Americans: 1 infantry Battle in 6 Sea Zone Germans attack with 1 bomber, 1 fighter and 1 submarine British defend with 1 destroyer and 1 submarine Germans roll dice for 1 submarine in 6 Sea Zone, round 2 : 0/1 hits, 0.33 expected hits British roll dice for 1 submarine in 6 Sea Zone, round 2 : 0/1 hits, 0.33 expected hits Germans roll dice for 1 bomber and 1 fighter in 6 Sea Zone, round 2 : 1/1 hits, 1.17 expected hits British roll dice for 1 destroyer in 6 Sea Zone, round 2 : 0/1 hits, 0.50 expected hits 1 submarine owned by the British lost in 6 Sea Zone Germans roll dice for 1 submarine in 6 Sea Zone, round 3 : 1/1 hits, 0.33 expected hits British roll dice for 1 destroyer in 6 Sea Zone, round 3 : 0/1 hits, 0.50 expected hits 1 destroyer owned by the British lost in 6 Sea Zone Germans win with 1 bomber, 1 fighter and 1 submarine remaining. Battle score for attacker is 20 Casualties for British: 1 destroyer and 1 submarine Battle in Balkans Germans attack with 5 armour, 1 fighter and 1 infantry Russians defend with 2 artilleries and 2 infantry Germans roll dice for 5 armour, 1 fighter and 1 infantry in Balkans, round 2 : 3/1 hits, 3.17 expected hits Russians roll dice for 2 artilleries and 2 infantry in Balkans, round 2 : 2/1 hits, 1.33 expected hits 2 infantry owned by the Russians, 1 artillery owned by the Russians, 1 infantry owned by the Germans and 1 armour owned by the Germans lost in Balkans Germans roll dice for 4 armour and 1 fighter in Balkans, round 3 : 3/1 hits, 2.50 expected hits Russians roll dice for 1 artillery in Balkans, round 3 : 0/1 hits, 0.33 expected hits 1 artillery owned by the Russians lost in Balkans Germans win, taking Balkans from Russians with 4 armour and 1 fighter remaining. Battle score for attacker is 6 Casualties for Germans: 1 armour and 1 infantry Casualties for Russians: 2 artilleries and 2 infantry Non Combat Move - Germans 1 fighter moved from Balkans to Germany 1 bomber moved from 6 Sea Zone to Germany 1 fighter moved from 6 Sea Zone to Germany Place Units - Germans 3 infantry placed in Southern Europe 3 armour placed in Germany 1 submarine placed in 5 Sea Zone Turn Complete - Germans Germans collect 40 PUs; end with 41 PUs Combat Hit Differential Summary : Germans : -0.67 British : -1.33 Americans : -0.33 Russians : 0.33 Territory Summary for Germans : Germany : 1 aaGun, 3 armour, 1 bomber, 1 factory and 2 fighters French West Africa : 1 flag Belgian Congo : 1 flag Southern Europe : 1 aaGun, 1 factory and 3 infantry Italian East Africa : 1 flag, 1 armour Eastern Europe : 1 armour Western Europe : 1 aaGun and 2 infantry French Equatorial Africa : 1 flag Balkans : 4 armour Belorussia : 1 infantry Anglo Egypt : 1 flag 5 Sea Zone : 1 submarine 6 Sea Zone : 1 submarine 13 Sea Zone : 1 battleship and 2 transports Production/PUs Summary : Russians : 29 / 33 Germans : 40 / 41 British : 32 / 35 Japanese : 19 / 22 Americans : 46 / 48 Dice Statistics: Total 1 was rolled 26 times 2 was rolled 26 times 3 was rolled 26 times 4 was rolled 33 times 5 was rolled 37 times 6 was rolled 21 times Average roll : 3.544 Median : 4.000 Variance : 0.993 Standard Deviation : 0.997 Total rolls : 169 Null / Other 1 was rolled 1 times 4 was rolled 2 times 5 was rolled 1 times Average roll : 3.500 Median : 4.000 Variance : 1.111 Standard Deviation : 1.054 Total rolls : 4 Germans Combat 1 was rolled 9 times 2 was rolled 10 times 3 was rolled 8 times 4 was rolled 9 times 5 was rolled 12 times 6 was rolled 9 times Average roll : 3.561 Median : 4.000 Variance : 0.170 Standard Deviation : 0.412 Total rolls : 57 British Combat 1 was rolled 5 times 2 was rolled 4 times 3 was rolled 5 times 4 was rolled 8 times 5 was rolled 8 times 6 was rolled 7 times Average roll : 3.838 Median : 4.000 Variance : 0.412 Standard Deviation : 0.642 Total rolls : 37 Americans Combat 1 was rolled 2 times 2 was rolled 4 times 3 was rolled 4 times 4 was rolled 3 times 5 was rolled 5 times 6 was rolled 2 times Average roll : 3.550 Median : 3.500 Variance : 0.386 Standard Deviation : 0.621 Total rolls : 20 Russians Combat 1 was rolled 6 times 2 was rolled 2 times 3 was rolled 7 times 4 was rolled 4 times 5 was rolled 2 times 6 was rolled 2 times Average roll : 3.000 Median : 3.000 Variance : 1.129 Standard Deviation : 1.062 Total rolls : 23 Japanese Combat 1 was rolled 3 times 2 was rolled 6 times 3 was rolled 2 times 4 was rolled 7 times 5 was rolled 9 times 6 was rolled 1 times Average roll : 3.571 Median : 4.000 Variance : 1.827 Standard Deviation : 1.352 Total rolls : 28 Savegame

@ubernaut nevermind. I'll just look if there's something in 2 hours or so.

@redrum 1. Yep. 2. Yep. You're good at this! Cheers...

@Cernel The Battering-Ram and Siege-Tower will be for suppressing Wall Archers. Without the use if them, right now a Capital would practically kill 3 attacker units every turn, but only 1,6 unit if suppressed by two siege engines. The three artillery units are long range artillery vs. buildings and units, but their ammo will ofcours also fire if attacked. The Trebuchet is mostly an offence weapon, catapult a balanced weapon and the ballista has defensive stats. Right now the units can also defend themselves in combat with 1 def/1 att, but right now I am considering removing this and adding footmen/pikemen support abilliy.

@redrum Instead of adding a new 'canStack' property, why not just add the 'count' value to the 'bonusType' property. So for @Frostion's Siege-Tower: <option name="bonusType" value="Cover" count="3"/> would allow 3 Siege-Towers to stack the support together. The absent of count would equal 1. So if @Frostion had a Battering-Ram and its supportAttachment: <option name="bonusType" value="Cover"/> Then the Battering-Ram could not stack support with itself, but it would still stack with the Siege-Tower so that: 2 Siege-Towers would equal -2 support for enemy fortifications 1 Siege-Tower and 1 Battering-Ram would equal -2 support for enemy fortifications 2 Battering-Rams would equal just a -1 support for enemy fortifications. 1 Siege-Tower (count="3") with two Battering-Rams would still gain the -3 support. Just some thoughts. Cheers...

Mod status would be tied to account and not username. If someone wants to change their account name, they can create a new account. I'm not sure why we should make it so difficult and say "no, you have to re-register with that same email but a new account name". Is that just not convoluted? We can certainly discourage mods from changing their names, or changing often. I'm not sure if it's worth the complexity of special casing it into the code when we can keep the same name by convention. Given the game allows multiple logins, no limit on how many accounts, no validation of email, no password requirement even, it doesn't seem like relieving the requirement of creating a new account if/when a person wants to change their username is a huge deal necessarily. I really view it as a convenience so you don't have to register multiple accounts. Arguably we want that particularly when stats could become tied to a user.

@redrum yup forgot we still had that kicking around

@LaFayette oki doki

@Cernel I think you officially win the award for the "most emotions expressed by emoji in a single post"! But yeah, the others are a bit more hacky but could be better for certain situations. The good news is that they all should work. And yes unit selection/highlighting for 0 move units isn't very polished or flexible (seems like it would be a good feature request). @Frostion Ok. Well, I think having it proportion to movement cost rather than just number of territories moved is probably better as a default. But really whoever makes the first good map with fuel and movement cost can request how they think it should work and most likely I'll adjust it then.

@Frostion Well, probably those games had something going on for the guarding units, I assume. It would be cool if some dynamics like this would exist also in TripleA, like only units that didn't move having some defensive bonus or being able to scramble (this last one I would really like), but nothing at all the like is currently supported, and, even if it would, that would not be the default, so it wouldn't matter for the basics. I think that "guard" has the opposite problem as "sleep". While sleep sounds silly (will the units be attacked while they are sleeping?) and hints to something that is not really indefinite (sleeping forever in a neverending night?), but I would rather expect it is going to last at most 1 turn (even though, of course, there are usually many nights in one turn), "guard" would really make me think that those units are actually doing something, albeit static, that would give some advantage of some sort, over the units that are not in "guard" mode. So, I'm really neutral between "sleep" and "guard". Both sound about as bad to me. But the shield image is at least better than the shovel idea, in my opinion, as at least you won't expect some trenches to eventually appear. If "sleep" I would rather suggest a "hammock" instead of the "moon", and without the "zzz" letters. Side note, regarding "standing", that was the nomenclature for the German "static infantries".

@redrum no i havent, pretty much only run stable.

@RoiEX I am working on a system to randomly assign nations to alliances and I am using a small map for testing. I hope this gets fixed soon.

@Cernel In any case, this would change the current rules in that, then, you could move for free through a city that you captured on the same turn.

@LaFayette I'm actually guessing the reason was the map name was messed up as it had a dash which caused it to not download and launch properly. It is now updated and available to download in TripleA. I'll create a separate map thread for it tomorrow.

Transferred to bug tracker: https://github.com/triplea-game/triplea/issues/5216 DanVanAtta created this issue in triplea-game/triplea open UI Freeze Problem vs AI #5216

@ff03k64 It is a work-in-progress map. I have had a little pause in developing it, but I think that I am about ready to begin working on it again. I have not released a playable beta version yet, but it will come out eventually. Look for it in the maps and mods category.

It's my 8 week updated war/gaming Youtube pick! a dragon double shot Live the Metal Dragon Life by Dragon's Prophet; https://www.youtube.com/watch?v=2NGbSw_UYgU Magic Dragon by Gloryhammer; https://www.youtube.com/watch?v=UnsNFz_NrbA