Builder to player
| Module topics |
|---|
|
"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.
Overview
"Builder to player" packs every resource that is needed to be installed on another computer into a single filetype called DAZIP. You however must select those needed resources from folders and files in a treelike view. The "builder to player" function allows only files to be included from your modules "core" and "module" override folders, and the "Core Game Resources" Folder. As so it is very important that your resources are organized correctly.
It can be found under the "Tools -> Builder" menu.
Resources organized
While the Toolset exports Designer Resources into their correct location, Art Resources and 2DA's which you created with external tools need to be arranged manually.
Likely, in your first steps you have placed those into a random Override folder until it works. The Toolset can read every Override folder just fine, so this didnt cause harm until now. The "builder to player" function requires resources to be organized, so it can package them and get distributed. So that no file is missed in the package, which causes the Module to work for you ,but not for someone else. It can help if you place Resources correctly from the start up.
The primary choice is always your custom Modules folders. Depending on whether your Resources shall be available only in your "module", or to other modules "core".
*My Documents*\BioWare\Dragon Age\AddIns\*Modulename*\module\override\toolsetexport\ *My Documents*\BioWare\Dragon Age\AddIns\*Modulename*\core\override\toolsetexport\
The other folder that can be included is the "Core Game Resources" Folder. This Folder must be treated with care, as this place is reserved for Gamewide Core Resources..
*My Documents*\BioWare\Dragon Age\packages\core\override\toolsetexport\
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. (See: Bug Report) 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 and fully exported (that is if you created them):
Step by Step
Start the process by selecting from the menu:
"Tools -> Builder -> Builder to player package"
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.
Click cancel, or select a previously saved Manifest.
The toolset will now list all the binary files you've exported, including 2DA's, 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 game resources "from \packages\core", for example). It will then package them into 3 ERFs (one for each directory listed above), 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.
If you followed a clean structure with your resources, you may only select the whole custom module folder and be ready.
Select a location to save the file in. Click Save.
Create a Manifest if you wish, which will save your resources selection for the next time you do the process.
Currently, there is a file name bug which affects external levels etc. Refer to that link for a workaround.
| Language: | English • русский |
|---|
