@hamzeh-hammad

Depends on the map and whos playing. But a 4 player of suitable games can be completed in 8hrs if no big delays. However they can go much longer on occasion.

@alkexr You might want to try it though,we're always looking for new developers 😉

@redrum sweet! never knew that 🙂 TY

@bluebeatarezzo I would recommend you just join the lobby and play in a bot. For now.

Regarding attacking infrastructures, the last time I checked the behaviour was that sending an attacking infrastructure in an undefended territory conquers the territory; instead, if a battle is done and both attackers and defenders are destroyer, attacking infrastructures are conquered by the defender.
I think this should be harmonized, in that either the attacking infrastructures conquer the territory in both cases or are gifted to the defender in both cases.
I think an attacking infrastructure alone should not conquer a territory, but getting conquered, in doing so.
I've not tested this behaviour recently.

@beelee works in 9480 or newer they have fixed that

@lottaway1 I believe so here are the unit images that should be used when those techs are researched:

Bomber: https://github.com/triplea-maps/world_war_ii_v3/blob/master/map/units/Americans/bomber.png
Heavy Bomber: https://github.com/triplea-maps/world_war_ii_v3/blob/master/map/units/Americans/bomber_hb.png
Fighter: https://github.com/triplea-maps/world_war_ii_v3/blob/master/map/units/Americans/fighter.png
Long Range Fighter: https://github.com/triplea-maps/world_war_ii_v3/blob/master/map/units/Americans/fighter_lr.png

Yeah would be nice if the air unit validation didn't take this attribute ("movementLimit" for playerAttachments) into consideration until the player tries to click done for CM or NCM. Only then giving a prompt, if the player tries to end the CM or NCM phase while in a territory that is over the stacking limit set by "movementLimit".
The message displayed currently is "Units can not go over stacking limit". If air tries to fly over.

This is most likely gonna need to be a feature request, unless you wanna break other parts of the logic using triggers.

@roiex Nice work roiex ! Is way better : )

@Cernel yea seeing it now is the way it used to be . I think : ) My recall is ...unreliable : )

@prastle yea my sound used to throw errors when it was on. Took me a while to figure out why people were getting annoyed with me in the lobby. : )

Fortunately I think it's fixed because I don't get errors anymore

@ayoross Well I opened a PR a day ago that tries to cleanup the code: https://github.com/triplea-game/triplea/pull/2950
However we're running into the exact same issue you just described. (By we I mean @ssoloff and myself.)
We're currently assuming it has something to do with concurrency issues.
However in case we get everything working it does currently not look like the memory footprint is going down.
Looks like this requires much more changes than a small algorithm 😕

Thanks for the offer, @cmmiles. I believe this particular issue has been resolved because we have at least one dev on the team who's done some extensive testing with a Mac since I posted this. However, Mac is still probably the platform that gets the least amount of test coverage, in general, so if you happen to notice anything strange, please don't hesitate to report it in the Help & Questions category here or by opening a new issue on GitHub.

@general_zod said in How to use kamikaze tokens:

end of Japan's enemy's combat-

Thanks! I did see that. So a combat situation has to exist; not just enemy units in a kamikaze sea zone. Thanks for the reply!

The property that controls tech token removal listed below.

"Remove All Tech Tokens At End Of Turn" value="false"

Many maps either have it as optional in game setup or preset to false. Which means you keep tech tokens if you miss.

Although a few maps still play old school rules, where if you miss your roll, your token gets taken away.

@prastle

There's quite a few map specific rules to Big World 2 actually.

@prastle updated with a few more links

@hepps
🙂

@ssoloff Fixed this issue yesterday (for me it's today, but whatever ^^)
So it should be fixed in the latest pre-release

Thank You

I'll give it another go