So far I've been using the Compress-Archive command from PowerShell to pack up the zips in batch. This method causes the file paths to use backslashes, causing incompatibility with Unix file archivers (unless the actual program used for extraction is aware of this).
One such utility is KDE's Ark. Instead of displaying folders, it instead displays the full path as: "scripts\NFS_XtendedInput.asi".
Solution: I'll probably just use a command-line version of 7z or gzip. No big deal here.
Issue 2: Case-sensitivity and the "Global" folder
In the case the game is ran on a case-sensitive filesystem, the game will prefer to look for uppercase paths (because of the string hashing).
Moreover, the games were packed with uppercase paths since UG2 and their original casing was lost somewhere during the packing procedure during development.
Solution 1: This folder should probably be just renamed to uppercase to avoid any trouble.
Solution 2: In case 1 fails, the TPK should be relocated somewhere in the "scripts" folder.
Issue 1: Paths generated by
Compress-Archive
PowerShell command use backslashes instead of packing them correctlyThis was recently revealed to me in this issue: https://github.com/ThirteenAG/WidescreenFixesPack/issues/1144
So far I've been using the
Compress-Archive
command from PowerShell to pack up the zips in batch. This method causes the file paths to use backslashes, causing incompatibility with Unix file archivers (unless the actual program used for extraction is aware of this).One such utility is KDE's Ark. Instead of displaying folders, it instead displays the full path as: "scripts\NFS_XtendedInput.asi".
Solution: I'll probably just use a command-line version of 7z or gzip. No big deal here.
Issue 2: Case-sensitivity and the "Global" folder
In the case the game is ran on a case-sensitive filesystem, the game will prefer to look for uppercase paths (because of the string hashing).
Moreover, the games were packed with uppercase paths since UG2 and their original casing was lost somewhere during the packing procedure during development.
Solution 1: This folder should probably be just renamed to uppercase to avoid any trouble.
Solution 2: In case 1 fails, the TPK should be relocated somewhere in the "scripts" folder.