Scripts within shipdata - Revision history

Cholmondely: Tagged as Legacy scripting

2021-08-09T09:46:24Z

Tagged as Legacy scripting

Eric Walch: launch_actions and auto_ai

2009-08-02T10:37:22Z

launch_actions and auto_ai

Eric Walch: typo

2009-07-20T18:04:20Z

typo

Eric Walch: Mentioned JS scripts replacing legacy ones

2009-07-20T18:03:49Z

Mentioned JS scripts replacing legacy ones

Eric Walch: /* launch_actions */

2007-11-29T17:33:45Z

‎launch_actions

Eric Walch: /* launch_actions */

2007-11-14T08:38:53Z

‎launch_actions

Eric Walch: /* launch_actions */

2007-10-24T16:45:08Z

‎launch_actions

Eric Walch: /* launch_actions */

2007-10-24T16:02:14Z

‎launch_actions

Eric Walch: /* launch_actions */

2007-09-28T18:36:07Z

‎launch_actions

Eric Walch: /* launch_actions */

2007-09-27T20:50:10Z

‎launch_actions

← Older revision		Revision as of 09:46, 9 August 2021
Line 89:		Line 89:

	Return to [[shipdata.plist]]		Return to [[shipdata.plist]]
−	[[Category:Oolite scripting]]	+	[[Category:Oolite scripting]] [[Category:Legacy scripting]]

← Older revision		Revision as of 10:37, 2 August 2009
Line 24:		Line 24:
	The same is valid for other default roles like trader, pirate, hunter, police, sunskim-trader. If added by the [[System Populator]], a trader gets a route1traderAI and a pirate gets a pirateAI etc. If you want you ship to be added in one of the default roles but with your own AI you can redefine it here. (Only redefining the AI of ships with role "trader" will have the problem that traders are also launched by stations, but in that case with an exitingTraderAI.plist or a route2sunskimAI.plist. Launching can not be detected by the new custom AI, as the "LAUNCHED OKAY" message is released before the launch_actions are executed).		The same is valid for other default roles like trader, pirate, hunter, police, sunskim-trader. If added by the [[System Populator]], a trader gets a route1traderAI and a pirate gets a pirateAI etc. If you want you ship to be added in one of the default roles but with your own AI you can redefine it here. (Only redefining the AI of ships with role "trader" will have the problem that traders are also launched by stations, but in that case with an exitingTraderAI.plist or a route2sunskimAI.plist. Launching can not be detected by the new custom AI, as the "LAUNCHED OKAY" message is released before the launch_actions are executed).

−	launch_actions is also valuable when you add a certain ship by specific role but you want him to interact with other ships like a systemship as trader or thargoid. e.g. pirates look specific for ships with role "trader" and neglect unknown specific roles. Also for thargoid/non-thargoid commands to work properly it is essential that thargoids have a role of thargoid. You can redefine a ships-role with launch_actions.
		+	Setting the AI to a new one in launch_actions is replaced by the auto_ai key. Specially since 1.73 where also the [[System Populator]] will look at the auto_ai key. When you want escorts, traders, pirates or other standard roles to keep their custom AI it is enough to set auto_ai to false.
−
−	<key>launch_actions</key>
−	<array>
−	<string>setPrimaryRole: trader</string>
−	</array>
−
−	This way you select a ship by its original role and within the system it gets the new role. (This command will work with the new role systems introduced with Oolite 1.70 or newer)

	==death_actions==		==death_actions==

@@ Line 2: / Line 2: @@
 Ships can have 4 different scripts that are executed on creation or disapearing of the ship<br>
-(Starting with Oolite 1.71 ships can also have a "script" entry that points to a JS script inside the scipts folder. When a js script is defined, none of the legacy scripts mentioned below will be used.)
+(Starting with Oolite 1.71 ships can also have a "script" entry that points to a JS script inside the scripts folder. When a js script is defined, none of the legacy scripts mentioned below will be used.)
 ==setup_actions==

@@ Line 1: / Line 1: @@
 =Shipdata.plist scripts =
-Ships can have 4 different scripts that are executed on creation or disapearing of the ship.
+Ships can have 4 different scripts that are executed on creation or disapearing of the ship<br>
 ==setup_actions==

@@ Line 21: / Line 21: @@
  </array>
-The same is valid for other default roles like trader, pirate, hunter, police, sunskim-trader. If added by the [[System Populator]], a trader gets a route1traderAI and a pirate gets a pirateAI etc. If you want you ship to be added in one of the default roles but with your own AI you can redefine it here.
+The same is valid for other default roles like trader, pirate, hunter, police, sunskim-trader. If added by the [[System Populator]], a trader gets a route1traderAI and a pirate gets a pirateAI etc. If you want you ship to be added in one of the default roles but with your own AI you can redefine it here. (Only redefining the AI of ships with role "trader" will have the problem that traders are also launched by stations, but in that case with an exitingTraderAI.plist or a route2sunskimAI.plist. Launching can not be detected by the new  custom AI, as the "LAUNCHED OKAY" message is released before the launch_actions are executed).
 launch_actions is also valuable when you add a certain ship by specific role but you want him to interact with other ships like a systemship as trader or thargoid. e.g. pirates look specific for ships with role "trader" and neglect unknown specific roles. Also for thargoid/non-thargoid commands to work properly it is essential that thargoids have a role of thargoid. You can redefine a ships-role with launch_actions.

@@ Line 18: / Line 18: @@
  <key>launch_actions</key>
  <array>
-     <string>setAITo: my_escortAI.plist</string>
+     <string>switchAITo: my_escortAI.plist</string>
  </array>

@@ Line 27: / Line 27: @@
  <key>launch_actions</key>
  <array>
-     <string>setRoles: trader</string>
+     <string>setPrimaryRole: trader</string>
  </array>
-This way you select a ship by its original role and within the system it gets the new role.
+This way you select a ship by its original role and within the system it gets the new role. (This command will work with the new role systems introduced with Oolite 1.70 or newer)
 ==death_actions==

← Older revision		Revision as of 16:02, 24 October 2007
Line 22:		Line 22:

	The same is valid for other default roles like trader, pirate, hunter, police, sunskim-trader. If added by the [[System Populator]], a trader gets a route1traderAI and a pirate gets a pirateAI etc. If you want you ship to be added in one of the default roles but with your own AI you can redefine it here.		The same is valid for other default roles like trader, pirate, hunter, police, sunskim-trader. If added by the [[System Populator]], a trader gets a route1traderAI and a pirate gets a pirateAI etc. If you want you ship to be added in one of the default roles but with your own AI you can redefine it here.
		+
		+	launch_actions is also valuable when you add a certain ship by specific role but you want him to interact with other ships like a systemship as trader or thargoid. e.g. pirates look specific for ships with role "trader" and neglect unknown specific roles. Also for thargoid/non-thargoid commands to work properly it is essential that thargoids have a role of thargoid. You can redefine a ships-role with launch_actions.
		+
		+	<key>launch_actions</key>
		+	<array>
		+	<string>setRoles: trader</string>
		+	</array>
		+
		+	This way you select a ship by its original role and within the system it gets the new role.

	==death_actions==		==death_actions==