Mod import failed: Error: ENOENT: no such file or directory about starfield-mod-loader

[lVlyke]

Thanks for the bug report.

I’m also able to reproduce this issue on Linux, and after some digging, it appears that the zip files for these mods are using backslashes for path separators instead of slashes, which causes issues when extracting the files on Linux (and is also invalid according to the .ZIP file spec):

      4.4.17.1 The name of the file, with optional relative path.
       The path stored MUST NOT contain a drive or
       device letter, or a leading slash.  All slashes
       MUST be forward slashes '/' as opposed to
       backwards slashes '\' for compatibility with Amiga
       and UNIX file systems etc.  If input came from standard
       input, there is no file name field. 

Most filesystems on Linux use forward slashes for path separators and allow backslashes as part of the file name. When these zip files are extracted on Linux, the backslashes are interpreted as part of the file name, resulting in a file being created with the path as part of the file name itself (i.e. Data\SFSE\Plugins\BakaAchievementEnabler.dll). You can see the issue here when opening one of the zips with an archive utility like File Roller, where it shows a file with the backslash’d path as part of the file name:

Unfortunately, there’s not much I can do on my side for this issue. I could try to code in a workaround to detect this case and try to fix the folder structure on the fly, but it would be messy platform-specific code that could cause other issues, so I would rather avoid it, especially since this seems to be a pretty rare issue.

I would let the author of these mods know about the issue. Hopefully they can correct the problem with the tool they’re using to generate these zip files to make sure they are created with forward slashes.

As a workaround until then, you should be able to extract the files manually and then create the correct folder structure and fix the file names. You can then import the corrected files directly into the mod loader. Alternatively, if you have access to a Windows machine, you could extract the files on it first and then copy them over to import into the mod loader.

[Alkali-V2]

A simple fix is good enough for me. I was able to extract the items, create valid directories and get it imported correctly so that is all I needed. Not sure why he made the directory like that but for now I'll use the workaround. Thank you for confirming it wasn't just on my side and for your help getting this sorted out!