Difference between revisions of "Equipment-overrides.plist"

From Elite Wiki
(Created page with "<code>equipment-overrides.plist</code> is added with Oolite 1.89. It loads after all the <code>equipment.plist</code> data is read in. Whenever it finds a match with a k...")
 
(Updating BB links)
 
(4 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
It loads after all the <code>[[equipment.plist]]</code> data is read in. Whenever it finds a match with a key that also exists in <code>[[equipment.plist]]</code> of any oxp, it overwrites the entries defined in equipment-overrides.plist but leaves the others as they were.
 
It loads after all the <code>[[equipment.plist]]</code> data is read in. Whenever it finds a match with a key that also exists in <code>[[equipment.plist]]</code> of any oxp, it overwrites the entries defined in equipment-overrides.plist but leaves the others as they were.
  
The structure of the file is slightly different to the equipment.plist file, which is an array of arrays. This is a dictionary of dictionary objects. Each element of an equipment definition is specified with it's own unique property name. A sample file is shown below.
+
The structure of the file is slightly different to the equipment.plist file, which is an array of arrays. This is a dictionary of dictionary objects. Each element of an equipment definition is specified with its own unique property name. A sample file is shown below.
  
 
  {
 
  {
Line 18: Line 18:
 
  }
 
  }
  
See [[OXP_howto]] for an overview about the other plists.
+
 
 +
Special note: Unlike the [[shipdata-overrides.plist]] file, any information in the "script_info" section will be ''added'' to the equipment entry. It will not ''replace'' data in an existing "script_info" section unless explicitly updated. For instance, if the original equipment.plist entry has <code>"script_info = { equipment_space = 4; };"</code>, and the override file has <code>"script_info = { extra_space = 5; };"</code>, the end result will be <code>"script_info = { equipment_space = 4; extra_space = 5; };"</code>.
 +
 
 +
== Links ==
 +
*[https://bb.oolite.space/viewtopic.php?f=2&t=21499 Equipment-overrides :-/] (2023 - not all about the Equipment-overrides.plist)
 +
 
 +
*See [[OXP_howto]] for an overview about the other plists.
  
 
----
 
----
 +
[[Category:Updated JavaScript features in Oolite 1.89]]
 
[[Category:Oolite]]
 
[[Category:Oolite]]
 
[[Category:Oolite scripting]]
 
[[Category:Oolite scripting]]

Latest revision as of 01:39, 29 February 2024

equipment-overrides.plist is added with Oolite 1.89.

It loads after all the equipment.plist data is read in. Whenever it finds a match with a key that also exists in equipment.plist of any oxp, it overwrites the entries defined in equipment-overrides.plist but leaves the others as they were.

The structure of the file is slightly different to the equipment.plist file, which is an array of arrays. This is a dictionary of dictionary objects. Each element of an equipment definition is specified with its own unique property name. A sample file is shown below.

{
  "EQ_WEAPON_PULSE_LASER" = {
    techlevel = 7;
    price = 50000;
    short_description = "Laser Pointer";
    long_description = "A simple, all purpose (but weak) laser. Only useful for irritating pirates.";
    available_to_all = YES;
    weapon_info = {
      color = "whiteColor";
    };
  };
}


Special note: Unlike the shipdata-overrides.plist file, any information in the "script_info" section will be added to the equipment entry. It will not replace data in an existing "script_info" section unless explicitly updated. For instance, if the original equipment.plist entry has "script_info = { equipment_space = 4; };", and the override file has "script_info = { extra_space = 5; };", the end result will be "script_info = { equipment_space = 4; extra_space = 5; };".

Links

  • See OXP_howto for an overview about the other plists.