Shipdata.plist - Revision history

Cholmondely: /* subentities */ Added link to range discussion on BB (has important details on functional range)

2021-12-23T13:20:45Z

‎subentities: Added link to range discussion on BB (has important details on functional range)

Tsoj: Fixed the maximum for weapon_range of ball_turret

2021-12-23T13:01:07Z

Fixed the maximum for weapon_range of ball_turret

Cholmondely: Added Links

2021-10-11T16:02:32Z

Added Links

Cholmondely: Added defining quote by cim

2021-08-26T20:14:02Z

Added defining quote by cim

Milo: added missing quotation mark pointed out by UK_Eliter

2021-07-15T02:53:51Z

added missing quotation mark pointed out by UK_Eliter

Cholmondely: /* heat_insulation */ Added link

2021-05-02T00:28:54Z

‎heat_insulation: Added link

Hiran: /* Format */

2021-04-27T21:20:15Z

‎Format

Hiran at 21:19, 27 April 2021

2021-04-27T21:19:21Z

Hiran at 21:12, 27 April 2021

2021-04-27T21:12:17Z

Milo: corrected and added more information about heat_insulation

2020-06-19T01:37:34Z

corrected and added more information about heat_insulation

@@ Line 894: / Line 894: @@
 * ''Static subentities'', the default type, are simply extra models. They are defined as separate shipdata.plist entries, so technically they’re ships, but they don’t have a mind of their own. If the main ship is [[#frangible|frangible]], static subentities can take damage and blow up separately from the main ship. They can also be individually exploded or removed by scripts.
 * ''Docks'' are recognized when setting up a station or carrier, and used to determine the station’s docking port parameters. After set-up, they work just like normal static subentities. The string "dock" in lowercase must be part of the old style name in order to get recognised as the dock subEntity.
 * ''Ball turrets'' turn to track the ship’s current target, and shoot plasma balls if the target is within range (6000 metres). A ball turret’s field of fire is a 157 ° cone centred on its original facing. Currently, ball turrets make no effort not to shoot their own ship, so it is up to the designer to ensure this field of fire is clear. Like a static subentity, a ball turret is based on a shipdata.plist entry so its appearance can be customized. Oolite provides a built-in shipdata entry for ball turrets called, imaginatively, '''ballturret'''.
 * ''Flashers'' are blobs which glow with a pulsating light. From Oolite 1.74 onwards, constant light will also be an option. Note that while flashers appear luminous – they are unaffected by shadows – they do not cast light on other objects.

@@ Line 934: / Line 934: @@
 | '''fire_rate''' || number || Interval between shots in seconds, for '''ball_turret''' subentities. Default: 0.5; minimum: 0.25.
 |-
-| '''weapon_range''' || number || Range for '''ball_turret''' subentities. Default: 6000; maximum 7500.
+| '''weapon_range''' || number || Range for '''ball_turret''' subentities. Default: 6000; maximum 7200.
 |-
 | '''weapon_energy''' || number || Weapon energy for '''ball_turret''' subentities. Default: 25; maximum 100.

@@ Line 1,343: / Line 1,343: @@
 --------------------------------------------------------------------------------
 [[Category:Oolite]]
 [[Category:Oolite scripting]]

← Older revision		Revision as of 20:14, 26 August 2021
Line 1:		Line 1:
		+	{{QuoteText\|Text=The shipdata.plist would be more accurately called objectdata nowadays - a "ship" in Oolite might be a ship, a station, a rock, basically any solid object smaller than a planet\|Source=([http://www.aegidian.org/bb/viewtopic.php?p=275475#p275475 Cim])}}
		+
	= Format =		= Format =
	Shipdata.plist is in [http://wiki.alioth.net/index.php/Property_list Property List] format.		Shipdata.plist is in [http://wiki.alioth.net/index.php/Property_list Property List] format.

@@ Line 1,240: / Line 1,240: @@
 If this key is omitted, the station will have no market. This is roughly equivalent to
- "market_definition = (
+ "market_definition" = (
+ 	{
  		"type" = "default";

@@ Line 438: / Line 438: @@
 == heat_insulation ==
 This real number gives the amount of heat insulation of a ship. Default is 1.0 (2.0 for ships equipped with EQ_HEAT_SHIELD). Values below 0.125 will be increased to that minimum. This parameter is only for NPC ships and stations. Player ships ignore this and always start with 1.0 heat insulation and can add an additional 1.0 (for a total of 2.0) with the ship equipment EQ_HEAT_SHIELD. Heat insulation for NPCs is only a factor when close to the sun. Energy damage does not cause overheating (because otherwise it would be too easy to overheat NPC ships with missiles or lasers), but it can raise ships' temperature to the maximum safe level. Overheating occurs when a ship's temperature exceeds the safe level, which is determined by the heat insulation level. External temperature is determined by distance from the sun. Larger suns are hotter. Suns that are going nova are, unsurprisingly, even warmer.
 Example:
  "heat_insulation" = "2.0";
-NPC ships launched from stations are given the same heat insulation as the station if the station's is greater than the ship's. Courier ships generated by the core system populator are given a heat insulation level of 6.0. Escort ships (if any) receive at least the same heat insulation as the ship they are escorting.
+NPC ships launched from stations are given the same heat insulation as the station if the station's is greater than the ship's. Courier ships generated by the core system populator are given a heat insulation level of 6.0. Escort ships (if any) receive at least the same heat insulation as the ship they are escorting. See [http://www.aegidian.org/bb/viewtopic.php?p=177357#p177357 BB Thread] (2012)
 Player ships use the same model as NPC ships for external temperature from the sun, but additionally simulate heat from air friction when inside planetary atmospheres, which is a factor that NPC ships ignore.

@@ Line 3: / Line 3: @@
 The shipdata document is a dictionary of ships. Example:
-  "rsvh_adder" = {
+      "rsvh_adder" = {
-    like_ship = "adder";
+        like_ship = "adder";
-    is_external_dependency = yes;
+        is_external_dependency = yes;
-    pilot = "oolite-hunter";
+        pilot = "oolite-hunter";
-    roles = "rrs-vicious-hunter(1)";
+        roles = "rrs-vicious-hunter(1)";
-    "missile_role" = "EQ_HARDENED_MISSILE";
+        "missile_role" = "EQ_HARDENED_MISSILE";
-	"script_info" = {
+    	"script_info" = {
-		"randomshipnames" = "hunter";
+    		"randomshipnames" = "hunter";
-		"skilled_npc_role" = "hunter";
+    		"skilled_npc_role" = "hunter";
-	};
+    	};
-  };
+      };
-−
-  "rsvh_asp" = {
+      "rsvh_asp" = {
-    like_ship = "asp";
+        like_ship = "asp";
-    is_external_dependency = yes;
+        is_external_dependency = yes;
-    pilot = "oolite-hunter";
+        pilot = "oolite-hunter";
-    roles = "rrs-vicious-hunter(1)";
+        roles = "rrs-vicious-hunter(1)";
-    "aft_weapon_type" = "WEAPON_BEAM_LASER";
+        "aft_weapon_type" = "WEAPON_BEAM_LASER";
-	"script_info" = {
+    	"script_info" = {
-		"randomshipnames" = "hunter";
+    		"randomshipnames" = "hunter";
-		"skilled_npc_role" = "hunter";
+    		"skilled_npc_role" = "hunter";
-	};
+    	};
-  };
+      };
-−
+    }
 '''shipdata.[[plist]]''' will provide Oolite with all the definitions necessary to include it as an entity in the game, be it ship, station, freak object or sub-entity [[shipdata_structure|(extra)]]. The following (property) entries are, for order's sake, listed alphabetically:
 = Ship keys=

← Older revision		Revision as of 21:19, 27 April 2021
Line 1:		Line 1:
		+	= Format =
	Shipdata.plist is in [http://wiki.alioth.net/index.php/Property_list Property List] format.		Shipdata.plist is in [http://wiki.alioth.net/index.php/Property_list Property List] format.
		+	The shipdata document is a dictionary of ships. Example:
		+
		+	{
		+	"rsvh_adder" = {
		+	like_ship = "adder";
		+	is_external_dependency = yes;
		+	pilot = "oolite-hunter";
		+	roles = "rrs-vicious-hunter(1)";
		+	"missile_role" = "EQ_HARDENED_MISSILE";
		+	"script_info" = {
		+	"randomshipnames" = "hunter";
		+	"skilled_npc_role" = "hunter";
		+	};
		+	};
		+
		+	"rsvh_asp" = {
		+	like_ship = "asp";
		+	is_external_dependency = yes;
		+	pilot = "oolite-hunter";
		+	roles = "rrs-vicious-hunter(1)";
		+	"aft_weapon_type" = "WEAPON_BEAM_LASER";
		+	"script_info" = {
		+	"randomshipnames" = "hunter";
		+	"skilled_npc_role" = "hunter";
		+	};
		+	};
		+	}

	'''shipdata.[[plist]]''' will provide Oolite with all the definitions necessary to include it as an entity in the game, be it ship, station, freak object or sub-entity [[shipdata_structure\|(extra)]]. The following (property) entries are, for order's sake, listed alphabetically:		'''shipdata.[[plist]]''' will provide Oolite with all the definitions necessary to include it as an entity in the game, be it ship, station, freak object or sub-entity [[shipdata_structure\|(extra)]]. The following (property) entries are, for order's sake, listed alphabetically:

← Older revision		Revision as of 21:12, 27 April 2021
Line 1:		Line 1:
		+	Shipdata.plist is in [http://wiki.alioth.net/index.php/Property_list Property List] format.
		+
	'''shipdata.[[plist]]''' will provide Oolite with all the definitions necessary to include it as an entity in the game, be it ship, station, freak object or sub-entity [[shipdata_structure\|(extra)]]. The following (property) entries are, for order's sake, listed alphabetically:		'''shipdata.[[plist]]''' will provide Oolite with all the definitions necessary to include it as an entity in the game, be it ship, station, freak object or sub-entity [[shipdata_structure\|(extra)]]. The following (property) entries are, for order's sake, listed alphabetically: