Extracting game files - Revision history

Scratch at 10:25, 31 July 2017

2017-07-31T10:25:21Z

2017-06-24T00:34:25Z

‎On Windows

2017-06-21T23:00:20Z

Reverted edits by Myran (talk) to last revision by Scratch

2017-06-21T14:52:32Z

Reverted edits by Scratch (talk) to last revision by Mauritsio

2017-06-20T14:45:10Z

‎On Windows

2017-06-19T09:21:46Z

Windows 10 note

2017-06-15T10:22:00Z

‎On Windows

2017-06-12T12:15:32Z

@@ Line 5: / Line 5: @@
 <pre>
-PACKAGER.exe /u res/assets.bin /d assets
+PACKAGER.exe --unpack=res/assets.bin --destination=assets
 </pre>
@@ Line 11: / Line 11: @@
 <pre>
-.\PACKAGER.exe /u res/assets.bin /d assets
+.\PACKAGER.exe --unpack=res/assets.bin --destination=assets
 </pre>
 [[File:Extracted.png]]
-== On Linux ==
+== Scenarios ==
-It's roughly the same process as on Windows, except you pass the parameters a little bit differently to the Packager tool:
+The same process works for scenarios, except you pass the .bds file to the /u parameter. For example:
 <pre>
-./PACKAGER -u res/assets.bin -d assets
+PACKAGER.exe --unpack=scenarios/payload.bds --destination=scenarios/payload
 </pre>
-== Scenarios ==
+{{NewBuild|The --sval option currently does not exist, and info.xml is currently not extracted from scenarios.}}
-<pre>
+Depending on when the scenario was packaged, you will not get an <code>info.xml</code> file. This is the case for scenarios packaged at or before build 181.
-Note that this currently does not extract the info.xml.
+In such cases where you don't have the <code>info.xml</code> file but you do need to know its contents, you can get a read-only approximation of this file by passing <code>--sval</code> while unpacking. This will write a serialized <code>info.sval</code> file into the destination folder. This file is not very useful if you intend to take it and modify it, as it's only an approximation.

@@ Line 2: / Line 2: @@
 == On Windows ==
-First, navigate to your Bogus Detour installation folder. In this folder, hold down Shift and F10 at the same time to open the advanced shortcut menu. From here, select "Open command prompt here." You should now see the Windows command prompt in front of you, in the current folder. Then, run the following command, which will extract all files from <code>res/assets.bin</code> into the <code>assets</code> folder.
+First, navigate to your Bogus Detour installation folder. In this folder, hold down Shift and F10 at the same time to open the advanced shortcut menu. From here, select "Open command prompt here." (On Windows 10 this is Powershell.) You should now see the Windows command prompt in front of you, in the current folder. Then, run the following command, which will extract all files from <code>res/assets.bin</code> into the <code>assets</code> folder.
 <pre>

← Older revision		Revision as of 12:15, 12 June 2017
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.