Races and vesselData.xml

You want to use hullID="6000", not hulltype there. Alternately, use hultype="Cube"

*wags his finger at Thom*

ATTRIBUTE: hulltype
VALID: 0-? (corresponds to the unique hull ID in vesselData.xml)

The docs need to be updated. :)

So what are hullkeys then?

hullkeys are the things that specify the particular kind of ship after racekeys. In your example, racekey="Borg enemy" would specify any enemy with preference given to Borg races. hullkey="Cube large" would specify any enemy within the racekey types with the broadtype or subtype large, with preference given to Cube types. It's a priority and generalization thing - hullID makes the missions pretty inflexible to changes to the vesselData file - once you specify 6000, by god it's gonna call 6000 regardless if its a cube, a bird of prey, or nothing at all (which will crash Artemis). hullKeys and raceKeys make it so you can modify the vesselData file (or use it with a different mod!) and it looks for the tags you specify. If it doesn't find 'em, then it broadens the search until it finds a valid object.

<create type="enemy" x="50000.0" y="0.0" z="50000.0" raceKeys="Borg enemy" hullKeys="Cube large" name="BFD 59-482" fleetnumber="2"/> - calls a Cube of Borg. If there aren't any Cube types, it calls a large of Borg. If there aren't any Borg, it calls a Cube of enemy. If neither Cube nor Borg, it calls a large of enemy.

NB - your tags should be single words, since "Bird of Prey" and "Bird of Death" could both be called on "Bird" - I've had some bizarre replacements show up :)

<create type="enemy" x="50000.0" y="0.0" z="50000.0" raceKeys="Borg enemy" hullKeys="Cube large" name="BFD 59-482" fleetnumber="2"/> - calls a Cube of Borg. If there aren't any Cube types, it calls a large of Borg. If there aren't any Borg, it calls a Cube of enemy. If neither Cube nor Borg, it calls a large of enemy.

I gotcha. Thanks. :)

So it's working now, but when I get into the manual fire mode, it's the artemis again. Any idea how to fix that?

Do you have the script folder with all of your models and artwork copied to all of the consoles? Maybe the Weapons console doesn't have the Borg artwork so it's showing something else?

It's running all on the same computer. So yeah. It has it.

Hm. That's.... bizarre. I've never run into that. Admittedly, we tend to leave it in autofire on beams, so I'm not sure if it actually has come up. Do the impusle/weapon points look like they line up on Artemis? or are they off the model somewhere in space (as if it were on an enormous cube...)

I just see the weapon hardpoint. That may be because of my code though.

Well, if all the points are specified, they should all show up. Did you pick the points off using the ship editor tool? or manually via some other method?

Also, what's efficiency = "1.0" ? I've never seen or used that in my vesselData file.

There's a ship editor tool?

I dunno. It was there for the last ship.

http://artemiswiki.pbworks.com/w/page/52152707/Mods

The ship editor tool by Thom - you place texture files you want into the ShipTextures folder, then open the program. Load up the .dxs of your choice and go to town. It generates .snt files for player ships and allows modification of said files. it has a surface picker that allows you to click anywhere on the front half of the ship and it'll find the most exterior point, typically for locating beam and torpedo ports, engine ports, drone ports, etc. If the point you want is on the back half, click on the centerline of the ship and navigate with wsad. Invaluable tool, I use it for all of my ships

The mission editor tool is also very useful for mission scripting - it handles a lot of the lower level syntax stuff and has plain word declarations so something like
<create type="enemy" x="50000.0" y="0.0" z="48000.0" angle="0.0" name="EN2" raceKeys="Borg enemy" hullKeys="Cube large" fleetnumber="1" />
is created with
Create enemy at point (50000.0, 0.0, 48000.0) with bearing 0.0 degrees with name "EN2" and race/hull keys "Borg enemy" "Cube large" with fleet number 1

The bold parts are clickable and either pull up a list of commands or a box to type in information. It handles the new expressions, although it doesn't check them for validity. Extremely useful, developed some time ago by Hissatsu and maintained by RussJudge. http://px2owffng8.tal.ki/20130130/artemis-mission-editor-2347979/

There's a space map to check where things are, actions and conditions for events, comments and folders - really very useful. You can load in the mission script you've already created and it'll open it, arrange it and offer some error checking.

Hrm. I'll check it out. Thanks. :)