PakChunk Checker

Versions

See the "Changelogs" dropdown just above.

Introduction

There's already a Chunk ID Conflict Manager to resolve pakchunk conflicts, but I didn't want to resolve conflicts. I just wanted to check whether the mod I'd just created conflicted with any of the mods I already had. So I created this batch script to check. It doesn't resolve any conflicts, it just tells you if there are any.

Installation

• []Download the mod.

  []Extract the PakChunkChecker.bat file and the MANIFEST folder into your

  Steam\steamapps\common\Hogwarts Legacy\Phoenix\Content\Paks\~mods\ folder.

  []Make sure the PakChunkChecker.bat file and the MANIFEST folder didn't end up in

  Steam\steamapps\common\Hogwarts Legacy\Phoenix\Content\Paks\~mods\Phoenix\Content\Paks\~mods\ by mistake!

  If they did, move them to

  Steam\steamapps\common\Hogwarts Legacy\Phoenix\Content\Paks\~mods\

  and delete the unnecessary

  Steam\steamapps\common\Hogwarts Legacy\Phoenix\Content\Paks\~mods\Phoenix folder.

• []Double click PakChunkChecker.bat in Windows Explorer.
  • []Drag & drop PakChunkChecker.bat from Windows Explorer to your desktop while holding ALT.

    []That will create a shortcut. Feel free to rename it.

  • Double-click the shortcut to run the batch file.

    Usage - Harder Method

    1) Open a cmd window. (Do not run it as Administrator.)

    2) Go to your ~mods folder.

    3) Run PakChunkChecker.bat

    In other words do what you see in the image below (but amend it to reflect the location of your ~mods folder).  In my case the ~mods folder is on my D: drive so I have to change drive (using the "d:" command) then cd to the right folder. If your ~mods folder is on your C: drive you won't need to change drives.

    As you can see in the above example the zBPApparate_P mod (Blueprint Apparate Modloader) conflicts with pakchunk102-WindowsNoEditor (which is the mod I just created). They both have the same PackageID (which is a hashed copy of the pakchunk number). If two mods have the same PackageID then they must have been cooked using the same pakchunk number.