Region is undefined in this case, so the mission will be using default regions. This also means it won't spawn the proper terrain...
In general, I advise to analyze how it's done in Piratez. First, you define your mission region, eg.:
- type: REGION_MONSTER_HUNT_MEGASCORPION
missionZones:
-
- [356, 356, -23, -23, -100]
- [6.13, 6.13, -30.6, -30.6, -100]
- [13.71, 13.71, -26.76, -26.76, -100]
- [27, 27, -21, -21, -100]
- [40.24, 40.24, -25, -25, -100]
- [20, 20, 24, 24, -100]
- [20.84, 20.84, 27.42, 27.42, -100]
- [48.5, 48.5, -9.2, -9.2, -100]
- [255, 255, -32, -32, -100]
- [249, 249, -32.5, -32.5, -100]
- [244, 244, -40, -40, -100]
- [292, 292, 41, 41, -100]
- [72, 72, -25, -25, -100]
- [63, 63, -33, -33, -100]
- [35, 35, -28.55, -28.55, -100]
- [49.269, 49.269, -26.88, -26.88, -100]
This specific region requires spawnZone: 0, since only the first block of coordinates is defined. Also -100 is arbitrary, any negative value other than -1 (already used for normal Terrors) will do.
Next, you need to define that -100 texture. Texture links to desired alienDeployment, which, in turn, liks to desired terrains (which I presume you have):
- id: -100
deployments:
STR_LOC_MONSTER_HUNT_MEGASCORPION: 100
Finally, you need to tell the mission script to use your terrain, in this example:
- type: monsterHunt1
firstMonth: 0
lastMonth: 15
missionWeights:
0:
STR_LOC_MONSTER_HUNT_MEGASCORPION: 100
regionWeights:
0:
REGION_MONSTER_HUNT_MEGASCORPION: 100
useTable: false
researchTriggers:
STR_MONSTER_HUNT: true
executionOdds: 75
startDelay: 8000
As you can see, this one links to proper mission, proper region, and (which you might not need) is time-constrained and blocked by a research.