Difference between revisions of "Extracting game files"
(Created page with "The packager tool allows you to package a scenario, but it also allows you to unpack or extract scenarios, as well as base the content from the <code...") |
|||
| Line 14: | Line 14: | ||
./PACKAGER -u res/assets.bin -d assets | ./PACKAGER -u res/assets.bin -d assets | ||
</pre> | </pre> | ||
| + | |||
| + | == Scenarios == | ||
| + | The same process works for scenarios, except you pass the .bds file to the /u parameter. For example: | ||
| + | |||
| + | <pre> | ||
| + | PACKAGER.exe /u scenarios/payload.bds /d scenarios/payload | ||
| + | </pre> | ||
| + | |||
| + | Note that this currently does not extract the info.xml. | ||
Revision as of 14:15, 12 June 2017
The packager tool allows you to package a scenario, but it also allows you to unpack or extract scenarios, as well as base the content from the res/assets.bin file. This is useful if you want to use any of our base resources such as units and scripts, in your mod, or use them as reference material.
On Windows
Open a Windows command prompt window (Win+R) and navigate to your Bogus Detour installation folder. Then, run the following command, which will extract all files from res/assets.bin into the assets folder.
PACKAGER.exe /u res/assets.bin /d assets
On Linux
It's roughly the same process as on Windows, except you pass the parameters a little bit differently to the Packager tool:
./PACKAGER -u res/assets.bin -d assets
Scenarios
The same process works for scenarios, except you pass the .bds file to the /u parameter. For example:
PACKAGER.exe /u scenarios/payload.bds /d scenarios/payload
Note that this currently does not extract the info.xml.
