What a ware describes#
A ware links an ID, name and description to price, production and restrictions. A ship ware also identifies its hull macro. A library price may differ from the final UI quote because market state, personal conditions and equipment can affect the total.
Change the base price#
The installed X4 9.00 ware ship_arg_s_fighter_02_a has min, average and max price attributes. The example patches them to 70000, 80000 and 90000. Keep min ≤ average ≤ max. This changes base data, not a guaranteed equipped-ship purchase quote.
<diff>
<replace sel="/wares/ware[@id='ship_arg_s_fighter_02_a']/price/@min">70000</replace>
<replace sel="/wares/ware[@id='ship_arg_s_fighter_02_a']/price/@average">80000</replace>
<replace sel="/wares/ware[@id='ship_arg_s_fighter_02_a']/price/@max">90000</replace>
</diff>A new ware#
Create a unique ID and text references. Connect a ship ware to its new macro, and base recipes and restrictions on a working analogue. Resources and ships have different economic roles. Transport class and volume affect storage compatibility, not only a menu label.
The production chain#
Separate credit value, input resources, output amount and cycle duration. Production needs the appropriate module and registrations, not only a price entry. Verify display, recipe, actual consumption and production, then persistence and compatibility.