Did this remove the possibility to start endless games and should have a hardcoded check for endless? (Noticed in D1240)

@mimo The conquest default as is is a problem, because it prevents endless games on random and skirmish maps.
But endless games are useful, for example for running survival of the fittest, jebel barkal or danubius with dryRun = true and debugLog = true in the trigger script shows a summary of the templates spawned.

So I (or you if you prefer) can either:

• remove the default Conquest and just have it log the loaded victory conditions (to inform the user that it's an endless game),
• or implement an --endless argument which would set an empty vector to victoryConditions (even if other victory conditions are passed)

In rP21108#29857, @elexis wrote:

@mimo The conquest default as is is a problem, because it prevents endless games on random and skirmish maps.
So I (or you if you prefer) can either:

• remove the default Conquest and just have it log the loaded victory conditions (to inform the user that it's an endless game),
• or implement an --endless argument which would set an empty vector to victoryConditions (even if other victory conditions are passed)

then maybe removing the default (equivalent to having endless as default) would be cleaner.

endless support readded in rP21474

In rP21108#30645, @bb wrote:

endless support readded in rP21474

Ah, nice, I forgot that.
(Then we only need to update the two descriptions in one a24 commit to fix both commits with missing victory condition description updates.)