PakChunk conflict checker

A Windows batch script to check if the mods in your ~mods folder use the same pakchunk.

PakChunk conflict checker

📖 Introduction

Although there is already a Chunk ID Conflict Manager to resolve pakchunk conflicts, sometimes we don't want to resolve conflicts, but just want to check whether the module we just created conflicts with existing modules. So I created this batch script to check. **It will not resolve any conflicts, it will only tell you if there is one. **

---

📦 Installation

• **Download the module. **
• Extract the **PakChunkChecker.bat** file and **MANIFEST** folder into your `Steam\steamapps\common\Hogwarts Legacy\Phoenix\Content\Paks\~mods\` folder.
• Make sure that the **PakChunkChecker.bat** file and **MANIFEST** folder are placed in `Steam\steamapps\common\Hogwarts Legacy\Phoenix\Content\Paks\~mods\Phoenix\Content\Paks\~mods\` without errors!
• If misplaced, please move them to the correct `~mods` folder and delete the redundant `Phoenix` folder.

---

🚀 How to use - the easy way

**Method 1:**

• Double-click **PakChunkChecker.bat** in Windows Explorer.

**Method 2:**

• Hold down the **ALT** key and drag and drop **PakChunkChecker.bat** from Windows Explorer to the desktop.
• This will create a shortcut that you can rename as you like.
• Double-click the shortcut to run the batch file.

---

💻 How to use - command line method

• Open a cmd window (**DO NOT** run as administrator).
• Switch to your `~mods` folder.
• Run `PakChunkChecker.bat`.

In other words, do what's shown below (but adjust it based on the location of your `~mods` folder). In my case, the `~mods` folder is on the D drive, so I need to switch drives (using the `d:` command) and then `cd` to the correct folder. If your `~mods` folder is on the C drive, there is no need to switch drives.

As shown in the example above, the `zBPApparate_P` module (Blueprint Apparate Modloader) conflicts with `pakchunk102-WindowsNoEditor` (the module I just created). They have the same PackageID (which is the hash of the pakchunk number). If two modules have the same PackageID, then they must be packaged with the same pakchunk number.

We usually don't know which pakchunk was used (because the hash function is not reversible), but in this case, we can know from the file name (and because I just created it) that `pakchunk102-WindowsNoEditor` uses pakchunk 102, so the `zBPApparate_P` module must also use pakchunk 102. So, I have to use a different pakchunk for my mod.

My `zMySLowMo-103_P` mod also conflicts with `pakchunk103-WindowsNoEditor` (which is an earlier version of the same mod that I forgot to rename and delete).

For conflicts between mods that you **didn't create**, use the Chunk ID Conflict Manager to resolve them.

---

🗑️ How to uninstall

Just delete the **PakChunkChecker.bat** file from your `~mods` folder. You can also delete the **MANIFEST** folder, **unless** you have my Mod Merger Checker mod installed, in which case please keep the **MANIFEST** folder, otherwise it will break that mod.

---

⚠️ Known issues

• This script will search your `~mods` folder (and all its subfolders), but mods placed in a folder one level above (i.e. the `Paks` folder) will also be loaded by the game, and this script cannot find them. If you have any mods in the `Paks` folder, they should be moved to the `~mods` folder.

---

🎉 Acknowledgments

Thanks to Menv for UEcastoc, which my script uses to generate the manifest file.

---

❓ Conflict Report

If you find any conflicting mods, please report them in the Posts section to keep the community informed. Thanks! 😊