Differences

This shows you the differences between two versions of the page.

--- extraction [2026/02/20 12:24] – ultracomfy
+++ extraction [2026/04/14 17:41] (current) – ultracomfy
@@ Line 1: / Line 1: @@
+~~NOTOC~~
 <WRAP column 18% right>
 {{page>Templates:Video_Games}}
@@ Line 6: / Line 7: @@
 <WRAP centeralign>Video Games/Assets/\\
 <fs xx-large>Extraction</fs></WRAP>
-Video game file extraction is the process of ripping assets from a video game's game files. In 2026, video game assets are still stored on the local machine and streamed from the disk. This makes all game assets accessible from the local machines, allowing talented individuals to extract them into their individual parts.
-====== Process ======
+Welcome! This is my hub for video game asset extraction related information and guides. I will be going through everything one step at a time to explain how everything works.
-Some games store their assets plainly, ie. their textures, sounds and many other things are just literal picture and sound files. In this case, "extraction" is as simple as copying the folder's contents elsewhere. [[DEFCON (Game)]] is one such case.
-===== Container Files =====
+Please note that these tutorials presume a basic, general understanding of how to work with a computer. It demands that you are comfortable with the Windows file system, understand file paths and are capable of performing basic PC procedures like installing and running applications, editing standard file formats like ''.txt'', download files or programs from Github and can perform basic operations in Command Prompt (I prefer cmd over ps). For example, I will not be teaching how to open the Command Prompt or how to navigate between folders with it. However, this tutorial does //not// expect you to be advanced enough to actually build Github projects, for example.
-However, other games, especially ones that were made using one of the popular [[video game engine]]s like [[Unity]] or - shudders - [[Unreal]] don't make it quite as easy. When baking, these games pack all the assets into engine-specific [[container file]]s. For Unity, these are typically found in the game's "Data" folder with .resource endings. Unreal games come with .pak files in the "Shipping" folder.
-These files are a lot like .rar and .zip files. You cannot open them directly, but they can be extracted with tools. For .rar/.zip you would use one of the many tools like WinRAR, 7Zip or such, whereas with Unity's files you will need [[AssetStudio]]. Like WinRAR lets you load .zip files, AssetStudio lets you load the .resource files, view their contents and extract assets.
+===== Step 1: Basics =====
+Before you can work with video game files, you need to understand some basic game development concepts.\\
+I have compiled the most important ones here:
-Unreal is a lot more proprietary, so it is a lot harder to crack. Unreal is constantly changed and updated so that tool creators have to constantly keep up with Unreal's changes on a shorter timeframe. This leads to tools quickly becoming outdated, which itself leads to many different tools in different stages of production that are compatible with different versions of Unreal to varying degrees. Seriously, I have like four different tools for Unreal games because of that. The standard method is a command line tool called "QuickBMS". On its own QuickBMS is basically just a "launcher" for all kinds of extraction scripts, a list of which can be found [[https://aluigi.altervista.org/quickbms.htm|here]]. When QuickBMS is run, it will ask for a script to run. In our case we would use the Unreal Tournament 4 script. It will then ask for the input files and for an output location. In many cases, games are AES encrypted - an encryption layer on top of the packing method that Unreal already employs - if it asks for an AES Key, that has to be supplied as well. These are game-specific, not computer-specific, so there are resources online with comprehensive lists for a lot of Unity games with keys that work on all machines.
+  * [[Extraction Basics]]\\
+This page includes only the strictly necessary information related to extraction.
-Once set, QuickBMS with the script will get to work and extract.
+===== Step 2: Identify Game Files =====
+The approach to extraction depends on what the game files look like.
-===== Middleware Files =====
+Games on Android, for example, come packaged as ''.apk'' files. That's all you need to know for now and you can already move to Step 3.\\
-Especially when it comes to stuff like game audio (which is what I am mostly interested in), games like to use third party software to help them with the development of the game's audio implementation. It's a bit like a video game engine for video games, but for audio, and it's on top of the video game. So when you run these games, you will often also be running a WWise session that tells the game what to do with its audio. Software like WWise have their own specialized formats which, in some cases, are also their own type of container files. Classic examples here are .wem and .bank files. Wem is an audio format, while .bank is a "soundbank", ie. a file containing multiple, individual audio files.
+On Windows, you will now need to dig into the game's folder and see what you can find.
-If you are new to this, you are probably looking for a .wav or .mp3 files, which you consider proper audio files (not at least because most audio players only understand these and similar file formats). In this case, files like .wem need to still be converted, and .bank files need to be extracted. The exact approach here differs based on the exact type of file you're looking at.
+  - Unreal games, for example, tend to place their files into the ''\<gamename>\Content\Paks'' folder and contain ''.pak'' and ''.utoc'' files.
+  - Unity games often have their files in the ''\<gamename>\<gamename>_Data'' and contain ''.assets'' and ''.res'' files.
+  - In some cases, the game might store middleware files //outside// of the game engine's files. Rocket League for example stores many Wwise files in ''rocketleague\TAGame\CookedPCConsole''.
+===== Step 3: Select Approach =====
+Depending on the file identification, follow the following links:
+  * [[Unreal Engine Extraction|Unreal Engine]]
+  * [[Unity Extraction|Unity]]
+  * [[Android Extraction|.APK and Android Files]]