Builder to player - Revision history

Proleric1: /* Step by Step */

2011-04-18T17:49:32Z

‎Step by Step

Kelamor: Add languages bar

2011-02-14T01:56:32Z

Add languages bar

Eshme at 18:49, 3 February 2010

2010-02-03T18:49:26Z

Eshme: /* Resources organized */

2010-01-31T00:47:33Z

‎Resources organized

Eshme: /* Step by Step */

2010-01-30T20:16:25Z

‎Step by Step

Eshme at 20:02, 30 January 2010

2010-01-30T20:02:03Z

Eshme at 19:33, 29 January 2010

2010-01-29T19:33:02Z

Apolyon6k at 22:53, 23 December 2009

2009-12-23T22:53:14Z

BryanDerksen: quick summary, can't believe I missed out creating a page on this

2009-11-06T21:28:38Z

quick summary, can't believe I missed out creating a page on this

New page

"Builder to player" packaging is a system for packaging up the playable binary files you've exported from your toolset into a form that is easily installed and played on another system. It can be found under the "Tools -> Builder" menu.

The toolset will list all the binary files you've exported, including both art and designer resources, and give you the opportunity to select which ones to include in the package (you usually won't need to include core resources, for example). It will then package them into [[ERF]]s, which will be bundled together into a [[DAZIP]] file along with a manifest file used by the program DAUpdater when installing the package on the end user's machine.

← Older revision		Revision as of 17:49, 18 April 2011
Line 45:		Line 45:

	Create a Manifest if you wish, which will save your resources selection for the next time you do the process.		Create a Manifest if you wish, which will save your resources selection for the next time you do the process.
		+
		+	Currently, there is a [[Bug:_toolset_export_generates_files_with_names_that_can%27t_be_packaged_in_builder_to_player \| file name bug]] which affects external levels etc. Refer to that link for a workaround.

	{{languages}}		{{languages}}

@@ Line 45: / Line 45: @@
 Create a Manifest if you wish, which will save your resources selection for the next time you do the process.
 [[category:database]]
 [[category:modules]]

← Older revision		Revision as of 18:49, 3 February 2010
Line 47:		Line 47:

	[[category:database]]		[[category:database]]
		+	[[category:modules]]

@@ Line 24: / Line 24: @@
 Resources in here is not advised, it allows Resources to be available to other modules even if you deactivate your custom Module. Additionally the Toolset has the habbit of exporting Core Game Resources here, which are mere duplicates unless you modified them. These duplicates need to be deleted, as potentially they still create problems in the singleplayer campaign. <small>''(See: [[Bug: export creates unnecessary core override|Bug Report]])''</small>  If all your Resources are in your Modules Folder, this is an easy thing of selecting all and deleting.
-All Resources need to be present (that is if you created them):
+All Resources need to be present and fully exported (that is if you created them):
 *[[Designer Resources]]

@@ Line 32: / Line 32: @@
 == Step by Step ==
-"Tools -> Builder" menu.
+Start the process by selecting from the menu:
-The toolset will list all the binary files you've exported, including both art and designer resources, and give you the opportunity to select which ones to include in the package (you usually won't need to include core resources, for example). It will then package them into [[ERF]]s, which will be bundled together into a [[DAZIP]] file along with a manifest file used by the program DAUpdater when installing the package on the end user's machine.
+It will ask for a "Manifest". The "Manifest" is a helper, which isnt available the first time. However can be created afterwards, which will save you resource selection, so that exporting the next time you can select this "Manifest" and wouldnt need to select all the resources again.
 [[category:database]]

@@ Line 1: / Line 1: @@
 {{Infobox module}}
-"Builder to player" packaging is a system for packaging up the playable binary files you've exported from your toolset into a form that is easily installed and played on another system. It can be found under the "Tools -> Builder" menu.
+"Builder to player" packaging is a system for packaging up the playable binary files you've exported from your toolset into a form that is easily installed and played on another system.
 The toolset will list all the binary files you've exported, including both art and designer resources, and give you the opportunity to select which ones to include in the package (you usually won't need to include core resources, for example). It will then package them into [[ERF]]s, which will be bundled together into a [[DAZIP]] file along with a manifest file used by the program DAUpdater when installing the package on the end user's machine.
 [[category:database]]

← Older revision		Revision as of 22:53, 23 December 2009
Line 2:		Line 2:

	The toolset will list all the binary files you've exported, including both art and designer resources, and give you the opportunity to select which ones to include in the package (you usually won't need to include core resources, for example). It will then package them into [[ERF]]s, which will be bundled together into a [[DAZIP]] file along with a manifest file used by the program DAUpdater when installing the package on the end user's machine.		The toolset will list all the binary files you've exported, including both art and designer resources, and give you the opportunity to select which ones to include in the package (you usually won't need to include core resources, for example). It will then package them into [[ERF]]s, which will be bundled together into a [[DAZIP]] file along with a manifest file used by the program DAUpdater when installing the package on the end user's machine.
		+	[[category:database]]