Project

General

Profile

Actions

Feature #629

closed

Continent/ocean size requirement

Added by Alina Lenk about 2 months ago. Updated about 1 month ago.

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

0%

Estimated time:

Description

Add a requirement type for maximum continent size or ocean size. Given the number of other things that just say "continent" to also mean "or ocean", we could just call this "MaxContinentSize"; but we could also give it a more neutral name, e.g. "MaxRegionSize" (like CityTile's "Bordering TClass Region").


Files


Related issues 3 (0 open3 closed)

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

Actions
Blocked by Feature #642: client: keep track of continent and ocean sizesClosedAlina Lenk05/18/2024

Actions
Blocks Feature #652: MaxRegionTiles requirement at C/Adjacent rangesClosedAlina Lenk05/19/2024

Actions
Actions #1

Updated by Alina Lenk about 2 months ago

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

Updated by Alina Lenk about 2 months ago

Doing this requires implementing a client-side understanding of continent sizes (with only partial map knowledge), as well as storage for the computed information in common code (probably the civ_map struct).

Actions #3

Updated by Alina Lenk about 2 months ago

  • Blocked by Feature #642: client: keep track of continent and ocean sizes added
Actions #4

Updated by Alina Lenk about 2 months ago

Patch depends on #602.

Decided to make this a MaxNumTiles requirement at Continent range, since that seems more likely to be extendable to other ranges (e.g. city). I didn't see much use for a continent size requirement at c/adjacent ranges ("are we on a small island or next to a small lake?"); maybe a little more if we were to make those work differently from normal and exclude the continent of the tile itself (just "are we next to a small lake?"), but even that didn't seem too useful. If it turns out we do want something like that, we can always add it later.

Actions #5

Updated by Alina Lenk about 2 months ago

I just realized we can use this for another part of #588, i.e. for something needed now rather than something possibly useful in the future: The "ocean tile with at most two other adjacent ocean tiles" (bay) part. So I changed the name of the requirement type to "MaxRegionTiles", i.e. "at most this many tiles of the same region as the target tile" so we can make it do that at C/Adjacent ranges.

Actions #6

Updated by Alina Lenk about 2 months ago

  • Blocks Feature #652: MaxRegionTiles requirement at C/Adjacent ranges added
Actions #7

Updated by Alina Lenk about 1 month ago

Updated patch; mainly pulling forward some changes I made for #652 (i.e. doing things right the first time).

Actions #9

Updated by Alina Lenk about 1 month ago

  • Status changed from In Review to Closed
Actions

Also available in: Atom PDF