phosit

The starting position and the lakes are similar to "Pyrenean Sierra". Maybe you can base your map on that.

I don't understand the argument. The difficulty of AIs is independent of teams.

What's the point of more teams? When there are more then 4 teams at least one player is a lone in a team. So it has the same effect as to assign no team to that player.

I think that the current Egypt(3v3) should be turned, so that the fertile land is in the foreground and the mountains in the back.

Nice that there are already two starting positions for Petra

Removing an invocation of `pickRandom` doesn't invalidate another. (Worst case is that in DE the AI might not be serializeable.) I tried to bisect it but wasn't successful there are always like 10 units idle.

Sorry for the late reply. Maybe you can find something in this PR. In there are many commits, so bisect should help a lot.

I can't reproduce that. But I noticed that the map isn't revealed after loading.

That's indeed an issue. Thanks for reporting.

That's because it first chooses the placement, without knowing whether the map supports it.

To fix the issue, the map has to somehow expose the restrictions. Those restrictions could then also be read by the random selection algorithm. At least that's how I think of it.

Oh, so you choose random as placement - I understand now. I think it would be a hard to delay the random selection to the mapgen script. One would also have to change replay-summary: there it shouldn't be displayed as "random". The more complete solution is the one stated in the ticket.

I don't know of a remaining issue of persistent map settings. Also the name of a game should be causally unrelated to the placement. I know #8148 which is related especially this link.

I'd say "Must Have"s and "Release Blocker"s should have the next release as milestone. The others should be backlogged.

@Stan`