Changes between Version 26 and Version 27 of Ticket #1834


Ignore:
Timestamp:
Oct 17, 2017, 7:46:02 PM (7 years ago)
Author:
elexis
Comment:

As stated above, all maps except Caledonian Meadows and Wild Lake support all map sizes already.

So currently the gamesetup supports persistance of user settings when changing any other setting. This meets the current user expectation from random map settings - players browse through the map while having the player assignments, victory condition - and for this matter mapsize persisted.

For example players willing to play a "pizza" game on a tiny map size and then see which map they would ideally like to play. They can chose freely until they come across that one map that resets the size to Normal.

Multiply that with any gamesetting we have and we end up with scenario and skirmish maps which overwrite each setting when changing the map, making it impossible to fine-tune settings in consensus.

So this feature would have devastating effects on the gamesetup in my opinion.

So these two maps must be fixed to work with all mapsizes instead. We already have a way to prevent resource collisions (tile classes + retry loops). One should expect that even on tiny maps with limiting area there is enough space for starting bases. But if a map is exotic, it could still fallback to nomad starting units instead of dropping setting independence in the gamesetup.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1834

    • Property Status newclosed
    • Property Summary [PATCH] Add player caps for random maps by map size option to their json files handled in gamesetup.js[PATCH] Allow random maps to restrict the gamesetup mapsize choice
    • Property Milestone Backlog
    • Property Resolutionwontfix