I still want control where the mission appears. I dont want THIS type mission left up to the scripter as to what hex if any it shows up in.
Consider this, since I do not want it appearing in Base hexes, then it would seem that under the Artifex 'Base Tab' using either of these terrain types: 'Listening Post' or 'Weapons Platform' could be added together with 'shipping Lane' to allow for greater specificity where the mission shows. If those two combined dont cut it, then we can add in another terrain type like 'Asteroid Base1, 2 or 3' Since I do not want the mission showing on a Planet hex, then this terrain type would suit me fine under the Artifex 'Planet Tab'.
Bottom line is that there are certain 10 DV hexes on my map that are begging for a good convoy raid mission to show. As a map maker and server designer, I'd like the tools available to me so I can get this type mission to show up where I want it to.
Here are the possible terrain settings:
kTerrainShift = 0,
kAsteroidHex = 1 << 0,
kNebulaHex = 1 << 1,
kBlackHoleHex = 1 << 2,
kShippingLaneHex = 1 << 3,
kDustCloudsHex = 1 << 4,
kEmptySpaceHex = 1 << 5,
kAnyTerrainHex = kAsteroidHex | kNebulaHex | kBlackHoleHex | kShippingLaneHex | kDustCloudsHex | kEmptySpaceHex,
kBaseShift = 6,
kBaseStationHex = 1 << 6,
kBattleStationHex = 1 << 7,
kStarbaseHex = 1 << 8,
kBaseWeaponsPlatformHex = 1 << 9,
kBaseListeningPostHex = 1 << 10,
kAnyBaseHex = kBaseStationHex | kBattleStationHex | kStarbaseHex | kBaseWeaponsPlatformHex | kBaseListeningPostHex,
kPlanetShift = 11,
kHomeworldHex = 1 << 11,
kCoreworldHex = 1 << 12,
kAsteroidBaseHex = 1 << 13,
kColonyHex = 1 << 14,
kAnyPlanetHex = kHomeworldHex | kCoreworldHex | kAsteroidBaseHex | kColonyHex,
Determining whether some of them actually work like the kHomeworldHex, kBaseStationHex, kAnyTerrainHex, et al. or don't work like kShippingLaneHex will take a tedious trial and error process to figure out.
Retiring from scripting is the smartest move of 2004 pour moi. Just look at all the free time I have now. *snicker*