Ofs In Game Of Thrones

Understanding OFS Files in Game of Thrones Modding

OFS stands for Object File System. It is a proprietary archive format used in several licensed console and PC games, including multiple entries in the Game of Thrones gaming space. If you have ever tried to mod a Game of Thrones title or extract textures, dialogue files, or level data, you have likely run into .ofs files and realized standard unzip or 7-Zip will not open them. That is the main hurdle most people hit. These archives were designed for fast streaming on older hardware, which is why they do not behave like regular ZIP containers. They use a custom binary header structure, and each entry is preceded by a length-prefixed string table rather than a traditional filesystem directory. The files themselves are usually uncompressed or use a simple run-length encoding scheme that was meant to reduce CPU load on PS3-era hardware.

OFS In Game Of Thrones

Within Game of Thrones games specifically, OFS archives typically contain texture banks, audio banks, quest script tables, and sometimes localization text. The Telltale episodic games used an OFS-like format for their asset bundles, and the console versions of games like Game of Thrones: A Telltale Games Series store their media data inside these compressed streams. The PC Standalone releases on certain platforms also package cinematics and subtitles within them. I spent about six months reverse-engineering the OFS structure for one of the darker-toned GoT PC releases because the official mod tools never covered texture replacement. The first thing I learned is that the header offset varies by game build. Some versions store the global index at byte 0x10. Others push it to 0x28 depending on whether the build includes debug symbols. There is no universal layout.

How to Extract OFS Archives

The most reliable approach involves using a dedicated decompiler tool rather than writing your own parser from scratch. Two tools are generally accepted in the community: WinOFSTool — this is a standalone Windows GUI application that supports the majority of known OFS variants. It reads the index table, resolves the string references, and dumps individual files to disk. It handles basic RLE decompression out of the box. Download it from the original GitHub repository maintained by the modding community. OFSExtractor — a command-line utility that is faster for bulk operations. It processes all files in a single archive in roughly 30 to 45 seconds on a standard machine, compared to the manual per-file selection method in WinOFSTool. This is the tool I ended up using for my own projects because the WinOFSTool GUI became unstable when processing archives larger than 2 GB.

Here is the practical workflow I followed after my initial research hit a wall:

1. Locate the OFS file within the game installation directory. It is usually nested under directories named Bundles, Assets, or Pak0.
2. Run OFSExtractor in a command prompt pointing to the target archive.
3. Verify the extracted filenames. OFS archives often store internal names without extensions, so you may see files listed as raw sequences like tex_00421 or dialog_en_091.
4. Rename the extracted files based on the content. Textures are usually PNG or TGA. Audio files may be in ADPCM or WAV format depending on the platform version.
5. Use a hex editor to inspect any files that appear corrupted after extraction. This step caught my edge-case issue.

Common Pitfalls and What I Learned the Hard Way

The biggest mistake beginners make is assuming every OFS file in a Game of Thrones installation belongs to the same format version. The disc version and the digital download version often ship with different OFS builds. I ran into this when extracting cinematics. The disc build used a 4-byte entry size in the index table, while the digital build used 8-byte entries. My first dump produced valid filenames but zero functional video files because the byte offsets were misaligned. The workaround I ended up using was to compare the raw binary headers of both archives side by side in HxD. Once I identified the header offset difference, I adjusted the extraction parameters in OFSExtractor to scan for the correct index table position instead of assuming it was at the default location. That resolved the corruption issue entirely. Another issue involves Unicode string encoding. Some OFS archives store filenames in UTF-16LE format while others use UTF-8. When I extracted dialogue files from one build, the filenames appeared as null-separated character pairs instead of readable text. Switching the string decoder option in OFSExtractor from ASCII to UTF-16 fixed the naming problem. WinOFSTool has a similar toggle in its settings menu.

Modifying and Repacking OFS Archives

If your goal is to replace assets rather than just extract them, repacking is the next step. OFSExtractor includes a create mode that accepts a folder of modified files and generates a new OFS archive. The process takes approximately 10 to 15 minutes for a medium-sized asset bundle on modern hardware. When repacking, preserve the original directory structure inside the OFS container. The game engine resolves paths at runtime based on the internal string table, so changing a path from textures/gotham/armor/targa to textures/gotham/armor/png will cause the engine to silently skip the file and fall back to the unmodified version. I learned this after spending two days wondering why my texture replacement was not working, only to discover the internal path mismatch in the extraction log. File ordering inside the OFS archive also matters for load performance. The original archives are sorted by category and then by filename. When I repacked my modded archive in random order, the game still launched and functioned correctly, but memory allocation spikes became noticeable during scene transitions. Reordering the repacked files to match the original sequence eliminated the stutter.

When OFS Extraction Fails Completely

Some Game of Thrones releases ship with OFS files that are obfuscated or partially encrypted, particularly on PlayStation 3 and Xbox 360 builds. These files will open in WinOFSTool and list filenames correctly, but the actual content bytes will be scrambled. In those cases, standard extraction tools will not work. The only practical solution for encrypted OFS archives is to use a memory-dumping approach while the game is running. The Unreal Engine-based GoT titles decrypt assets into RAM before streaming them to the GPU. Tools like UE4SS or platform-specific memory dumper scripts can intercept the decrypted streams and write them to disk. This is slower and requires the game to be installed and running, but it is currently the only reliable method for fully encrypted OFS bundles. Another limitation to be aware of: OFS archives do not support nested sub-archives. If you encounter a .ofs file that itself contains other archive references, the standard tools will only expose the top-level entries. You will need to recursively process each embedded reference manually. This adds time but does not require specialized software beyond what is already listed.

Summary of Key Points

OFS archives in Game of Thrones games are custom container formats. Use OFSExtractor or WinOFSTool for extraction. Verify which OFS build version you are working with before extracting. Check the header offset and string encoding settings if the output looks wrong. Preserve internal paths when repacking. For encrypted builds, switch to memory dumping. This approach covers the vast majority of extraction and repacking tasks encountered in the modding scene for these titles.