I made a programming error when improving mod pack support. My improvements in fact broke it completely (oh the irony, stop laughing). I’ve found and fixed it but the change won’t appear until patch 5, which isn’t too far away, but I imagine you would like a workaround now. To summarise the error, I am getting the precedence order checking the wrong way around. Precedence is declared in byte five of the pack file, immediately after the identification marker PFH4. Mod packs should use 3 for this byte. However, until the patch drops you can change this value to 5. Once the patch drops I can’t guarantee that your mods will work if you don’t switch the byte back to 3 (this has always been the case with mod packs). As I think has been described elsewhere, the lower three bits of the precedence byte are a simple ordering sequence thus:
0 Boot pack (there can be only one)
1 Release pack
2 Patch pack
3 Mod pack
4 Movie pack (special pack files which are opened in a different way from the others depending on our video playback solution)
Some have achieved a similar result, through good fortune more than anything else, by changing the byte to 4. If you’ll forgive the allusion
, four shalt thou not use. Five is right out (except for this brief period before the patch drop).
It really is gratifying to see so much modding going on: I first started work on the modding system a little over ten years ago back in Rome I. I do hope you derive a lot of satisfaction from it.
J Guy Davidson