Exporting and running a module - Revision history

Proleric1: /* Exporting the module */

2010-11-24T19:17:41Z

‎Exporting the module

Proleric1: /* Exporting the module */

2010-11-24T19:15:51Z

‎Exporting the module

Proleric1: /* Exporting the module */

2010-11-24T19:15:19Z

‎Exporting the module

Proleric1: /* Export Options */

2010-11-24T19:12:37Z

‎Export Options

Proleric1: /* Export Options */

2010-11-24T19:12:04Z

‎Export Options

Proleric1: /* Export Options */

2010-11-24T19:10:16Z

‎Export Options

Proleric1: /* Exporting the module */

2010-11-24T19:01:19Z

‎Exporting the module

Sunjammer: Applied Languages template

2010-10-26T12:29:30Z

Applied Languages template

Equilibrium Keeper: /* Locations where resources are exported to/read from */

2010-10-16T09:31:22Z

‎Locations where resources are exported to/read from

Apolyon6k at 22:55, 23 December 2009

2009-12-23T22:55:42Z

@@ Line 49: / Line 49: @@
 * Forgetting to export something is a major cause of mysterious problems in game, so be sure to select everything you've modified.
 * Changes to the Export Options do not take effect until something is exported.
-* It's always wise to export areas before testing. Certain object properties (e.g. tag) can be overriden for area instances. If you change the resource template, the change will NOT take effect in game until the area is exported, even if the area is using the default values (this might be a bug).
+* It's always wise to export areas before testing. Certain object properties (e.g. tag) can be overriden for area instances. If you change the resource template then export it, the change will NOT take effect in game until the area is exported, even if the area is using the default values (this might be a bug).
 * There's also a good case for exporting scripts every time. This recompiles them all, ensuring that any changes to custom includes are consistent.
 * If you create a resource without saving it, it will not export automatically, even if '''Auto-Export on Save''' is set. This can happen if, for example, you create resources in a Builder-to-Builder Load, but never edit them.

@@ Line 51: / Line 51: @@
 * It's always wise to export areas before testing. Certain object properties (e.g. tag) can be overriden for area instances. If you change the resource template, the change will NOT take effect in game until the area is exported, even if the area is using the default values (this might be a bug).
 * There's also a good case for exporting scripts every time. This recompiles them all, ensuring that any changes to custom includes are consistent.
-* If you create a resource without saving it, it will not export automatically, even if """Auto-Export on Save""" is set. This can happen if, for example, you create resources in a Builder-to-Builder Load, but never edit them.
+* If you create a resource without saving it, it will not export automatically, even if '''Auto-Export on Save''' is set. This can happen if, for example, you create resources in a Builder-to-Builder Load, but never edit them.
 == Export Options ==

@@ Line 47: / Line 47: @@
 Points to watch out for:
 * Changes to the Export Options do not take effect until something is exported.
 * It's always wise to export areas before testing. Certain object properties (e.g. tag) can be overriden for area instances. If you change the resource template, the change will NOT take effect in game until the area is exported, even if the area is using the default values (this might be a bug).
 * There's also a good case for exporting scripts every time. This recompiles them all, ensuring that any changes to custom includes are consistent.
-* If you create a resource without saving it, it will not export automatically. This can happen if, for example, you create resources in a Builder-to-Builder Load, but never edit them.
+* If you create a resource without saving it, it will not export automatically, even if """Auto-Export on Save""" is set. This can happen if, for example, you create resources in a Builder-to-Builder Load, but never edit them.
 == Export Options ==

@@ Line 53: / Line 53: @@
 == Export Options ==
-'''Export without dependent resource:''' This is almost invariably the best option. It only exports the currently selected resource(s). It gives complete control over what is exported. Forgetting to export something is a major cause of mysterious problems in game, so be sure to select everything you've modified. All other options export core resources unnecessarily, making the player package bigger than it needs to be.
+'''Export without dependent resource:''' This is almost invariably the best option. It only exports the currently selected resource(s). It gives complete control over what is exported. All other options export core resources unnecessarily, making the player package bigger than it needs to be.
 '''Export with dependent resources:''' This will export the currently selected resource, as well as any other resources that it depends upon. For instance, if you have created an area with a creature in it, this option will export the area, the creature, the creature's inventory, the scripts, etc. It would then grab any dependencies for the creature, inventory, or scripts and continue until it exhausted all of their dependencies. Doing this is a good way to make sure you get all of the needed pieces for any particular resource, but it can also quickly multiply to the point where it is picking up half of the module.

@@ Line 53: / Line 53: @@
 == Export Options ==
-'''Export without dependent resource:''' This is almost invariably the best option. It only exports the currently selected resource(s). It gives complete control over what is exported. Forgetting to export something is a major cause of mysterious problems in game, so be sure to select everything you've modified.
+'''Export without dependent resource:''' This is almost invariably the best option. It only exports the currently selected resource(s). It gives complete control over what is exported. Forgetting to export something is a major cause of mysterious problems in game, so be sure to select everything you've modified. All other options export core resources unnecessarily, making the player package bigger than it needs to be.
-−
-The other options are rarely useful, because they export core resources unnecessarily. There's no point in making the player package bigger than it needs to be!
 '''Export with dependent resources:''' This will export the currently selected resource, as well as any other resources that it depends upon. For instance, if you have created an area with a creature in it, this option will export the area, the creature, the creature's inventory, the scripts, etc. It would then grab any dependencies for the creature, inventory, or scripts and continue until it exhausted all of their dependencies. Doing this is a good way to make sure you get all of the needed pieces for any particular resource, but it can also quickly multiply to the point where it is picking up half of the module.

@@ Line 37: / Line 37: @@
 == Exporting the module ==
-When this is completed, close the Export options window and select the Export with dependent resources or export without dependent resources option.
+When this is completed, close the Export options window. In the ALL view of the resource palette, select all of the resources for your module (only). Right-click then Export without dependent resources.
 [[Image:DA_Audio_Design_Documentation_Ambience_Content_html_m5298f3df.png]]
-Either option will export the level to the game. Once the export has completed you should be able to start a "New Game" (if editing the main campaign) or select your module under "Other Campaigns" (for stand-alone content). You should start in the level that you have exported at the waypoint that you have set as your starting point.
+This will export your module to the game. Once the export has completed you should be able to start a "New Game" (if editing the main campaign) or select your module under "Other Campaigns" (for stand-alone campaigns). You should start in the level that you have exported at the waypoint that you have set as your starting point.
 == Export Options ==

← Older revision		Revision as of 12:29, 26 October 2010
Line 56:		Line 56:

	See [[Source directory priorities]] for a list of the directories that resources can be stored for the game and toolset to use.		See [[Source directory priorities]] for a list of the directories that resources can be stored for the game and toolset to use.
−	~~<includeonly>{{H-langs:{{{enname\|}}}}}</includeonly><noinclude>{{H-langs:H:f Exporting_and_running_a_module}}~~

	[[Category:Tutorials]]		[[Category:Tutorials]]
		+	{{Languages}}

← Older revision		Revision as of 09:31, 16 October 2010
Line 56:		Line 56:

	See [[Source directory priorities]] for a list of the directories that resources can be stored for the game and toolset to use.		See [[Source directory priorities]] for a list of the directories that resources can be stored for the game and toolset to use.
−	[[~~category~~:~~tutorials~~]]	+	<includeonly>{{H-langs:{{{enname\|}}}}}</includeonly><noinclude>{{H-langs:H:f Exporting_and_running_a_module}}
		+
		+	[[Category:Tutorials]]

← Older revision		Revision as of 22:55, 23 December 2009
Line 56:		Line 56:

	See [[Source directory priorities]] for a list of the directories that resources can be stored for the game and toolset to use.		See [[Source directory priorities]] for a list of the directories that resources can be stored for the game and toolset to use.
		+	[[category:tutorials]]