Scenarios.plist - Revision history

Cholmondely: /* Links */ Added Checksum

2025-04-24T08:26:39Z

‎Links: Added Checksum

Cholmondely: Added link

2024-07-01T09:48:50Z

Added link

Phkb: Updating BB links

2024-02-29T02:44:06Z

Updating BB links

Phkb at 11:35, 6 November 2023

2023-11-06T11:35:58Z

Cholmondely: Added summary

2023-03-12T00:35:20Z

Added summary

Cholmondely: Added Links

2023-02-01T22:13:43Z

Added Links

Massively Locked: /* scenario */ replaced "function"

2022-10-28T15:14:56Z

‎scenario: replaced "function"

Cholmondely: Added examples

2021-10-08T10:08:35Z

Added examples

Cim: /* OXP restrictions */ Core plist cancellation

2014-12-06T15:14:43Z

‎OXP restrictions: Core plist cancellation

Cim: /* Scenario-only OXPs */ clarify

2014-09-05T19:50:07Z

‎Scenario-only OXPs: clarify

@@ Line 78: / Line 78: @@
 == Links ==
 *[https://bb.oolite.space/viewtopic.php?p=254260#p254260 Cim on the aim of Scenarios.plists] (2017)
 === Examples ===
 Currently (2023) the only examples are [[SOTL Exploration]] & [[SOTL Altmap]], both by [[User:Cim|Cim]]. They each require his Loader OXZ.

@@ Line 61: / Line 61: @@
 * "'''id:'''identifier". Single OXP. The OXP with that identifier in its [[manifest.plist]], and any OXPs in its <code>requires_oxps</code> list (but ''not'' ones only in <code>optional_oxps</code>) will be loaded. No others will be.
 * "'''tag:'''tagname". OXP groups. Any OXPs with that tag in the tag list in their [[manifest.plist]]s, and any OXPs in their <code>requires_oxps</code> list (but ''not'' ones only in <code>optional_oxps</code>) will be loaded. No others will be.
-* "'''exc:'''plist". Core plist exclusion. This prevents the core Oolite plist with this filename being loaded when merging plists. For example, <code>exc:world-scripts.plist</code> will prevent any of the normal Oolite world-scripts being loaded unless they are listed in the OXPs world-scripts.plist. (Plists which cannot be overridden by OXP can not be excluded by this method, and neither can logcontrol.plist). Note that Oolite may require particular values to be set in the merged plist (e.g. <code>trade-goods.plist</code> must contain "alloys", "minerals" and "slaves" keys, to represent the cargo scooped up in hull debris, splinters, and escape pods respectively) - an OXP which excludes the core plist is responsible for ensuring that all essential values are redefined.
+* "'''exc:'''plist". Core plist exclusion. This prevents the core Oolite plist with this filename being loaded when merging plists. For example, <code>exc:world-scripts.plist</code> will prevent any of the normal Oolite world-scripts being loaded unless they are listed in the OXPs world-scripts.plist. (Plists which cannot be overridden by OXP can not be excluded by this method, and neither can [[logcontrol.plist]]). Note that Oolite may require particular values to be set in the merged plist (e.g. <code>trade-goods.plist</code> must contain "alloys", "minerals" and "slaves" keys, to represent the cargo scooped up in hull debris, splinters, and escape pods respectively) - an OXP which excludes the core plist is responsible for ensuring that all essential values are redefined.
 Restriction types other than default and strict mode may be combined by using ';' as a separator, e.g.

@@ Line 77: / Line 77: @@
 == Links ==
-*[http://www.aegidian.org/bb/viewtopic.php?p=254260#p254260 Cim on the aim of Scenarios.plists] (2017)
+*[https://bb.oolite.space/viewtopic.php?p=254260#p254260 Cim on the aim of Scenarios.plists] (2017)
 === Examples ===
 Currently (2023) the only examples are [[SOTL Exploration]] & [[SOTL Altmap]], both by [[User:Cim|Cim]]. They each require his Loader OXZ.

@@ Line 18: / Line 18: @@
 *Set the player in the middle of a major war between powers with definite front lines, regions, and battles - can they still make a living as a trader, pirate or bounty hunter when there's a full-scale Thargoid invasion on, and hundreds of systems have already completely fallen to them.
 *Completely rewrite the galaxies, ships, equipment and rules to make your own new space game with the Oolite engine.
-::(from "Features Introduced" in Oolite v.1.82 on Oolite.org's whatsnew/v1.82)
+::(from "Features Introduced" in Oolite v.1.82 on Oolite.space's whatsnew/v1.82)

@@ Line 9: / Line 9: @@
   		"scenario" = "oolite-tutorial";
+  	}
 ==Plist keys==

@@ Line 65: / Line 65: @@
 Note that the "start new game" screen itself operates in 'default' mode, so the OXP which defines the scenario cannot have the "oolite-scenario-only" tag, or require an OXP which does, or the scenario will never actually be visible. A small "loader" OXP which contains only the scenarios must be used. (The main scenario OXP probably should require the loader OXP to make sure that it gets installed)
-== Examples ==
+== Links ==
-Currently (2021) the only examples are [[SOTL Exploration]] & [[SOTL Altmap]], both by [[User:Cim]]. They each require his Loader OXZ.
+*[http://www.aegidian.org/bb/viewtopic.php?p=254260#p254260 Cim on the aim of Scenarios.plists] (2017)
 [[Category:Oolite]]
 [[Category:Oolite scripting]]

@@ Line 30: / Line 30: @@
 This key sets up the name of the scenario. If you intend the scenario to be a completely self-contained event, with a definite ending, rather than simply an alternative start position or set up for the player, then you will probably want to call [[Oolite_JavaScript_Reference:_Player#endScenario|player.endScenario]] at that point to end the game. The key here must exactly match the one used in the call to <code>player.endScenario()</code>.
-This key is optional; if it is omitted, it will be impossible to end the game using that script function.
+This key is optional; if it is omitted, it will be impossible to end the game using that method.
 ==Special Scenario Features==

@@ Line 56: / Line 56: @@
 ====Scenario-only OXPs====
-Normally an OXP will always be loaded unless excluded by the scenario. For OXPs which make major changes, it may only be appropriate to load them in particular scenarios and not in normal play. This can be achieved by adding the tag "oolite-scenario-only" to the tag list, as well as the tag or identifier required by the scenario.
+Normally an OXP will always be loaded unless excluded by the scenario. For OXPs which make major changes, it may only be appropriate to load them in particular scenarios and not in normal play. This can be achieved by adding the tag "oolite-scenario-only" to the tag list in its [[manifest.plist]], as well as the tag or identifier required by the scenario.
 Note that the "start new game" screen itself operates in 'default' mode, so the OXP which defines the scenario cannot have the "oolite-scenario-only" tag, or require an OXP which does, or the scenario will never actually be visible. A small "loader" OXP which contains only the scenarios must be used. (The main scenario OXP probably should require the loader OXP to make sure that it gets installed)