Project

General

Profile

Actions

Feature #652

closed

MaxRegionTiles requirement at C/Adjacent ranges

Added by Alina Lenk 6 months ago. Updated 6 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
General
Target version:
Start date:
05/19/2024
Due date:
% Done:

0%

Estimated time:

Description

Expand the new requirement type from #629 by adding "at most this many (cardinally) adjacent tiles of the same continent/ocean as the tile itself" functionality, for use in unhardcoding the "bay" rule of #588.


Files


Related issues 2 (0 open2 closed)

Blocks Feature #588: Unhardcode tile claimability rulesClosedAlina Lenk05/11/2024

Actions
Blocked by Feature #629: Continent/ocean size requirementClosedAlina Lenk05/16/2024

Actions
Actions #1

Updated by Alina Lenk 6 months ago

  • Blocks Feature #588: Unhardcode tile claimability rules added
Actions #2

Updated by Alina Lenk 6 months ago

  • Blocked by Feature #629: Continent/ocean size requirement added
Actions #4

Updated by Marko Lindqvist 6 months ago

Would next natural expansion be MaxTerrainClassPct requirement, to unhardcode ocean <-> land transformation rules?

Actions #5

Updated by Alina Lenk 6 months ago

Marko Lindqvist wrote in #note-4:

Would next natural expansion be MaxTerrainClassPct requirement, to unhardcode ocean <-> land transformation rules?

With topology requirements to determine whether we're hex or not, plus a bit of crunching numbers, this is already possible with this (albeit less convenient). Oh, except at the edge of the map maybe, haven't checked how that's handled currently. So we might need that.

Then again, part of this whole #588 operation I'm doing right now is in the hopes of one day unhardcoding and allowing more than two terrain classes (early uses would be putting Lake and Inaccessibel terrain in separate classes). At that point "at most 85% the current terrain class" would no longer mean "at least 15% the new terrain class"; our unhardcoding efforts now might lead to a world where we can only express the former, but not the latter, which is what we really want. So maybe we should hold off on unhardcoding that until we have a satisfactory solution.

Actions #6

Updated by Alina Lenk 6 months ago

Updated patch to use #656 instead of using raw adjc_dirlist_iterate.

Actions #7

Updated by Alina Lenk 6 months ago

Updated patch; based on the new version of #629 and now with metaknowledge.

Actions #8

Updated by Alina Lenk 6 months ago

  • Status changed from In Review to Closed
Actions

Also available in: Atom PDF