WAD file

From RRU Knowledge Base
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

This article is an unfinished work in progress or contains transferred information that needs to be rewritten or reformatted to fit our standards. Please excuse the mess and do not mark for deletion.

The .WAD files (Where's All the Data?) contain nearly all of the data for the Windows version of LEGO Rock Raiders. There are only two of these files: LegoRR0.WAD, which contains the bulk of the game's properties, and LegoRR1.WAD, which contains various messages and text contained in the game, as well as voices; in other words, files that would vary between different regional releases of the game, depending on the language spoken in the region. They are located in LEGO Media/Games/Rock Raiders, or whatever location the game is installed to.

These are compressed files and can be extracted using the Wad Tool, and is the first step in modifying the game. It is very important to have back-ups of the original unmodified LegoRR0.wad and LegoRR1.wad. This can be done by simply copying a pair to a separate location, but it is advisable not to place back-up WAD files in the same folder as the WAD Tool; otherwise, it will compress new files on top of them. A back-up folder is the best way of doing this.

When extracted two folders of the same name are created, which contain all the data in a more easily editable condition. After the wanted modification has been done, they can be compressed back into WAD files using the WAD Tool. Afterward, these can be moved back to Lego Media/Games/Rock Raiders and then the game can be run to test the modifications effected.

It has been discovered that up to 10 WAD files can be used, from LegoRR0 to LegoRR9.

Format Specifications

char {4} - Header (WWAD)

uint32 {4} - File count

// Relative Directories (for each file) char {n} - relative file path (null terminated string. Relative path within the archive)

// Absolute Directories (for each file) char {n} - absolute file path (null terminated string. Path of the source file was when it was burnt)

// For each file uint32 {4} - Version uint32 {4} - File size uint32 {4} - File size again uint32 {4} - File data offset

// Data (For each file) byte {x} - File data