I was still working under the caveat that content mods need to be installed before texture mods. That doesn't change, regardless of sfar unpacking. What the unpacking does is prevent a texture-modded pcc from overwriting a content-modded pcc when it is repacked in the sfar (the old method that texplorer doesn't use anymore).
This is how I see it working:
1. The user extracts their DLC. either via DLCEd2 or Texplorer. The key is that both methods have to extract all files, so we can assume every user has all DLC files extracted.
2. User installs MEHEM/TM/JAM. Main files and DLC files are replaced via an installer.
3. User might have to run a main game/DLC TOC.bin update, depends on the mod.
4. User installs texture mods.
Problem is that right now Texplorer only unpacks pcc and tfc files. We need to make sure that all DLC files are unpacked, standard. Then that means as content modders we can make installers that handle any DLC file just as if it was a main game file. That means no concerns about sfar size, having a vanilla install, using .mod files, etc. And, it's easier for the user.
It does not solve the problems of PCC replacement, i.e., overwriting a user's current, modded PCC with another modded PCC. But, my impression is that sfar unpacking wasn't supposed to solve that issue. It was to ensure files didn't get overwritten inside the sfar, which was the only way that both texture mods and content mods could be applied until unpacking came along. Basically, you had to pick one or the other if both modified the same file.
Now, assuming that content mods are applied first, users can texture mod DLC files til their hearts content.





Retour en haut







