New ship cant buy weapons in equipment sales SOLVED

[Rustybolts]

Finally got to test drive my creation unfortunately a few bugs discovered the main one being that although new weapons are available to buy in equipment section, once selected it wont give position to mount them.
Is it because i have not set weapon_position_ in shipdata.plist?
Thought i would ask as i have already set the ship_facings at 15 in the shipyard.plist

[Rustybolts]

I've set weapon positions and yet it still has same problem really unsure of where to go from here. Do i have to set weapon positions in non player part of shipdata aswell as player?
*edit* have set weapon positions in player and non player yet still can't mount any new weapons (sigh!!)*edit*

[Thargoid]

Presuming you're just talking about lasers, do you have them listed under optional equipment in the shipyard.plist for the ship in question?

The example below is from my player Manta Ray, which can use any of the trunk lasers but only has forward and rear mounts (weapon_facings = 3). The arrows indicate the relevant lines, and aren't in the original file:

Code: Select all

	"aquatics_mantaRay-player" =
	{
		"chance" = 0.25;
		"optional_equipment" = (
			"EQ_ECM",
			"EQ_CARGO_BAY",
			"EQ_PASSENGER_BERTH",
			"EQ_FUEL_INJECTION",
			"EQ_FUEL_SCOOPS",
			"EQ_ESCAPE_POD",
			"EQ_ENERGY_BOMB",
			"EQ_ENERGY_UNIT",
			"EQ_NAVAL_ENERGY_UNIT",
			"EQ_DOCK_COMP",
			"EQ_WEAPON_PULSE_LASER",             <------
			"EQ_WEAPON_BEAM_LASER",             <------
			"EQ_WEAPON_MINING_LASER",             <------
			"EQ_WEAPON_MILITARY_LASER",             <------
			"EQ_WEAPON_TWIN_PLASMA_CANNON",             <------
			"EQ_SCANNER_SHOW_MISSILE_TARGET",
			"EQ_MULTI_TARGET",
			"EQ_TARGET_MEMORY",
			"EQ_GAL_DRIVE",
			"EQ_ADVANCED_COMPASS",
			"EQ_ADVANCED_NAVIGATIONAL_ARRAY",
			"EQ_SHIELD_BOOSTER",
			"EQ_NAVAL_SHIELD_BOOSTER",
			"EQ_MILITARY_JAMMER",
			"EQ_MILITARY_SCANNER_FILTER",
			"EQ_HEAT_SHIELD"
		);
		price = 150000;
		standard_equipment = {
			extras = ();
			forward_weapon_type = "EQ_WEAPON_BEAM_LASER";
			missiles = 2;
		};
		techlevel = 8;
		weapon_facings = 3;
	};

[Rustybolts]

Presuming you're just talking about lasers, do you have them listed under optional equipment in the shipyard.plist for the ship in question?

The example below is from my player Manta Ray, which can use any of the trunk lasers but only has forward and rear mounts (weapon_facings = 3). The arrows indicate the relevant lines, and aren't in the original file:

Code: Select all

	"aquatics_mantaRay-player" =
	{
		"chance" = 0.25;
		"optional_equipment" = (
			"EQ_ECM",
			"EQ_CARGO_BAY",
			"EQ_PASSENGER_BERTH",
			"EQ_FUEL_INJECTION",
			"EQ_FUEL_SCOOPS",
			"EQ_ESCAPE_POD",
			"EQ_ENERGY_BOMB",
			"EQ_ENERGY_UNIT",
			"EQ_NAVAL_ENERGY_UNIT",
			"EQ_DOCK_COMP",
			"EQ_WEAPON_PULSE_LASER",             <------
			"EQ_WEAPON_BEAM_LASER",             <------
			"EQ_WEAPON_MINING_LASER",             <------
			"EQ_WEAPON_MILITARY_LASER",             <------
			"EQ_WEAPON_TWIN_PLASMA_CANNON",             <------
			"EQ_SCANNER_SHOW_MISSILE_TARGET",
			"EQ_MULTI_TARGET",
			"EQ_TARGET_MEMORY",
			"EQ_GAL_DRIVE",
			"EQ_ADVANCED_COMPASS",
			"EQ_ADVANCED_NAVIGATIONAL_ARRAY",
			"EQ_SHIELD_BOOSTER",
			"EQ_NAVAL_SHIELD_BOOSTER",
			"EQ_MILITARY_JAMMER",
			"EQ_MILITARY_SCANNER_FILTER",
			"EQ_HEAT_SHIELD"
		);
		price = 150000;
		standard_equipment = {
			extras = ();
			forward_weapon_type = "EQ_WEAPON_BEAM_LASER";
			missiles = 2;
		};
		techlevel = 8;
		weapon_facings = 3;
	};

Code: Select all

	<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>ste-player</key>
	<dict>
		<key>chance</key>
		<real>0.75</real>
		<key>techlevel</key>
		<integer>5</integer>
		<key>optional_equipment</key>
		<array>
            <string>EQ_CARGO_BAY</string>
			<string>EQ_ECM</string>
			<string>EQ_FUEL_SCOOPS</string>
			<string>EQ_ESCAPE_POD</string>
			<string>EQ_ENERGY_BOMB</string>
			<string>EQ_ENERGY_UNIT</string>
			<string>EQ_NAVAL_ENERGY_UNIT</string>
			<string>EQ_PASSENGER_BERTH</string>
			<string>EQ_WEAPON_PULSE_LASER</string>
			<string>EQ_WEAPON_BEAM_LASER</string>
			<string>EQ_WEAPON_MINING_LASER</string>
			<string>EQ_WEAPON_MILITARY_LASER</string>
			<string>EQ_FUEL_INJECTION</string>
			<string>EQ_SCANNER_SHOW_MISSILE_TARGET</string>
			<string>EQ_MULTI_TARGET</string>
			<string>EQ_GAL_DRIVE</string>
			<string>EQ_SHIELD_BOOSTER</string>
			<string>EQ_NAVAL_SHIELD_BOOSTER</string>
		</array>
		<key>price</key>
		<integer>185000</integer>
		<key>standard_equipment</key>
		<dict>
		<key>weapon_facings</key>
		<integer>3</integer>
			<key>extras</key>
			<array>
				<string>EQ_DOCK_COMP</string>
				<string>EQ_ADVANCED_COMPASS</string>
			</array>
			<key>forward_weapon_type</key>
			<string>EQ_WEAPON_BEAM_LASER</string>
			<key>missiles</key>
			<integer>3</integer>
		</dict>
		<key>techlevel</key>
		<integer>5</integer>
	</dict>
	<key>stey-player</key>
	<dict>
		<key>chance</key>
		<real>0.75</real>
		<key>techlevel</key>
		<integer>5</integer>
		<key>optional_equipment</key>
		<array>
            <string>EQ_CARGO_BAY</string>
			<string>EQ_ECM</string>
			<string>EQ_FUEL_SCOOPS</string>
			<string>EQ_ESCAPE_POD</string>
			<string>EQ_ENERGY_BOMB</string>
			<string>EQ_ENERGY_UNIT</string>
			<string>EQ_NAVAL_ENERGY_UNIT</string>
			<string>EQ_PASSENGER_BERTH</string>
			<string>EQ_WEAPON_PULSE_LASER</string>
			<string>EQ_WEAPON_BEAM_LASER</string>
			<string>EQ_WEAPON_MINING_LASER</string>
			<string>EQ_WEAPON_MILITARY_LASER</string>
			<string>EQ_FUEL_INJECTION</string>
			<string>EQ_SCANNER_SHOW_MISSILE_TARGET</string>
			<string>EQ_MULTI_TARGET</string>
			<string>EQ_GAL_DRIVE</string>
			<string>EQ_SHIELD_BOOSTER</string>
			<string>EQ_NAVAL_SHIELD_BOOSTER</string>
		</array>
		<key>price</key>
		<integer>185000</integer>
		<key>standard_equipment</key>
		<dict>
		<key>weapon_facings</key>
		<integer>3</integer>
			<key>extras</key>
			<array>
				<string>EQ_DOCK_COMP</string>
				<string>EQ_ADVANCED_COMPASS</string>
			</array>
			<key>forward_weapon_type</key>
			<string>EQ_WEAPON_BEAM_LASER</string>
			<key>missiles</key>
			<integer>3</integer>
		</dict>
		<key>techlevel</key>
		<integer>5</integer>
	</dict>
	<key>ster-player</key>
	<dict>
		<key>chance</key>
		<real>0.75</real>
		<key>techlevel</key>
		<integer>5</integer>
		<key>optional_equipment</key>
		<array>
            <string>EQ_CARGO_BAY</string>
			<string>EQ_ECM</string>
			<string>EQ_FUEL_SCOOPS</string>
			<string>EQ_ESCAPE_POD</string>
			<string>EQ_ENERGY_BOMB</string>
			<string>EQ_ENERGY_UNIT</string>
			<string>EQ_NAVAL_ENERGY_UNIT</string>
			<string>EQ_PASSENGER_BERTH</string>
			<string>EQ_WEAPON_PULSE_LASER</string>
			<string>EQ_WEAPON_BEAM_LASER</string>
			<string>EQ_WEAPON_MINING_LASER</string>
			<string>EQ_WEAPON_MILITARY_LASER</string>
			<string>EQ_FUEL_INJECTION</string>
			<string>EQ_SCANNER_SHOW_MISSILE_TARGET</string>
			<string>EQ_MULTI_TARGET</string>
			<string>EQ_GAL_DRIVE</string>
			<string>EQ_SHIELD_BOOSTER</string>
			<string>EQ_NAVAL_SHIELD_BOOSTER</string>
		</array>
		<key>price</key>
		<integer>185000</integer>
		<key>standard_equipment</key>
		<dict>
		<key>weapon_facings</key>
		<integer>3</integer>
			<key>extras</key>
			<array>
				<string>EQ_DOCK_COMP</string>
				<string>EQ_ADVANCED_COMPASS</string>
			</array>
			<key>forward_weapon_type</key>
			<string>EQ_WEAPON_BEAM_LASER</string>
			<key>missiles</key>
			<integer>3</integer>
		</dict>
		<key>techlevel</key>
		<integer>5</integer>
	</dict>
</dict>
</plist>

It lists as available to buy but when you select to buy it doesnt give you any option for where to mount it.

[Thargoid]

You've got the weapon_facings key entry inside the dict tags for the standard equipment. Move the entry down below the end of that dict tag pair, just above the tech level. It shouldn't be inside the standard equipment dictionary.

Look at my shipyard.plist to see an example of what I mean. Mine's in openstep format but you can see how the layout should be.

[Rustybolts]

Ill thank you now before i test it, i really didnt know where to look much appreciated

[Thargoid]

No probs. Hope it fixes the glitch.

That's why I prefer to code in openstep format. It's much simpler and clearer to follow and track (when indented properly) than the xml tags are (at least to my eyes). Although of course you lose on some of the apps that area around for automagically reviewing xml format files.

[Rustybolts]

Just to let you know tested and works. Brilliant mate nice one, For the past 3 hours i have been altering things that i shouldn't of been just for the slim chance it would work