If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.
You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!

command_create

Page history last edited by Ryan McMullan 3 years, 7 months ago

The create mission scripting command creates objects in the game. There are two variants, one that creates named objects, and one that creates unnamed objects. Note that other commands that reference an object by name, such as set_relative_position for example, cannot be called in the same event (or start block) as the create command that creates the object. Instead, the script must put them in a separate event that executes once that object exists (e.g., using the if_exists condition). The valid attributes of the command depend what is being created.

For creating named objects:

Attribute	Valid Values	Optional?	Description
name	text	Optional for all but station	The name given to the object, should be unique and will be used to address this object by other commands. A station with unspecified name will crash the game. Once created, names are compared case-insensitively so names should be unique regardless of case. To have two objects appear to have the same name, they can have a different number of trailing spaces.
type	station, player, enemy, neutral, anomaly, blackHole, monster, genericMesh, whale	Mandatory	The type of object we are creating. Depending on the type, additional attributes may be required. (see below) Note that "whale" is deprecated, but still functions identically to creating a "monster" of monsterType=1.
use_gm_position	anything, only presence of this attribute is checked for	Optional (use instead of x, y, z)	If attribute is present (any value will suffice), the x and z attributes are defined by GM console position.
x	0 to 100000 (float)	Mandatory	x-coordinate where object will be created, in distance left of the right edge of the map. Invalid value will crash the game. Unspecified value will crash the game.
y	-100000 to 100000 (float)	Mandatory	y-coordinate where object will be created. Invalid value will crash the game. Unspecified value will crash the game.
z	0 to 100000 (float)	Mandatory	z-coordinate where object will be created, in distance down from the top edge of the map. Invalid value will crash the game. Unspecified value will crash the game.
angle	0-360	Optional	Initial orientation, in degrees, of created object. 0 is facing upwards, value increases clockwise. Works with objects of type player, enemy, monster, and neutral, but NOT anomaly, black hole, generic mesh, or station. (For all types, one can still use set_object_property to set angle after creation, but keep in mind the value is calculated differently.) There was previously a report that this was not functioning with enemy and neutral ships in v2.4 but in v2.7.5 those work as expected.
hullID	0-?		DEPRECATED - use raceKeys and hullKeys Corresponds to the unique hullID in vesselData.xml.
fleetnumber	-1 to 99 (integer)	only used for enemy and neutral	This number is used to group ships together, so that they may move and react together. If you use a fleet number that's illegal, crashes and wierd graphical glitches will occur. -1 means no fleet.
raceKeys	text	only used for player, enemy, neutral, and station	Corresponds to hullRace name and keys in vesselData.xml. See below for more info. If neither hullID nor valid combination of race/hull keys is specified, game will crash.
hullKeys	text	only used for player, enemy, neutral, and station	Corresponds to vessel className and broadType in vesselData.xml. See below for more info. If neither hullID nor valid combination of race/hull keys is specified, game will crash.
sideValue	0-31 0: no side 1 (default): enemy 2: friendly and players	Optional	Neutral ships on side 2 start double-scanned. Neutral ships on other sides start single-scanned.

Some named object types have additional attributes as noted in subsections below.

Example:

Creates a space station named DS1 at position (052000, 000000, 005000) (roughly in the middle top of the play area) that is friendly to the player.

RaceKeys and HullKeys

Creating ships and assigning hulls to them is now more flexible. The old way was to use the hulltype attribute to specify the exact ID of the hull (from the vesselData.xml file), for example:

That way is still supported, but no longer recommended. Instead, when you create a ship using the 'create' command, use the raceKeys and hullKeys to pick the best hull indirectly. For instance (using vesselData.xml 1.60 as a reference), if you want to create an enemy that's a Torgoth Battleship, you can use

This will make an enemy Torgoth Battleship. However, what if your script is being played by someone who's modified the vesselData.xml, or a later version of the game has changed vesselData.xml, or the player is playing a modded game? Your script might not find the Torgoth race or its Battleship hull. So let's broaden the keys to allow for alternatives:

Now if the Torgoth race isn't found, a race with the "enemy support" key will be. If a Battleship isn't found, the "medium" broadtype will be. Now your script stands a much better chance of working, no matter what changes have happened to the vesselData.xml file. Keys are compared using a case-insensitive comparison.

Scanned Level of ships

Level 0 means no info is visible, level 1 means the ship type is visible, and level 2 means the shield frequencies, specials, and captain text is visible. Unfortunately, there is currently no way to directly set a ship's scanned level. You can conditionally check a ship's scan level with the if_scan_level command (example: <if_scan_level name="Debris" side="2" comparator="GREATER_EQUAL" value="1" />).

A ship's initial scanned level is as follows:

all ships on the player's side always have scanned level 2
neutral ships on any other side start with scanned level 1
enemy ships on any other side start with scanned level 0

Using set_side_value to change a ship from the player's side to another side only changes the scanned level if done immediately upon creation. Otherwise, it will stay at scanned level 2.

Additional attributes when the named object is of type “player”:

Attribute	Valid Values	Optional?	Description
player_slot	0-7 (corresponds to the 8 player ships allowed in the game)	Optional for first ship, Mandatory for others. (use this with or instead of a "name" attribute)	Player ships can be referenced by player_slot even if not created with this attribute.
accent_color	0-99	Optional	Overrides the player selected accent color
warp	yes or no	Optional	Sets Warp Drive if "yes", or Jump Drive if "no". This attribute is ignored if the jump attribute is also present.
jump	yes or no	Optional	Sets Jump Drive if "yes", or Warp Drive if "no".

Examples:

<create type="player" name="Artemis" x="50000" y="0" z="50000" angle="90 /> (prevents override of ship's name)

<create type="player" player_slot="1" x="58542" y="0" z="51042" angle="0" /> (creates a second player ship in slot #2)

If only one player ship is created, ships in the other player slots will be spawned when the crew logs in to the running server with that ship. The crew will not be allowed to log in to the extra ship until the server is running. At least one player ship should be created in the start block.

If more than one player ship is created in the script, player_slot must be specified for all but the first, or the ship will be created, but the players will be unable to log into it.

Additional attributes when the named object is of type “genericMesh”:

Attribute	Valid Values	Optional?	Description
meshFileName	text		Path to a dxs DeleD mesh file. If it begins with dat\ this is a path relative to the game exe dir. If it only contains a file name it is relative to the mission directory. So, game will look for "dat\1.dxs" in Artemis\dat folder and for "1.dxs" in Artemis\dat\Missions\MISS_XXX folder
textureFileName	text		Path to a png texture file. If it begins with dat\ this is a path relative to the game exe dir. If it only contains a file name it is relative to the mission directory. So, game will look for "dat\1.png" in Artemis\dat folder and for "1.png" in Artemis\dat\Missions\MISS_XXX folder
hullRace	text
hullType	text
fakeShieldsFront	-1-1000		The front shield strength read by sensors for the object. Defaults to -1, which means no fake shields, if only the fakeShieldsFront is positive, the generic looks like a station.
fakeShieldsRear	-1-1000		The rear shield strength read by sensors for the object. Defaults to -1, which means no fake shields, if only the fakeShieldsFront is positive, the generic looks like a station.
hasFakeShldFreq	0 or 1
colorRed	0.0-1.0		These three values represent the color used on the LRS screen and Science console to display the mesh and its name. Default value is 1.0, 0.0, 1.0 (pink). You can use 0.0, 0.0, 0.0 to hide the object from the map (technically, it's still there, drawn in black, but its very hard to see).
colorGreen	0.0-1.0
colorBlue	0.0-1.0

Examples:

Additional attributes when the named object is of type “anomaly”:

Attribute	Valid Values	Optional?	Description
pickupType	0-7 0 = HiDens Power Cell 1 = Vigoranium Nodule 2 = Cetrocite Crystal 3 = Lateral Array 4 = Tauron Focuser 5 = Infusion P-Coil 6 = Carapaction Coil 7 = Secret Code Case 8 = Bio Beacon (in v2.7.0, see below) 9 = Space Junk (in v2.7.0, see below)	Optional, defaults to 0 (the original "energy" anomaly)	See Upgrades for details. The Bio Beacon and Space Junk only appear rarely in non-scripted modes.
beaconMonsterType	0-8 (v2.7.0 and later) 0 = TYPHON (classic space monster) 1 = WHALE 2 = SHARK 3 = DRAGON 4 = PIRA (Piranha) 5 = CHARYBDIS 6 = NSECT 7 = JELLY (in v2.7.0) or WRECK (prior to v2.7.0) 8 = WRECK (in v2.7.0)	only used for Bio Beacon
beaconEffect	0-1 (v2.7.0 and later) 0 = ATTRACT 1 = REPEL	only used for Bio Beacon

Examples:

Additional attributes when the named object is of type “monster”:

Attribute	Valid Values	Optional?	Description
age	1 = Young 2 = Mature 3 = Ancient	Optional	Added in v2.7.1
monsterType	0-8 0 = TYPHON (classic space monster) 1 = WHALE 2 = SHARK 3 = DRAGON 4 = PIRA (Piranha) 5 = CHARYBDIS 6 = NSECT 7 = JELLY (in v2.7.0) or WRECK (prior to v2.7.0) 8 = WRECK (in v2.7.0)	Optional, defaults to 0 (TYPHON)
podnumber	0-9	Only used for whales and piranhas	If you use a pod number that's illegal, crashes and weird graphical glitches will occur.

Examples:

(The last two commands will create the exact same Space Whale.)

For creating UN-named objects:

Attribute	Valid Values	Optional?	Description
type	nebulas, asteroids, mines		type of unnamed objects to be created
nebType	1 = Purple 2 = Blue 3 = Yellow	Only used for nebulas	If present, sets the nebula type. Different types display as different colors. (Added in v2.6.3)
count	0 to 500 (integer)		number of unnamed objects to be created. You can use values over 500 just fine, despite game manual specifying 500 as the max value
radius	0 100000		the distance around the startX, startY, startZ point in which these objects are created. If this is equal to 0, objects are created in a line defined by start and end coordinates. If this is greater than 0, objects are created in a circle defined by start coordinate and this radius
randomRange	0 to 100000		random spread range, defines how far will unnamed objects spread from the line or the circle.
use_gm_position	anything		If attribute is present (any value will suffice), the startx and startz attributes are defined by GM console position.
startX	0 to 100000 (float)		Invalid values will not crash the game
startY	-100000 to 100000 (float)
startZ	0 to 100000 (float)		Invalid values will not crash the game
endX	0 to 100000 (float)		Invalid values will not crash the game
endY	-100000 to 100000 (float)
endZ	0 to 100000 (float)		Invalid values will not crash the game
randomSeed	0 to big number (int)		The number used to generate the random distribution of objects.
startAngle	integer		Used to spawn objects in an arc instead of a full circle. If both are not specified, objects are spawned in a circle or a line. If one is specified, and other isn't, unspecified value is considered to be 0. Arc will always go from the lowest of the two angles to the highest clockwise, so if you want to have, for example, an arc from 330 to 30, you have to specify -30 and 30, otherwise you'll get an arc from 30 to 330. You can have an arc longer than 2piradius (like, if you have angles -180 and 360, you'll have twice as many objects in the left half circle than the right, because the arc goes 540 degrees, overlapping.
endAngle	integer

Examples:

Extended examples (version 2.1.1):

Damcon teams rejuvenated

Comments (0)

You don't have permission to comment on this page.

To join this workspace, request access.

Already have an account? Log in!

Loading…

Loading…

command_create

For creating named objects:

RaceKeys and HullKeys

Additional attributes when the named object is of type “player”:

Additional attributes when the named object is of type “genericMesh”:

Additional attributes when the named object is of type “anomaly”:

Additional attributes when the named object is of type “monster”:

For creating UN-named objects:

command_create

Page Tools

Insert links

Comments (0)

Join this workspace

Navigator

SideBar

Recent Activity