Continent variable naming

[scient]

I've been making progress on the Path class and as part of that working on the Continent structure. It's essentially metrics on each internal map region. For example, the first value of the struct is a tile count and another is how many pods are available. For unk_3, I pretty much know what it is but I'm leaving it alone until I wrap my head around faction sites vs goals. I just finished an initial draft of the the function that sets up unk_6 (it's essentially a bitfield for ocean regions connected to the specific land region/continent). I'm fairly certain unk_5 is padding since I haven't found any references to it.

Then there is unk_2 that I'm having trouble coming up with a name for it. It's specifically land tiles that meet certain criteria. It's used by enemy_move() in a bunch of places to determine doing various actions (this is largest function, so hard to discern what's going on). The good news is the exact criteria can be viewed here. Essentially, it's a count of land tiles, that are rainy or moist, flat or rolling without fungus for a Continent. Not sure why that last check is thrown in there for sea fungus but it's never considered. I thought it might be something related to how easy to traverse or move through a particular region but I'm blanking on a good way to name it. Anyway, thought I would open it up for discussion.

[EmpathCrawler]

clear_terrain
unobstructed_terrain
open_terrain

[Induktio]

I think open_terrain is a good choice here. Supposedly it means any non-rocky, non-fungused tile where you need only 1 movement point to travel to it.

The fact that uint8_t unk_6[8] has 64 bits while ocean regions are assigned 64 different IDs also seems to line up pretty well. Maybe the bits are assigned in the same order than the table for facilities built in a base?

[scient]

I like open_terrain as well. Thanks for input! Will update my source with it.

It's likely used by AI to prioritize exploration for continents that have less movement penalties.

The fact that uint8_t unk_6[8] has 64 bits while ocean regions are assigned 64 different IDs also seems to line up pretty well. Maybe the bits are assigned in the same order than the table for facilities built in a base?

Yeah, it's using exact same method as base facilities table. It's set up here. I was going to name it something like "oceanAccess" once I clean up code and make sure I'm understanding exactly what it's doing.

[EmpathCrawler]

I'm helping!