[DONE] [Suggestion] Changing alien base deployment by time passed

[Nord]

I have a request for my new mod idea:
Changing alien base deployment by time passed.
E.g. by the end of month.
So if you leave base untouched, it can develop and grow.

I can now create new bases with new deployments based on current month, but what i want - is to allow old bases to grow.

[Meridian]

Seems nice.
Todolisted.

[Solarius Scorch]

Very nice indeed. But what exactly would grow? I understand the base size and the number of enemies, but anything else? (Defensive UFOs maybe, if they are coded? I don't really have any ideas.)

[Meridian]

Anything deployment related.

PS: Defensive UFOs are already able to change over time.

[Hobbes]

Me likes this!

[ohartenstein23]

I'd be interested in this too. Can I add to this the option to tie map generation RNG to a seed based on mission latitude and longitude, like I did for base defense missions? That way, if you go to a base multiple times, it could look the same instead of complete remodeling every time.

[Meridian]

Done.
Alien bases can now upgrade their deployment, after the first game month... and based on their current age in months.

Ruleset example:

Code: [Select]

alienDeployments:
  - type: STR_ALIEN_BASE_ASSAULT
    alienBaseUpgrades:
      0:
        STR_ALIEN_BASE_ASSAULT: 100
      3:
        STR_ALIEN_BASE_ASSAULT_OLDBASE_1: 50
        STR_ALIEN_BASE_ASSAULT_OLDBASE_2: 50
      6:
        STR_ALIEN_BASE_ASSAULT_VERYOLDBASE: 100

Change happens once every month, for each alien base separately.

Affected:
 - alien battlescape deployment
 - starting conditions
 - base detection range
 - base hunt missions type and frequency
 - base supply mission type and frequency
 - geoscape scoring
 - base's saving/loading ID (depends on markerName, see disclaimer)

Not affected:
 - counter of generated supply missions
 - alien race
 - corresponding infiltrated country

DISCLAIMER:
All upgrades (deployments) must use the same "markerName" as the original deployment!
Otherwise weird shit will happpen... you've been warned.

[Nord]

Wonderful.
But what is used: current base age in months or global months?

[Meridian]

Wonderful.
But what is used: current base age in months or global months?

Global number of game months... is that OK?

[Nord]

Global number of game months... is that OK?

Well, i think that count age of each base is far more complicate to do, so global months should be just fine.

[Solarius Scorch]

Global number of game months... is that OK?

But if the idea is to make the base grow over time, then it should be based on the base age, not campaign age, no?
If I am mistaken and it's actually not about base age, then sorry in advance.

[Meridian]

I don't care, both are doable... let me know.

[Nord]

I don't care, both are doable... let me know.

If it is not too hard, base age will be better.
Thanks. 

[Meridian]

If it is not too hard, base age will be better.
Thanks. 

Done.

Base age (in months) is calculated as current game month minus month when the base spawned.

So if the base spawned on 31.1.2000 and it is now 2.2.2000, the base is 1 month old.

PS: month when the base was discovered is irrelevant

[Nord]

Done.

Base age (in months) is calculated as current game month minus month when the base spawned.

Great!
The syntaxis has been not changed?