MissileSpawn: Difference between revisions
No edit summary |
Millennium (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
Can be set to 'yes' or 'no' and determines whether or not this AircraftType is actually a spawned missile rather than a true aircraft, as the Dreadnaught and V3 spawn these types. If set to yes, this means (perhaps along with other functionality) that the kills scored by the spawned object count towards the veterancy of the spawning object (for example, the V3 Launcher can become Veteran or Elite by the kills done by the V3 Rockets it spawns). Another apparent function is that no more instances of an object with MissileSpawn=yes are spawned once the spawning object is no longer itself attacking (for example, an Aircraft Carrier will spawn fighters at a target even when having been ordered to move, as long as the target is within range, opposed to the V3 Launcher, which stops spawning when moving). | |||
Can be set to 'yes' or 'no' and determines whether or not this AircraftType is actually a spawned missile rather than a true aircraft, as the Dreadnaught and V3 spawn these types. | |||
Revision as of 17:56, 20 March 2009
Can be set to 'yes' or 'no' and determines whether or not this AircraftType is actually a spawned missile rather than a true aircraft, as the Dreadnaught and V3 spawn these types. If set to yes, this means (perhaps along with other functionality) that the kills scored by the spawned object count towards the veterancy of the spawning object (for example, the V3 Launcher can become Veteran or Elite by the kills done by the V3 Rockets it spawns). Another apparent function is that no more instances of an object with MissileSpawn=yes are spawned once the spawning object is no longer itself attacking (for example, an Aircraft Carrier will spawn fighters at a target even when having been ordered to move, as long as the target is within range, opposed to the V3 Launcher, which stops spawning when moving).