WoWs depack

Open-Source World of Warships resource files unpacker.

Links

Interesting links:

• Git repository: github.com/wows-tools/wows-depack
• Format specification: FORMAT.md.
• Reverse Engineering process: REVERSING_STORY.md
• Library API: C API documentation

Usage

Build

# Install deps Debian/Ubuntu
apt install git cmake zlib1g-dev libpcre3-dev clang
 
# git clone + go in project dir
git clone https://github.com/kakwa/wows-depack.git
cd wows-depack/
 
# build
cmake .
make

CLI tool

Help

./wows-depack-cli --help
 
Usage: wows-depack-cli [OPTION...] -W WOWS_BASE_DIR
 
World of Warships resource extractor tool.
[...]

Print all files

To print all the files present:

./wows-depack-cli -W ~/Games/World\ of\ Warships/ -p
 
/gui/modernization_icons/icon_modernization_PCM020_DamageControl_Mod_I.png
/gui/modernization_icons/icon_modernization_PCM047_Special_Mod_I_Montana.png
[...]
/clanbase/headquarters_2/6/29/31.png
/server_stats.xml

Search

Search files by name pattern (perl compatible regular expression):

./wows-depack-cli -W ~/Games/World\ of\ Warships/ -s '.*[Pp]arams.*'
 
Found 3 matching files:
shipyardParams.xml
content/GameParams.data
content/UIParams.data

Extract a single file

To Extract a Single file, do:

./wows-depack-cli -W ~/Games/World\ of\ Warships/ \
    -e 'content/GameParams.data' -o GameParams.data

Extract a whole directory

To extract a whole sub directory, do:

./wows-depack-cli -W ~/Games/World\ of\ Warships/ \
    -e 'content/' -O out/

Extract every World of Warships resource files

To extract everything (rip your free disk space), run:

./wows-depack-cli -W ~/Games/World\ of\ Warships/ \
    -e '/' -O out/

Parse Specific index file(s)

Instead of -W/--wows-dir, a specific index file or directory can be specified through the -i or -I options.

Parse a single index file:

./wows-depack-cli -i ~/Games/World\ of\ Warships/bin/6831266/idx/system_data.idx -p

Parse all the indexes in an index directory:

./wows-depack-cli -I ~/Games/World\ of\ Warships/bin/6831266/idx/ -p

Note, the other examples are using -W <WOWS DIR> , but it could be faster to specify one index file directly through -i <FILE>. Specifically, GameParams,data is referenced in the system_data.idx index.

Also, please note that you will need to adapt the path to your WoWs install and the parent of idx/ (the 6831266 part changes with every update).

Library

API documentation

The API documentation is available here.

Usage examples

Initialize Context & Parse Index Files

To start searching/extracting file, you first need to init & fill the context.

With a single index file:

#include "wows-depack.h"
 
 
/* Other debug categories */
// WOWS_DEBUG_RAW_RECORD
// WOWS_DEBUG_FILE_LISTING
/* several debug categories can be enabled like so: */
// WOWS_DEBUG_FILE_LISTING | WOWS_DEBUG_RAW_RECORD;
 
 
WOWS_CONTEXT *context = wows_init_context(WOWS_NO_DEBUG);
 
/* Parse the index file */
int ret = wows_parse_index(index_file_path, context);

To parse the indexes, you can either specify a specific index file:

char *index_file_path = "Games/World of Warships/bin/6831266/idx/system_data.idx"
 
/* Parse the index file */
int ret = wows_parse_index(index_file_path, context);

Alternatively, you can parse all the index files in a given directory:

// Note: the '6831266' directory changes every updates
char *index_dir_path = "Games/World of Warships/bin/6831266/idx"
 
/* Parse the index file */
int ret = wows_parse_index_dir(index_dir_path, context);

Wows depack also provides a small helper to detect the latest idx directory.

char *index_dir_path;
 
get_latest_idx_dir("Games/World of Warships/", index_dir_path);
 
/* Parse the index file */
int ret = wows_parse_index_dir(index_dir_path, context);
 
// [...] do stuff
 
// You need to free index_dir_path after
free(index_dir_path);

These operations will parse one or several index files, and construct a pseudo-filesystem tree which can be then explored.

Searching files/directories

It's possible to search for matching files inside the indexes:

// Init output variables
int resc;
char **res_files;
 
 
/* Supported search modes:
WOWS_SEARCH_FILE_ONLY     < Search only on file names.
WOWS_SEARCH_DIR_ONLY      < Search only on directory names.
WOWS_SEARCH_FILE_PLUS_DIR < Search on directory and file names.
WOWS_SEARCH_FULL_PATH     < Search on the full path of files.
*/
 
// PCRE search pattern, please note that the final regex is "^<search_pattern>$"
char *search_pattern = ".*Params.*";
 
// Search the files
wows_search(context, search_pattern, WOWS_SEARCH_FILE_ONLY, &resc, &res_files);
 
// Print and free the result
printf("Found %d matching files:\n", resc);
for (int i = 0; i < resc; i++) {
    printf("%s\n", res_files[i]);
    // Free Each file path must be freed
    free(res_files[i]);
}
// Free the array containing these paths
free(res_files);

Extracting Files

To extract files, you can do the following:

char *output = "path/output.xml"
 
// Extract to output file
ret = wows_extract_file(context, "stuff.xml", output);

If you want to control the underlying File Pointer (for example, to write in a memstream), extract functions also provide an _fp version whenever possible:

char *buf = NULL;
size_t buf_size = 0;
 
// Open the file
FILE *f = open_memstream(&buf, &buf_size);
 
// Extract to File *
ret = wows_extract_file_fp(context, "stuff.xml", f);
 
// Close the file
fclose(f);
 
free(buff);

You can also extract files recursively under a given directory:

char *output_dir = "./out/"
 
ret = wows_extract_dir(context, "/wows-resources/dockyard/", output_dir);

Note that with this extract, wows-depack will reproduce the pseudo-filesystem in the archive with output_dir as its root.

Clean-up

Once done, you need to release the context memory:

wows_free_context(context);

Error Handling & Debugging

Most wows_* returns 0 on success or error codes on failure. To convert it to an error message, you can do the following:

// wows_* function call example
int ret = wows_parse_index(index_file_path, context);
 
/* Error handling */
if (ret != 0) {
    /* get an error message + additional info from context + return code */
    char *err_msg = wows_error_string(ret, context);
    printf("Error: %s\n", err_msg);
    // the message must be freed
    free(err_msg);
}

To print the whole pseudo-filesystem tree to stdout, you can use the following functions:

// Print a tree like layout
wows_print_tree(context);
 
// Print the full path of each file, one per line
wows_print_flat(context);

Write support

wows-depack provides experimental write support for creating index and pkg files:

char *input_dir = "./tests";
FILE *nfd_pkg = fopen("stuff.pkg", "w+");
FILE *nfd_idx = fopen("stuff.idx", "w+");
wows_write_pkg(context, input_dir, "stuff.pkg", nfd_pkg, nfd_idx);
fclose(nfd_idx);
fclose(nfd_pkg);

Please note that the write support is limited, and was created mainly to generate test data.

Build & development

Dependencies

Installing the dependencies on Debian:

apt install cmake zlib1g-dev libpcre3-dev clang

Installing the test/coverage/doc dependencies:

apt install lcov libcunit1-dev doxygen

Build

cmake .
make

Install

# Remove DESTDIR for system installation
make install DESTDIR=fakeroot

Files installed:

tree fakeroot
fakeroot
└── usr
    └── local
        ├── bin
        │   └── wows-depack-cli
        ├── include
        │   └── wows-depack.h
        └── lib
            ├── libwows-depack.so -> libwows-depack.so.0
            ├── libwows-depack.so.0 -> libwows-depack.so.0.1.0
            └── libwows-depack.so.0.1.0

Tests

To run the unit tests, do the following:

# cmake run (on time)
cmake -DCOVERAGE=ON -DBUILD_TESTS=ON .
# run just the unit tests
make tests
# run also the coverage tests
make coverage

in case of issues, you can directly launch the test binary alone:

# directly:
./wows-depack-test
 
# or with gdb:
gdb --args ./wows-depack-test

Documentation

To build the doxygen documentation:

cmake -DBUILD_DOC=ON .
 
make doc_doxygen

Optionally, get a nicer doxygen theme:

./misc/setup_doxycss.sh
 
make doc_doxygen

Fuzzing

This tool/lib parses binary data, consequently checking for overflow might be a good idea.

To do so, install american fuzzy lop++ (afl++):

# Debian/Ubuntu
apt install afl-clang
 
# Mac OS
brew install afl-fuzz

Compile with afl support:

cmake -DCMAKE_CXX_COMPILER=afl-clang++ -DCMAKE_C_COMPILER=afl-clang .
make

Run the fuzzing

# Replace with your WoWs install directory
INDEX_DIR="~/Games/World\ of\ Warships/bin/6775398/idx/"
 
afl-fuzz -i "$INDEX_DIR" -o ./out -t 10000 -- ./wows-depack-cli -i '@@'

Then wait for crashes to occur (hopefully this will be in vain).