HowTo:Add Cargo - Revision history

Nikai: navbar

2010-09-19T11:20:44Z

navbar

Melonhead: /* Walkthrough */

2007-04-11T23:56:26Z

‎Walkthrough

Melonhead: /* Walkthrough */

2007-04-11T23:55:47Z

‎Walkthrough

Melonhead: /* Contraband */

2007-04-11T23:51:15Z

‎Contraband

Melonhead at 23:49, 11 April 2007

2007-04-11T23:49:07Z

Melonhead at 02:52, 24 January 2007

2007-01-24T02:52:08Z

Melonhead at 02:50, 24 January 2007

2007-01-24T02:50:44Z

Melonhead at 02:48, 24 January 2007

2007-01-24T02:48:14Z

Melonhead at 02:44, 24 January 2007

2007-01-24T02:44:52Z

Melonhead at 02:44, 24 January 2007

2007-01-24T02:44:23Z

← Older revision		Revision as of 11:20, 19 September 2010
Line 1:		Line 1:
		+	{{NAV_Manual \|
		+	\| previous=[[HowTo:Add Upgrades\|Add Upgrades]]
		+	\| up=[[HowTos]]
		+	\| next=[[HowTo:Edit Systems\|Edit Systems]]
		+	}}
		+	----
	Note: In Vega Strike, there is an ongoing effort to make the economy much more sophisticated. This file discusses adding cargo using Privateer 1.2 as the example, but Vega Strike 0.4.3 should be similar. [{{Fixme}} Add VS data.]		Note: In Vega Strike, there is an ongoing effort to make the economy much more sophisticated. This file discusses adding cargo using Privateer 1.2 as the example, but Vega Strike 0.4.3 should be similar. [{{Fixme}} Add VS data.]

Line 62:		Line 68:

	You also need to decide where your cargo will be available and where buyers will take it off your hands. At bases which supply your cargo, use the Price% multiplier to set the price low. At bases which demand your cargo, use the Price multiplier to set the price higher. At both, set the price variability using Pricestddev%. Be careful not to create a price differential that’s unbalancing. At bases which supply your cargo, use the Quant% and Quantstddev% to determine how much of your commodity is normally available, and the range this quantity can vary. These entries go in units.csv, in the cargo_import column for each base. Note that if you don’t put an entry for your cargo at a base, then that base will buy your cargo at the base price set in master_parts_list.csv. If you don't want a base to by a cargo item, you must give that item a zero price multiplier in the cargo_import column for that base type.		You also need to decide where your cargo will be available and where buyers will take it off your hands. At bases which supply your cargo, use the Price% multiplier to set the price low. At bases which demand your cargo, use the Price multiplier to set the price higher. At both, set the price variability using Pricestddev%. Be careful not to create a price differential that’s unbalancing. At bases which supply your cargo, use the Quant% and Quantstddev% to determine how much of your commodity is normally available, and the range this quantity can vary. These entries go in units.csv, in the cargo_import column for each base. Note that if you don’t put an entry for your cargo at a base, then that base will buy your cargo at the base price set in master_parts_list.csv. If you don't want a base to by a cargo item, you must give that item a zero price multiplier in the cargo_import column for that base type.
		+	----
		+	{{NAV_Manual \|
		+	\| previous=[[HowTo:Add Upgrades\|Add Upgrades]]
		+	\| up=[[HowTos]]
		+	\| next=[[HowTo:Edit Systems\|Edit Systems]]
		+	}}

← Older revision		Revision as of 23:56, 11 April 2007
Line 61:		Line 61:
	So, to add a new type of cargo, you need a couple ideas, and one file. You need a name for your new cargo, the base price, a description, and the picture to be displayed in Commodity Exchange. These go in master_parts_list.csv. The graphics file goes in /textures/cargo.		So, to add a new type of cargo, you need a couple ideas, and one file. You need a name for your new cargo, the base price, a description, and the picture to be displayed in Commodity Exchange. These go in master_parts_list.csv. The graphics file goes in /textures/cargo.

−	You also need to decide where your cargo will be available and where buyers will take it off your hands. At bases which supply your cargo, use the Price% multiplier to set the price low. At bases which demand your cargo, use the Price multiplier to set the price higher. At both, set the price variability using Pricestddev%. Be careful not to create a price differential that’s unbalancing. At bases which supply your cargo, use the Quant% and Quantstddev% to determine how much of your commodity is normally available, and the range this quantity can vary. These entries go in units.csv, in the cargo_import column for each base. Note that if you don’t put an entry for your cargo at a base, then that base will buy your cargo at the base price set in master_parts_list.csv. If you don't want a base to by a cargo item, you must ~~specify~~ that item ~~with~~ a zero price multiplier in the cargo_import column for that base type.	+	You also need to decide where your cargo will be available and where buyers will take it off your hands. At bases which supply your cargo, use the Price% multiplier to set the price low. At bases which demand your cargo, use the Price multiplier to set the price higher. At both, set the price variability using Pricestddev%. Be careful not to create a price differential that’s unbalancing. At bases which supply your cargo, use the Quant% and Quantstddev% to determine how much of your commodity is normally available, and the range this quantity can vary. These entries go in units.csv, in the cargo_import column for each base. Note that if you don’t put an entry for your cargo at a base, then that base will buy your cargo at the base price set in master_parts_list.csv. If you don't want a base to by a cargo item, you must give that item a zero price multiplier in the cargo_import column for that base type.

← Older revision		Revision as of 23:55, 11 April 2007
Line 61:		Line 61:
	So, to add a new type of cargo, you need a couple ideas, and one file. You need a name for your new cargo, the base price, a description, and the picture to be displayed in Commodity Exchange. These go in master_parts_list.csv. The graphics file goes in /textures/cargo.		So, to add a new type of cargo, you need a couple ideas, and one file. You need a name for your new cargo, the base price, a description, and the picture to be displayed in Commodity Exchange. These go in master_parts_list.csv. The graphics file goes in /textures/cargo.

−	You also need to decide where your cargo will be available and where buyers will take it off your hands. At bases which supply your cargo, use the Price% multiplier to set the price low. At bases which demand your cargo, use the Price multiplier to set the price higher. At both, set the price variability using Pricestddev%. Be careful not to create a price differential that’s unbalancing. At bases which supply your cargo, use the Quant% and Quantstddev% to determine how much of your commodity is normally available, and the range this quantity can vary. These entries go in units.csv, in the cargo_import column for each base. Note that if you don’t put an entry for your cargo at a base, then that base will buy your cargo at the base price set in master_parts_list.csv.	+	You also need to decide where your cargo will be available and where buyers will take it off your hands. At bases which supply your cargo, use the Price% multiplier to set the price low. At bases which demand your cargo, use the Price multiplier to set the price higher. At both, set the price variability using Pricestddev%. Be careful not to create a price differential that’s unbalancing. At bases which supply your cargo, use the Quant% and Quantstddev% to determine how much of your commodity is normally available, and the range this quantity can vary. These entries go in units.csv, in the cargo_import column for each base. Note that if you don’t put an entry for your cargo at a base, then that base will buy your cargo at the base price set in master_parts_list.csv. If you don't want a base to by a cargo item, you must specify that item with a zero price multiplier in the cargo_import column for that base type.

← Older revision		Revision as of 23:51, 11 April 2007
Line 35:		Line 35:


−	In order to make cargo into Contraband, you must do two things. First add the “''Contraband''” keyword in front of the cargo name. Then, add that cargo type to list of contraband items found in the lines “''Contraband_xxx''” in units.csv, column DB, cargo_import. There are types of contraband for Confed, Militia, and Retros. Note that if you misspell Contraband, that cargo won’t be available for purchase at the usual places.[{{Fixme}} There are several fields in the contraband description, including a 1 at the end. Determine what these are for--e.g. do any determine the probability of the contraband being detected?]	+	In order to make cargo into Contraband, you must do two things. First, add the “''Contraband''” keyword in front of the cargo name in master_parts_list.csv. Then, add that cargo type to list of contraband items found in the lines “''Contraband_xxx''” in units.csv, column DB, cargo_import. There are types of contraband specified for Confed, Militia, and Retros. Note that if you misspell Contraband, that cargo won’t be available for purchase at the usual places.[{{Fixme}} There are several fields in the contraband description, including a 1 at the end. Determine what these are for--e.g. do any determine the probability of the contraband being detected?]


Line 41:		Line 41:


		+	[{{Fixme}} Identify differences for Vega Strike.]

	== Cargo outside the ship ==		== Cargo outside the ship ==

@@ Line 32: / Line 32: @@
-Note that you can’t just add the “''Contraband''” keyword in front of regular cargo.  It APPEARS that the cargo is not classified as contraband. [{{FIXME}} How is cargo made into contraband?]  Note that if you misspell Contraband, that cargo won’t be available for purchase at the usual places.
+== Contraband ==
 In addition to the “Contraband” keyword, “''Starships''” indicates what types of vessels are available for purchase at this location, e.g. {starships/Merchant/Light;1;;12;6}, and the keyword “''upgrades''” indicates what ship upgrades will be available at the Ship Dealer, e.g. {upgrades/Reactors/Medium;1;.1;3;1}.
-'''Cargo outside the ship.'''
 That just leaves the image to be used for cargo floating in space.  All cargo is loaded in small containers, so all cargo types floating outside a ship are displayed the same.  The graphics to be used are specified by the row entry “'''generic_cargo_upgrades'''” in units.csv.

@@ Line 1: / Line 1: @@
-Note:  In Vega Strike, there is an ongoing effort to make the economy much more sophisticated.  This file discusses adding cargo using Privateer 1.2 as the example, but Vega Strike 0.4.3 should be similar.  {{{Fixme}} Add VS data.}
+Note:  In Vega Strike, there is an ongoing effort to make the economy much more sophisticated.  This file discusses adding cargo using Privateer 1.2 as the example, but Vega Strike 0.4.3 should be similar.  [{{Fixme}} Add VS data.]
 ----
@@ Line 9: / Line 9: @@
 The '''description''' includes the location and name of the graphics file to be for displaying this cargo in the ''Commodity Exchange'', e.g. cargo\tungsten.png.  These are located off the \textures directory (so this example points to \textures\cargo\tungsten.png).  Note that the graphics files may be .png or .jpg format, and should be 128 x 128 pixels.  If the graphic is not 128 x 128 pixels, there will be a noticeable loss of performance while that cargo item is selected in Commodity Exchange.
-In Privateer, whether or not cargo is available for sale at bases/planets is determined by the units.csv file, column DB, “'''cargo_import'''”.  Recall the second row in units.csv provides a basic definition for the format of the various entries.  In Vega Strike 0.4.3, the same data is in column DA.  Column DB, “cargo” is different, and describes various attributes of the cargo itself.  {{{Fixme}} Add description of differences for VS.]
+In Privateer, whether or not cargo is available for sale at bases/planets is determined by the units.csv file, column DB, “'''cargo_import'''”.  Recall the second row in units.csv provides a basic definition for the format of the various entries.  In Vega Strike 0.4.3, the same data is in column DA.  Column DB, “cargo” is different, and describes various attributes of the cargo itself.  [{{Fixme}} Add description of differences for VS.]
@@ Line 21: / Line 21: @@
-“'''Pricestddev%'''” is a modifier for the price at a base/planet, so the price varies a little.  It doesn’t appear to actually be standard deviation.  The equation to determine the overall price is approximated by:  Absolute value(Price% - (Price% * Pricestddev%))  The minimal amount of price variation in Privateer 1.2 is due to the very small values of Pricestddev%.  When nonzero, typical values of Pricestddev% are 0.02 to 0.05 in Privateer 1.2, leading to variations of just a few tenths of a credit. {{Fixme}} Add Vega Strike info for comparison.
+“'''Pricestddev%'''” is a modifier for the price at a base/planet, so the price varies a little.  It doesn’t appear to actually be standard deviation.  The equation to determine the overall price is approximated by:  Absolute value(Price% - (Price% * Pricestddev%))  The minimal amount of price variation in Privateer 1.2 is due to the very small values of Pricestddev%.  When nonzero, typical values of Pricestddev% are 0.02 to 0.05 in Privateer 1.2, leading to variations of just a few tenths of a credit. [{{Fixme}} Add Vega Strike info for comparison.]

@@ Line 1: / Line 1: @@
-Note:  In Vega Strike, there is an ongoing effort to make the economy much more sophisticated.  This file discusses adding cargo using Privateer 1.2 as the example, but Vega Strike 0.4.3 should be similar.  {{Fixme}} add VS data
+Note:  In Vega Strike, there is an ongoing effort to make the economy much more sophisticated.  This file discusses adding cargo using Privateer 1.2 as the example, but Vega Strike 0.4.3 should be similar.  {{Fixme}} Add VS data.
 ----
@@ Line 9: / Line 9: @@
 The '''description''' includes the location and name of the graphics file to be for displaying this cargo in the ''Commodity Exchange'', e.g. cargo\tungsten.png.  These are located off the \textures directory (so this example points to \textures\cargo\tungsten.png).  Note that the graphics files may be .png or .jpg format, and should be 128 x 128 pixels.  If the graphic is not 128 x 128 pixels, there will be a noticeable loss of performance while that cargo item is selected in Commodity Exchange.
-In Privateer, whether or not cargo is available for sale at bases/planets is determined by the units.csv file, column DB, “'''cargo_import'''”.  Recall the second row in units.csv provides a basic definition for the format of the various entries.  In Vega Strike 0.4.3, the same data is in column DA.  Column DB, “cargo” is different, and describes various attributes of the cargo itself.  {{FIXME}} add description of differences for VS.]
+In Privateer, whether or not cargo is available for sale at bases/planets is determined by the units.csv file, column DB, “'''cargo_import'''”.  Recall the second row in units.csv provides a basic definition for the format of the various entries.  In Vega Strike 0.4.3, the same data is in column DA.  Column DB, “cargo” is different, and describes various attributes of the cargo itself.  {{Fixme}} Add description of differences for VS.
@@ Line 21: / Line 21: @@
-“'''Pricestddev%'''” is a modifier for the price at a base/planet, so the price varies a little.  It doesn’t appear to actually be standard deviation.  The equation to determine the overall price is approximated by:  Absolute value(Price% - (Price% * Pricestddev%))  The minimal amount of price variation in Privateer 1.2 is due to the very small values of Pricestddev%.  When nonzero, typical values of Pricestddev% are 0.02 to 0.05 in Privateer 1.2, leading to variations of just a few tenths of a credit. [FIXME Add Vega Strike info for comparison.]
+“'''Pricestddev%'''” is a modifier for the price at a base/planet, so the price varies a little.  It doesn’t appear to actually be standard deviation.  The equation to determine the overall price is approximated by:  Absolute value(Price% - (Price% * Pricestddev%))  The minimal amount of price variation in Privateer 1.2 is due to the very small values of Pricestddev%.  When nonzero, typical values of Pricestddev% are 0.02 to 0.05 in Privateer 1.2, leading to variations of just a few tenths of a credit. {{Fixme}} Add Vega Strike info for comparison.
@@ Line 32: / Line 32: @@
-Note that you can’t just add the “''Contraband''” keyword in front of regular cargo.  Rather than the cargo being classified as contraband, it won’t be available for purchase at the usual places.  [FIXME—why is this?]
+Note that you can’t just add the “''Contraband''” keyword in front of regular cargo.  It APPEARS that the cargo is not classified as contraband. {{{FIXME}} How is cargo made into contraband?]  Note that if you misspell Contraband, that cargo won’t be available for purchase at the usual places.
 In addition to the “Contraband” keyword, “''Starships''” indicates what types of vessels are available for purchase at this location, e.g. {starships/Merchant/Light;1;;12;6}, and the keyword “''upgrades''” indicates what ship upgrades will be available at the Ship Dealer, e.g. {upgrades/Reactors/Medium;1;.1;3;1}.
@@ Line 40: / Line 40: @@
 That just leaves the image to be used for cargo floating in space.  All cargo is loaded in small containers, so all cargo types floating outside a ship are displayed the same.  The graphics to be used are specified by the row entry “'''generic_cargo_upgrades'''” in units.csv.
-[FIXME What is the units.csv entry “cargo” used for?]
+{{Fixme}} What is the units.csv entry “cargo” used for?
 In units,csv, the Directory column specifies the location of the files called out in other columns.  For generic_cargo_upgrades, this location is ./objects/cargo, which is found under the /units folder.  Hud_image specifies the file name of the sprite used to display cargo boxes on your ship’s MFD (i.e. cargo-hud.spr).  Mesh specifies the file name of the 3D .bfxm mesh to be used.  Here, then, the container mesh is located in \units\objects\cargo, generic_cargo.bfxm.  The entry in the Name column does not appear to be used; when an object is targeted on the MFD, the entry in the “Key” column is displayed.

← Older revision		Revision as of 02:44, 24 January 2007
Line 9:		Line 9:
	The '''description''' includes the location and name of the graphics file to be for displaying this cargo in the ''Commodity Exchange'', e.g. cargo\tungsten.png. These are located off the \textures directory (so this example points to \textures\cargo\tungsten.png). Note that the graphics files may be .png or .jpg format, and should be 128 x 128 pixels. If the graphic is not 128 x 128 pixels, there will be a noticeable loss of performance while that cargo item is selected in Commodity Exchange.		The '''description''' includes the location and name of the graphics file to be for displaying this cargo in the ''Commodity Exchange'', e.g. cargo\tungsten.png. These are located off the \textures directory (so this example points to \textures\cargo\tungsten.png). Note that the graphics files may be .png or .jpg format, and should be 128 x 128 pixels. If the graphic is not 128 x 128 pixels, there will be a noticeable loss of performance while that cargo item is selected in Commodity Exchange.

−	In Privateer, whether or not cargo is available for sale at bases/planets is determined by the units.csv file, column DB, “'''cargo_import'''”. Recall the second row in units.csv provides a basic definition for the format of the various entries. In Vega Strike 0.4.3, the same data is in column DA. Column DB, “cargo” is different, and describes various attributes of the cargo itself. [FIXME add description of differences for VS.]	+	In Privateer, whether or not cargo is available for sale at bases/planets is determined by the units.csv file, column DB, “'''cargo_import'''”. Recall the second row in units.csv provides a basic definition for the format of the various entries. In Vega Strike 0.4.3, the same data is in column DA. Column DB, “cargo” is different, and describes various attributes of the cargo itself. {{FIXME}} add description of differences for VS.]