@frostion I see what you are getting at though I'm fairly hesitant to create a bunch of properties that allow lots of different behaviors for suicide units and even if we did want more flexibility then I start to think different unit properties might be better than global properties so you could have different functionality for say kamikaze planes vs ammo units on the same map. Here are a few additional things you probably need to consider in the 'strike one at a time' situation: How does it work with LL? How is order of suicide units rolls determined if there are different types of suicide units (attacking with say kamikaze and ammo units in the same battle)? Weakest rolls first? Strongest rolls first? Tie breaker? Essentially, you need a sense of ordering of the suicide units. Need to consider 'isSuicide' vs 'isSuicideOnHit' and whether they both would use the property as well as ordering. As you can probably see from these questions, this gets a bit complex fairly quickly which is probably the primary reason it works as it does currently.

@redrum thank you

I think the hard AI can be pretty enjoyable. For the standard WW2 maps that don't have complex objectives and features the AI doesn't 'understand' or tech wildcards and the like, it does reasonably for itself. One place where it can be instructive is seeing how airpower and bombers in particular can be pretty effective at covering vs fleets once the AI is amassing a big stack of 'em. Seen some brazen strikes from the machine there. But it still struggles with transports and naval, over-purchasing or spreading things too thin too quickly. You can also back it off a sea zone more effectively whereas a human would probably fight it out or make a trade to force a resolution. Right now it doesn't prioritize things like VCs, so it wouldn't play well vs a PvP strategy where victory is determined that way. Still its useful to have for showing the ropes, and getting familiar with maps beforehand.

@helsinkiharbour Thanks

@Frostion said in Can someone make a video in which you create a map in github?: @Cernel I must say that I dont know 100% what this feature is and what it is for, but if I don't use that overwrite thing, then the files do not seem to upload and replace the old uploaded stuff. Instead an error just occurs and no upload happens. I didn't use that setting for the latest world_at_war update and all seemed to work fine. Anyone knows better?

@general_zod Good recommendation. I've seen in for example online go timers that add a fixed amount per turn. The idea being there is that you can extend a long running game and not be forced to end the game in say round 3 or 4 because both players are low on time.

@redrum said in Units Can Load In Hostile Sea Zones: @Hepps This would actually probably be a good property for TWW as I've actually run into exactly this case in the Pacific in my game vs Wirkey which makes it so I have to keep all my troops loaded on transports which just feels wrong: https://forums.triplea-game.org/topic/533/tww-2-7-7-2-lalapalooza-redrum-allies-vs-wirkey-axis I actually think it is not that wrong to be wanting to keep stuff loaded, but for a different reason. Really, loading/unloading takes some time, so you would not want to unload on random islands, and then reload, for no good reason, but this should be rather related to the ships using like 1 movement point for loading and/or unloading anything, on the turn. So, for example, a ship can move 3 but if it loads/unloads anything in 1 sea zone can move 2 and if it loads/unloads anything in 2 sea zones can move 1. Probably, for easy of play, it would be advisable to charge the movement cost only on unloading, not on loading, especially since TA doesn't display loaded stuff well (what is loaded where). Of course, this is off topic. Final note, the original Axis&Allies 1981 (the first edition) actually had the loading cost dynamic, in that loading ships would have used 1 movement point for that. http://axisandallies.wikia.com/wiki/Axis_%26_Allies_(Nova_Games_Edition) I'm not opening a feature request, as I don't actually have a user case and I think there are more important feature requests around (or I could easily open hundreds of them more), but wanted to point out that the fact that normally in TA you almost never want to keep stuff on board is not necessarily that normal.

@Frostion Sorry, "alpha" was changed to "saturation" due to a limitation. So you'll want this: smallMap.territory.saturation=0.1

@redrum I have the bug @wirkey is describing if I load his savegame with 1.9.0.0.10498. I don't have it if I load it with 1.9.0.0.9687. I don't seem to be able to reproduce the issue starting a new game (with the map currently downloadable (the one still having "costPU"; not the new version I'm still waiting to have it merged), that I assume is the same one as the @wirkey savegame), with 1.9.0.0.10498 or 1.9.0.0.9687, playing it without reloading.

I have added total mobilized: Country Manpower on Entry into War End of War Peak Number Total Mobilized Albania 13,000 13,000 13,000 Australia 91,700 575,100 575,100 993,000 Belgium 600,000 650,000 650,000 900,000 Bulgaria 160,000 450,000 450,000 1,011,000 Canada 63,100 759,800 759,800 1,100,000 China 2,500,000 5,000,000 5,700,000 14,000,000 Denmark 6,600 6,600 6,600 Finland 127,800 270,000 270,000 270,000 France 900,000 437,000 2,680,000 2,680,000 Germany 3,180,000 7,800,000 9,500,000 17,900,000 Greece 430,000 540,000 540,000 Hungary 80,000 210,000 210,000 210,000 India 197,000 2,159,700 2,159,700 2,581,800 Italy 1,899,600 259,100 2,563,000 2,563,000 Japan 1,700,000 7,200,000 7,200,000 9,100,000 Netherlands 270,000 400,000 400,000 400,000 New Zealand 13,800 192,800 192,800 192,800 Norway 25,000 25,000 90,000 Poland 1,200,000 250,000 250,000 2,400,000 Rumania 686,000 370,000 1,225,000 1,225,000 South Africa 19,000 198,000 250,000 UK 681,000 4,683,000 4,683,000 5,896,000 USA 5,413,000 11,877,000 11,877,000 16,354,000 USSR 9,000,000 12,400,000 13,200,000 13,200,000 Yugoslavia 150,000 800,000 800,000 1,500,000