Installing Dying Light 2 pak mods by hand: the source folder and data file numbers
This guide is for Dying Light 2 players who want to install pak mods themselves instead of relying on a mod manager. By the end you will know where the files go, how to pick a number that will not clash with anything, and how to take a mod back out if it causes trouble.
Most Dying Light 2 mods arrive as a single file named something like data2.pak, data3.pak or data4.pak. That file goes straight into phsource folder inside your game install folder. It does not go into a subfolder inside phsource, just loose in that folder alongside the others.
Check what is already there first
Before you drop anything in, open the phsource folder and look at what already exists. The game keeps its own archives there, including data0.pak, which is part of the base game and must not be touched or overwritten. Any mod you add needs a number that is not already in use.
Never rename a new mod file to match an existing file name and copy it over the top. That overwrites whatever was there, whether it is a game file or another mod, and you will likely break both.
Picking a free number
If the number on your downloaded file is already taken by another pak in the folder, rename the new file to a free number instead. There is no single rule for how high you can go. Mod authors set their own limits because some mods expect to load in a particular order relative to others, so check the mod page rather than guessing.
- Open phsource and note every data number already present.
- Open the mod page or readme and check if the author names a specific slot, for example data4.pak, or gives a range they are comfortable with.
- If no specific slot is required, choose the lowest free number and rename the file to match, keeping the .pak extension.
- Place the renamed file into phsource and leave everything else in that folder untouched.
- Launch the game and confirm the mod is working before installing anything else.
Some authors say not to go past data7.pak, others allow up to data9.pak. Staying as low as possible, rather than always reaching for the highest free number, tends to cause fewer problems when you add more mods later. Follow what the specific mod page says over any general rule.
Mods with a fixed slot
A few mods are written to only work in one exact slot, for example data4.pak specifically, and the author will say so on the mod page. If that is the case, do not put a different mod in that same slot. If you are updating a mod that used to sit in an older slot and the new version wants a different one, delete the old pak file first so you are not left running two versions at once.
Uninstalling a pak mod
Removing a mod installed this way is simple: delete the pak file from phsource. There is no other cleanup step for a plain pak mod.
If you are not sure which numbered file belongs to which mod, .pak files open like standard archives in WinRAR or 7-Zip. Open the file and look at what is inside to confirm which mod it is before you decide to delete it.
Texture mods that edit rpack files
A small number of mods, mostly texture mods, go further and edit .rpack files such as common_textures_0_pc.rpack using a tool called 010 Editor. This is a separate and more involved process than dropping a pak file in a folder. Back up the original rpack files before you start, and follow the author’s exact steps rather than improvising, since a mistake here is harder to undo than deleting a pak.
Custom maps are not pak mods
Custom maps built with the free Developer Tools DLC are a different category entirely. They are shared through mod.io, not as pak files, and the installation process for those is handled through that platform rather than the phsource folder.
If something goes wrong
If the game fails to start or crashes after adding a pak file, remove the file you just added and try launching again to confirm it is the cause. If several mods are installed, remove them one at a time rather than all at once, so you can tell exactly which one is the problem.
Always back up your save files before installing anything new. There is no official list confirming which pak mods are safe to use in co-op, so read each mod page carefully and avoid gameplay-changing mods when playing with people you do not know.
Keep a simple text note listing which data number corresponds to which mod as you install more of them. It saves you from having to open archives to work it out later.
