I looked deeper into this, and the `PATCH.RE_` file seems to already have been applied to the `SCREAM.RES` file in all versions I could find? It overrides the same data in all language variants, so it can be reconstructed from any of the files in the EGS version. Here's a quick helper script i threw together with Claude Code:
https://gist.github.com/chkuendig/1dbb1 ... 68eb884bf3
This script produces the same file from any of the language versions in the epic release: (steam files have the same hashes, so they also already apply the patch)
Code: Select all
0cf2947caaa466c16267b8284efa4617 ./IHaveNoMouthAndIMusteUkBA/IHNMAIMS_Data/StreamingAssets/disk_EN/scream/SCREAM.RES
b20dd4b2697cbb94ef018bc787049da9 ./IHaveNoMouthAndIMusteUkBA/IHNMAIMS_Data/StreamingAssets/disk_SP/scream/SCREAM.RES
b60c33762572051e6c89ce086d456526 ./IHaveNoMouthAndIMusteUkBA/IHNMAIMS_Data/StreamingAssets/disk_GE/scream/SCREAM.RES
5ceb5d5a51fc7de6e0c3167373282abc ./IHaveNoMouthAndIMusteUkBA/IHNMAIMS_Data/StreamingAssets/disk_FR/scream/SCREAM.RES
55e89ac27ea2eac4f21339f4bcf42edf ./IHaveNoMouthAndIMusteUkBA/IHNMAIMS_Data/StreamingAssets/disk_IT/scream/SCREAM.RES
Still always ends up with the same `PATCH.RE_` the steam release has (md5sum: a88a9182abd95ed2af059ef28af9f4700
I have a suspicion we can remove the patch from the detection, but I'm not sure if there are older version that need it (and how we could differentiate this, given that the patch affects the middle of the file)