Mod Pak Merger

Pak Merger

Overview

Pak Merger was created to address a common problem when using multiple mods in OCTOPATH TRAVELER 0 & 2: two mods may include their own complete copy of the same game database file, so whichever Pak loads last can overwrite every change made by the other one.

This tool compares the selected mod Paks and builds one combined Pak. Changes that do not overlap are merged automatically. If two mods change the same field to different values, Pak Merger shows the conflict and lets you choose which mod's value to keep.

The goal is simple: keep the compatible changes from every selected mod instead of losing an entire mod's edits because of Pak load order.

How It Works

• []Files and database entries found in only one mod are added automatically.[/]

  []Identical content shared by multiple mods is kept once.[/]

  []Separate changes within a supported database can be combined field by field.[/]

  []When the same field has different values, you choose the Pak whose value should be used.[/]

  One selected input is used as the Base Pak. It supplies the starting file layout and the saved form of data that does not need a manual choice. It does not automatically win conflicts, and the order in which Paks were added does not decide the result.

  Pak Merger works directly with unencrypted mod Paks. It does not require the original game Pak, an AES key, or UnrealPak.

  Example: Detailed Skill Descriptions + Extra Boss Challenge

  Suppose you want to use Detailed Skill Descriptions together with Extra Boss Challenge.

  Extra Boss Challenge adds text for its new skills by including a modified copy of the English skill-text database. Detailed Skill Descriptions also modifies that database to replace existing skill descriptions. If both original mod Paks are loaded normally, one complete copy of the database can overwrite the other, depending on load order.

  With Pak Merger:

  • []Add both mod Paks and analyze them.[/]

    []The text added exclusively by Extra Boss Challenge is carried into the combined database automatically.[/]

    []For existing skill-text fields changed by both mods, select the Detailed Skill Descriptions version.[/]

    []Create the merged Pak.[/]

    The result keeps the new entries required by Extra Boss Challenge while using the Detailed Skill Descriptions text for the overlapping entries, allowing the two sets of changes to coexist in one Pak.

    Requirements and Supported Scope

    • []Windows x64[/]

      []Unencrypted Unreal Pak input versions v0 through v11[/]

      []Uncompressed, Zlib, Gzip, Zstd, LZ4, and Oodle-compressed input Paks[/]

      []Uncompressed or Oodle-compressed output[/]

      []Korean, English, and Japanese interface languages[/]

      Pak Merger can also read many unencrypted Unreal Paks from other games, but this does not mean that every Unreal game or every asset type can be merged field by field. Files without a matching game rule are handled conservatively. Simple compatible database values may still be compared, while complex or unknown assets are kept together and require a whole-file choice when they differ.

      Encrypted Paks and IoStore containers (.utoc / .ucas) are not supported. There is no AES-key entry feature.

      Oodle support requires oo2core_9_win64.dll. This DLL is not included in the download. If it is needed and is not already beside the executable, the built-in loader can download and verify it automatically. The first Oodle operation therefore requir