The set_player_carried_type mission scripting command defines a single seat ship to be carried inside another player ship. Note that this command cannot change a ship once created. It merely changes the list that is used when a ship is created so, unlike most commands, you must use this command before you create the player ship.
Attribute
|
Valid Values
|
Optional?
|
Description
|
name
|
Text
|
Optional
|
|
hullID
|
0-?
|
Optional
|
The unique hull ID in vesselData.xml
|
raceKeys
|
Text (corresponds to hullRace name and keys in vesselData.xml)
|
Optional
|
|
hullKeys
|
Text (corresponds to vessel className and broadType in vesselData.xml)
|
Optional
|
|
player_slot
|
0-7 (corresponds to the 8 player capital (not fighter) ships allowed in the game)
|
|
This player_slot value defines which carrier to put this single seat ship on.
|
bay_slot
|
0-?
|
|
The bay number inside the carrier ship. Slot 0 is extra, and is reserved for a shuttle, so most ships can only carry one shuttle.
|
These values override the player's applicable selections at start up time. Any attributes that are not set will revert to the player's choice. If either raceKeys or hullKeys are specified, they must both be specified. This will often force a single seat craft of a different race to appear on the player ship. For instance, you cannot force a shuttle to be an LR Shuttle without forcing it to be a TSN LR Shuttle, which will replace an Adventure shuttle on a Pirate ship. Likewise, there is no way to specify Bombers on a ship without specifying TSN or Zim Bombers.
Comments (0)
You don't have permission to comment on this page.