BitTitan

In your source path does it have C:\GAMEZ\Red Dead Redemption 2\update.rpf\x64\ -- which I think should be update_4. I use CodeX instead of OpenIV for paths. Though werewolf's script really only looks for the .rpf -- for instance my paths are RDR2\blah\blah and it'll translated the .rpf's just fine. Missing that _4 is kind of important because there isn't a key for just update.rpf. I suppose you could that key in his script because all the update's mount at the same place.

Might as well be called "Yet Another Gamerconfig.xml" So it's a band aid, or in the case of one of the gameconfig.xml's will actually cause the bug

There's something wrong with your update_1 path. Where it has the full path /update.rpf/blah/blah instead of update:/ -- that should be an update_1 and translated by the script to be update:/ Since I've been writing a powerautomate routine to query the path's from CodeX I've learned that R* likes to reuse names sometimes, weaponcomponents.meta just bit me in the ass for most of the night trying to figure out why I was crashing since the M1899 pistol and the base weapons both share the same name. But I'm gone through and rebuilt 150 mod's installs at this point with only a few problematic ones. I just restarted so I need to fly over to Denis and see if the trolley have people still, but my stream folder is running pretty thin; which is great!

@werwolf969 -- Dude you are a hero among men 😄 I'm looking at modifying your updated (Duplicates=True) version so that it also outputs to /nested/game/path/folder/moddedfile.ext.txt. Reasoning for this is I use ModOrganizr to manage RDR mods. After over a decade of Bethesda modding, I'm spoiled in what a mod manager should do. I'm still limited by what RDR requires to inject modded files, but your scripts and masochist methods of managing modded files is working well -- I think. Because I'm choose to not rely on LMM to handing conflict detection; frankly I'm not even sure LMM has conflict detection outside of looking the log file for OVERWRITE. My PowerShell-fu is weak and I'm converting Linux shell logic into PowerShell, but I'll get there soon as I figure out the translation and logic differences. My napkin logic (which at this point looks like the broken English of coding) is: mkdir -p nested\${RemainingPath}\${MatchingFile}.txt I'm not 100% on which variables make the most sense and obviously that syntax is now PowerShell.