---
title: Adding a new ship
summary: From a variant of an existing hull to a separate ship: macro, indexes, ware, text and availability.
section: ships
kind: guide
status: reference
tags: ["X4","modding","adding","ship"]
sources: ["https://wiki.egosoft.com/X4%20Foundations%20Wiki/Modding%20Support/Assets%20Modding/Community%20Guides/Making%20custom%20ships/","https://gist.github.com/MattMcFarland/1282329f83f88f1b98520c5e2ec491a2"]
---
## Choose the kind of change


To change an existing ship, use a [property patch](wiki:editing-parameters); a new macro and ware are unnecessary. To add a variant, reuse a model but create a macro and ware with unique IDs. To create a new hull, prepare a model and component first, then connect the same data chain: [Blender to game](wiki:ship-models).



## Start from a working analogue


Choose a ship of a similar class and role in your game version. For a first variant, reuse its component and change properties. Copy the original macro locally into your extension workspace. Elite Vanguard uses component `ship_arg_s_fighter_02`; a variant can change its macro name while retaining that model reference. Original complete macros are not distributed here; obtain them from your installation. Examples below are fragments, not a complete working ship.



## Connect the files


Use a unique `wiki_scout_macro` name, retain required component, connections, physics and properties, register the macro in the index, create a ware referring to it and add [text IDs](wiki:localization). The index path below must match your extension layout. Base the ware on a suitable ship in the installed version and change its ID, text references and component reference. The ware points to a macro; that is distinct from the macro's model component reference.




```text
wiki_ship/
├── content.xml
├── assets/units/size_s/macros/wiki_scout_macro.xml
├── index/macros.xml
├── libraries/wares.xml
└── t/0001-l044.xml
```




```xml
<diff>
  <add sel="/index">
    <entry name="wiki_scout_macro"
           value="extensions\wiki_ship\assets\units\size_s\macros\wiki_scout_macro" />
  </add>
</diff>
```




```xml
<component ref="wiki_scout_macro" />
```

## Make the ship available


Macro registration, ware existence and shipyard availability are separate steps. Configure price, production, ownership/faction rules and a blueprint acquisition route using a current analogue. Ship groups and faction configuration may also matter. First confirm creation and the correct hull, then test blueprint availability and purchase separately. One owner entry does not prove availability at every shipyard.



## Verify the new variant


Confirm that the original and variant have distinct IDs; names, descriptions and classes display correctly; engines, shields, weapons, cockpit and docking connections work; mass, hull, cargo and crew capacity are correct; and equipment and names survive save/load. Continue with [macros](wiki:ship-macros), [wares](wiki:wares-and-prices) and [equipment](wiki:ship-equipment).