Make an alien mission start at a later month?

[robin]

Like this:

  - type: STR_SOME_NEW_MISSION
    points: 0
    raceWeights:
      0:
          STR_ALIENRACE: 0
      1:
          STR_ALIENRACE: 0
      3:
          STR_ALIENRACE: 100
      5:
          STR_ALIENRACE: 100
      7:
          STR_ALIENRACE: 100

..or like this:

  - type: STR_SOME_NEW_MISSION
    points: 0
    raceWeights:
      3:
          STR_ALIENRACE: 100
      5:
          STR_ALIENRACE: 100
      7:
          STR_ALIENRACE: 100

..?

Thanks.

[Falko]

the only way i thought off (but no time for test ) is this:
adding a small ufo befor the normal wave make this ufo appear only a (very) short amount of time
then add a huge wait time between the next wave like 3 months (in seconds?)

so you can be assured that this mission main ufos only appear after X time BUT if this mission is selected in the early months there will be less ufo to shut down during that time

also if the list of possible mission gets smaller until mission reset and the last mission generated is such a "waiting"-mission you will have a huge (time X) waiting period where nothing is happening until mission reset

[Aldorn]

I wondered same question and add one

Or like this ?

Code: [Select]

  - type: STR_SOME_NEW_MISSION
    points: 0
    raceWeights:
      12:
          STR_ALIENRACE: 100


[Hobbes]

Like this:

  - type: STR_SOME_NEW_MISSION
    points: 0
    raceWeights:
      0:
          STR_ALIENRACE: 0
      1:
          STR_ALIENRACE: 0
      3:
          STR_ALIENRACE: 100
      5:
          STR_ALIENRACE: 100
      7:
          STR_ALIENRACE: 100

..or like this:

  - type: STR_SOME_NEW_MISSION
    points: 0
    raceWeights:
      3:
          STR_ALIENRACE: 100
      5:
          STR_ALIENRACE: 100
      7:
          STR_ALIENRACE: 100

..?

Thanks.

I'd say it works either way, but it would be better to use the second one since you don't have unnecessary lines of code.

[Falko]

you will get a crash with such "solutions"
see the rulfile
it has 50 test missions (copies of harvester mission) +unbeatable cannon/interceptor+cheap hyuperwave/basecosts to check for missiontype
with

Code: [Select]

    raceWeights:
      0:
          STR_SECTOID: 0
          STR_MUTON: 0
          STR_FLOATER: 0
      12:
          STR_SECTOID: 30
          STR_MUTON: 30
          STR_FLOATER: 40
as soon as the february sometimes march you get a crash
if you put a race value >0 in the 0 sections the crash disappears
Edit: its the same result if you remove the "0:"section