You need to name it Chinese instead China for the easiest way to bring China.

Then copy the XML and give a different name. Then examine the XML. It is not complicated.

@Hepps You could place a hostile munitions type unit that targets all units in the territory with a 50% chance of hitting on an AA type of attack.

Many scenarios have no victory condition defined.

@ubernaut - probably not, I’ll check it out later..

No, one of my teammates, playing on a pc, still can post so our epic battle continues!

@LaFayette said in mapName Deprecated:

There are further implications to this for both auto-download of missing maps and further reducing save-game size (which is the dominating factor (the dominating slow-down) for AI performance).

I'd like to clarify this. AI performance is dominated by battle calculations. Any battle calculation begins by first taking a full save of the existing game. It's been measured that over 80% of the time involved in battle calculation is at this step. This implies that AI is slow at later game stages as this full copy and load is slower and slower the more game history there is.

A save-game contains most of the data found from an XML. This data is expanded into game objects that take up a fair amount of space. We are designing a change to save-games so that the engine only saves the differences to game state after initial load. This should result in a drastically smaller save game file, and importantly it allows for much greater compatibility between game releases. It is very possible that after we make this change, all future TripleA games will be save game compatible. It will also be a boon to development, currently very seemingly innocent changes break save-game compatibility, the inability to make those changes create other headaches and essentially trashes the ability to fix core code architecture and design. Long story short, at some point the engine will need to know where the original XML file is located when loading save games as it will need to load in data from that XML file.

TL;DR, with 'delta' save-game files we expect save-game compatibility will be maintained for many releases going forward and no longer a year at a time. It will be a major benefit for code development and increase developer productivity. And, AI is expected to get something of a 10x boost in performance.

To do 'delta' save-games, I think we can likely do so without needing to modify existing maps. Having that work for 'variants' was not considered (until now it's been something of a distant memory). We would need to fix variants in some way if they were to keep working like this. Long term though there is already a different solution envisioned where all games XML files would be released independently of map files and map files would become 'graphics packs' that XMLs could pick and choose. The engine would automatically determine which 'graphic packs' are required for a given XML and download them automatically.

My hope is that delta-save games could be released before the end of 2023. It's a much higher priority than graphics packs. Meanwhile having a maps-server, a requirement for a graphics pack, which provides additional benefits, will be released likely in the next month or two.

TL;DR: delta-saves will not work at all for unofficial variants, they need to be modified one way or another. Long term there is another solution envisioned that will 'fix' variants so that game XML files are already independent of map assets. 'Delta-save-games' is currently planned to be released first before map 'graphic-packs'.

@Schulz @RogerCooper

Thanks for the responses. I was thinking about going the notification route as well.

TripleA Turn Summary: Japanese round 5

TripleA Turn Summary for game: World War II Pacific 1940 2nd Edition, version: 3.1.0

Game History

Round: 5 Politics - Japanese Purchase Units - Japanese Japanese buy 1 armour, 1 battleship, 2 bombers and 1 factory_minor; Remaining resources: 2 PUs; 6 SuicideAttackTokens; Combat Move - Japanese 1 carrier moved from 35 Sea Zone to 42 Sea Zone 1 tactical_bomber moved from 35 Sea Zone to 42 Sea Zone 1 tactical_bomber moved from Celebes to 42 Sea Zone 4 cruisers moved from 35 Sea Zone to 6 Sea Zone 2 battleships moved from 35 Sea Zone to 6 Sea Zone 4 submarines moved from 35 Sea Zone to 6 Sea Zone 1 tactical_bomber moved from 35 Sea Zone to 6 Sea Zone 3 destroyers moved from 35 Sea Zone to 6 Sea Zone 1 bomber moved from Kiangsu to 6 Sea Zone 1 mech_infantry moved from Szechwan to Yunnan 4 artilleries moved from Szechwan to Yunnan 5 infantry moved from Kweichow to Yunnan 1 artillery moved from Kweichow to Yunnan 1 artillery moved from Kweichow to Yunnan 1 infantry moved from Hunan to Yunnan 2 armour moved from Hunan to Yunnan 2 fighters moved from Hunan to Yunnan Combat - Japanese Battle in 6 Sea Zone Japanese attack with 2 battleships, 1 bomber, 4 cruisers, 3 destroyers, 4 submarines and 1 tactical_bomber Americans defend with 1 battleship, 1 carrier, 3 cruisers, 2 destroyers and 1 submarine; ANZAC defend with 1 destroyer Japanese roll dice for 4 submarines in 6 Sea Zone, round 2 : 1/4 hits, 1.33 expected hits Units damaged: 1 battleship owned by the Americans Japanese roll dice for 2 battleships, 1 bomber, 4 cruisers, 3 destroyers and 1 tactical_bomber in 6 Sea Zone, round 2 : 5/11 hits, 5.50 expected hits Americans roll dice for 1 submarine in 6 Sea Zone, round 2 : 0/1 hits, 0.17 expected hits Americans roll dice for 1 battleship, 1 carrier, 3 cruisers and 3 destroyers in 6 Sea Zone, round 2 : 4/8 hits, 3.50 expected hits Units damaged: 2 battleships owned by the Japanese 1 submarine owned by the Americans, 2 destroyers owned by the Americans, 1 destroyer owned by the ANZAC, 1 carrier owned by the Americans and 2 submarines owned by the Japanese lost in 6 Sea Zone Japanese roll dice for 2 submarines in 6 Sea Zone, round 3 : 1/2 hits, 0.67 expected hits 1 cruiser owned by the Americans lost in 6 Sea Zone Japanese roll dice for 2 battleships, 1 bomber, 4 cruisers, 3 destroyers and 1 tactical_bomber in 6 Sea Zone, round 3 : 6/11 hits, 5.50 expected hits Americans roll dice for 1 battleship and 2 cruisers in 6 Sea Zone, round 3 : 1/3 hits, 1.67 expected hits 2 cruisers owned by the Americans, 1 submarine owned by the Japanese and 1 battleship owned by the Americans lost in 6 Sea Zone Japanese win, taking 6 Sea Zone from Americans with 2 battleships, 1 bomber, 4 cruisers, 3 destroyers, 1 submarine and 1 tactical_bomber remaining. Battle score for attacker is 84 Casualties for Japanese: 3 submarines Casualties for ANZAC: 1 destroyer Casualties for Americans: 1 battleship, 1 carrier, 3 cruisers, 2 destroyers and 1 submarine Battle in 42 Sea Zone Japanese attack with 1 carrier and 2 tactical_bombers ANZAC defend with 2 destroyers and 2 transports Japanese roll dice for 1 carrier and 2 tactical_bombers in 42 Sea Zone, round 2 : 1/2 hits, 1.00 expected hits ANZAC roll dice for 2 destroyers and 2 transports in 42 Sea Zone, round 2 : 2/2 hits, 0.67 expected hits 1 destroyer owned by the ANZAC and 1 carrier owned by the Japanese lost in 42 Sea Zone Japanese roll dice for 2 tactical_bombers in 42 Sea Zone, round 3 : 1/2 hits, 1.00 expected hits ANZAC roll dice for 1 destroyer and 2 transports in 42 Sea Zone, round 3 : 0/1 hits, 0.33 expected hits 1 destroyer owned by the ANZAC lost in 42 Sea Zone 2 transports owned by the ANZAC lost in 42 Sea Zone Japanese win with 2 tactical_bombers remaining. Battle score for attacker is 14 Casualties for Japanese: 1 carrier Casualties for ANZAC: 2 destroyers and 2 transports Battle in Yunnan Japanese attack with 2 armour, 6 artilleries, 2 fighters, 6 infantry and 1 mech_infantry British defend with 4 armour and 1 mech_infantry; Chinese defend with 1 fighter and 2 infantry Japanese roll dice for 2 armour, 6 artilleries, 2 fighters, 6 infantry and 1 mech_infantry in Yunnan, round 2 : 11/17 hits, 6.17 expected hits Chinese roll dice for 4 armour, 1 fighter, 2 infantry and 1 mech_infantry in Yunnan, round 2 : 2/8 hits, 3.67 expected hits 2 infantry owned by the Japanese, 1 mech_infantry owned by the British, 2 infantry owned by the Chinese, 1 fighter owned by the Chinese and 4 armour owned by the British lost in Yunnan Japanese win, taking Yunnan from Chinese with 2 armour, 6 artilleries, 2 fighters, 4 infantry and 1 mech_infantry remaining. Battle score for attacker is 38 Casualties for Japanese: 2 infantry Casualties for British: 4 armour and 1 mech_infantry Casualties for Chinese: 1 fighter and 2 infantry Non Combat Move - Japanese 1 aaGun moved from Hunan to Yunnan 1 bomber moved from 6 Sea Zone to Japan 1 tactical_bomber moved from 6 Sea Zone to Japan 1 tactical_bomber moved from 42 Sea Zone to Borneo 1 tactical_bomber moved from 42 Sea Zone to Borneo 4 infantry moved from Anhwe to Hunan 1 infantry moved from Szechwan to Yunnan 1 infantry moved from Sikang to Szechwan 1 infantry moved from Kweichow to Hunan 1 infantry moved from Shensi to Kweichow 1 infantry moved from Tsinghai to Shensi 1 infantry moved from Suiyuan to Hopei 1 infantry moved from Kansu to Shensi 1 infantry moved from Suiyuan to Hopei 2 transports moved from 35 Sea Zone to 34 Sea Zone 1 infantry moved from Paulau Island to 34 Sea Zone 1 infantry and 1 transport moved from 34 Sea Zone to 35 Sea Zone 1 infantry moved from 35 Sea Zone to Philippines 1 transport moved from 34 Sea Zone to 35 Sea Zone 1 fighter moved from Yunnan to Hunan 1 fighter moved from Yunnan to Hunan Place Units - Japanese 1 factory_minor placed in Shantung 1 battleship placed in 6 Sea Zone 2 bombers placed in Japan 1 armour placed in Kiangsu Turn Complete - Japanese Japanese collect 54 PUs; end with 56 PUs

Combat Hit Differential Summary :

Chinese regular : -1.67 Americans regular : -0.33 Japanese regular : 4.83 ANZAC regular : 1.00

Territory Summary for Japanese :

Iwo Jima : 1 infantry Shantung : 1 flag, 1 factory_minor Kiangsu : 1 flag, 1 armour and 1 factory_minor Kiangsi : 1 flag Japan : 3 aaGuns, 1 airfield, 1 artillery, 3 bombers, 1 factory_major, 1 harbour, 5 infantry and 1 tactical_bomber Jehol : 1 flag Manchuria : 1 flag Shensi : 1 flag, 2 infantry Yunnan : 1 flag, 1 aaGun, 2 armour, 6 artilleries, 5 infantry and 1 mech_infantry Suiyuan : 1 flag Kweichow : 1 flag, 1 infantry Hunan : 1 flag, 2 fighters and 5 infantry Kansu : 1 flag Hopei : 1 flag, 2 infantry Tsinghai : 1 flag Szechwan : 1 flag, 1 infantry Chahar : 1 flag Sikang : 1 flag Anhwe : 1 flag Borneo : 1 flag, 2 tactical_bombers Kwangtung : 1 flag, 1 harbour Philippines : 1 flag, 1 airfield, 1 armour, 1 harbour and 1 infantry French Indo China : 1 flag Celebes : 1 flag Sumatra : 1 flag 36 Sea Zone : 1 flag 35 Sea Zone : 2 transports 6 Sea Zone : 3 battleships, 4 cruisers, 3 destroyers and 1 submarine

Production/PUs Summary :

Japanese : 54 / 56 Americans : 15 / 59 Chinese : 1 / 3 British : 10 / 12 ANZAC : 14 / 23 Russians : 9 / 0 French : 0 / 0 Dutch : 0 / 0

Dice Statistics:

Total 1 was rolled 63 times 2 was rolled 63 times 3 was rolled 56 times 4 was rolled 53 times 5 was rolled 52 times 6 was rolled 56 times Average roll : 3.397 Median : 3.000 Variance : 0.336 Standard Deviation : 0.579 Total rolls : 343 British Combat 1 was rolled 8 times 2 was rolled 12 times 3 was rolled 6 times 4 was rolled 9 times 5 was rolled 6 times 6 was rolled 8 times Average roll : 3.347 Median : 3.000 Variance : 0.517 Standard Deviation : 0.719 Total rolls : 49 ANZAC Combat 1 was rolled 8 times 2 was rolled 4 times 3 was rolled 4 times 4 was rolled 1 times 5 was rolled 1 times 6 was rolled 1 times Average roll : 2.263 Median : 2.000 Variance : 2.157 Standard Deviation : 1.469 Total rolls : 19 Americans Combat 1 was rolled 3 times 2 was rolled 7 times 3 was rolled 4 times 4 was rolled 3 times 5 was rolled 6 times 6 was rolled 7 times Average roll : 3.767 Median : 4.000 Variance : 0.621 Standard Deviation : 0.788 Total rolls : 30 Chinese Combat 1 was rolled 10 times 2 was rolled 5 times 3 was rolled 7 times 4 was rolled 13 times 5 was rolled 6 times 6 was rolled 6 times Average roll : 3.383 Median : 4.000 Variance : 1.018 Standard Deviation : 1.009 Total rolls : 47 Japanese Combat 1 was rolled 34 times 2 was rolled 35 times 3 was rolled 35 times 4 was rolled 27 times 5 was rolled 33 times 6 was rolled 34 times Average roll : 3.465 Median : 3.000 Variance : 0.234 Standard Deviation : 0.483 Total rolls : 198

Savegame

I think the version discussion boils down to utility vs complexity (specifically the complexity to understand and communicate how to use the map.yml version field).

There is a discussion open in github issues whether to bake categories into map.yml which would put it under map maker control and alleviate the map admin team from an ongoing upkeep task.

Deployment wise, remaining we'll need to generate a map.yml for every repo and upload it presumably to the top-most directory of each map. FWIW this should be not that bad, currently the map engine is now rigged to generate a map.yml file for any downloaded maps that do not have it, we'd only need to take the generated file and upload it.

Otherwise, does the current map.yml look good and is it clear? The XML path I think is maybe the most error prone and it's the path of any game XML relative to the map.yml file. If the map.yml file is at the top level of a map (expected), then the XML path is really just the path to the XML file from the map folder..

Last, hopefully it's also well understood that game and map name will now come from the map.yml file and the corresponding XML attributes would be considered deprecated and no longer read by 2.6+ engines.

The map.yml also removes the need for a map repository or map zip to have any kind of specific naming to match the map name in the XML, the map repo and zip could have any reasonable name and would essentially no longer matter.

@Contango right on 🙂 i had forgot about that. Glad you got it working

Hi there, I finished our main episode with John Cutter (Cinemaware) about Rocket Ranger and Defender of the Crown. It will be released via Spotify, itunes, etc. in Mid of February 2021.

Now there's some time to flavour the interview with some video as well. I think within the next 2 weeks, the Editing of the interview with LaFayette should be final and will be released. The Larry Harris video is still on hold, because we are about to relaunch our Website. As we're just two people doing the podcast, this is still queued. Meanwhile, on our homepage www.legendarygam.es you may find those pics he has done for us.

In December 2020, we've posted a full Let's Play of A&A in the TripleA engine on Youtube. It consists out of 30+ parts, showing a dice game of 1940 on the side of the Allies. It includes the strategic and tactical considerations of each turn as well as the analysis of the movement of the Axis player. All of this was done in German language. On the link below you may find the first episode of the Gameplay.

https://youtu.be/mbh-ocwXyqw

A second Let's Play will be released at the end of 2021 playing the Axis in 1940.

For all people being interested in Wargaming in common. My brother explains (in German language) all details to Gary Grigsby's - A world divided. This tutorial will be released within the next 2 weeks as well on our Youtube channel.

@epwitz What version of TripleA are you using? Is Java up to date?

@Contango Yup... not a perfect solution... but might work well with some testing. Just a thought to solve your problem.

Hi,

It's been a long time since I played A&A1940 last time, but I'd really like to play againa.
Not sure which is the "balanced edition", but glad to play 1vs1 with you and learn.