month 1: one alien research mission, one terror mission. shooting down UFOs may trigger a retaliation mission.
month 2: one randomly selected mission, one terror mission, missions from previous months continue. shooting down UFOs may trigger a retaliation mission.
repeat until:
month 6: two randomly selected missions, one terror mission, missions from previous months continue. shooting down UFOs may trigger a retaliation mission.
repeat until:
month 12-ish: two randomly selected missions, one terror mission, one alien retaliation mission, missions from previous months continue. shooting down UFOs may trigger a retaliation mission.
Ok, I thought it just randomly selected and executed one wave, and the mission was already over.
If I try to describe the whole process, it's actually like this:
- a region is randomly selected;
the only factor influencing this choice is the "regionWeight" entry.
- mission STR_ALIEN_BUKKAKE is randomly selected;
the only factor influencing this choice is "missionWeight" for the mission in the selected region.
- after 'timer', the first listed wave is executed, and the related 'count' ufos are spawned;
- the ufo (or ufos) goes over its 'trajectory' until it reaches the exit point (last coordinate of trajectory);
- the first wave is over;
- after 'timer', the second listed wave is executed, and the related 'count' ufos are spawned;
- the ufo (or ufos) goes over its 'trajectory' until it reaches the exit point (last coordinate of trajectory);
- the second wave is over;
(..and so on, in descending order, until it gets at the bottom of the list of waves for the STR_ALIEN_BUKKAKE mission).
- the mission then is over;
if the month is not over: it waits the end of the month and then it starts the whole process from the beginning;
if the month already switched to the next: it immediately re-starts the process.
?