Messages

The zipfile is now working properly. Thanks!

Oh, and good job with the mod itself, I kind of forgot to mention that. Yeah.

n0cifer,
when the "v" cause some problem maybe you should try a different zip-tool ?

I did that and indeed it extracted correctly.

and btw. the difference between the source code archive and the release are, the source code are missing the assemblies file, they need to be compiled.
So the source code archive is no useable mod (except the mod don't have any assemblies).

Oh right, I forgot about the assemblies... *facepalm* Thanks for the heads up! I guess I could have just copied over the assembled files from the non-source archive, but either way it's fine now since I was able to decompress the archives properly.

^ Yes what Canute said, you cannot use the source archive as it does not contain the files needed for the mod to run. You might have to try a different unzipper, not sure about what ones are good for linux. I will look into making the zips a little more cross-platform friendly for the next release.

Thanks for looking into this.

I managed to isolate the problem in 7zip; if I run any other unzip tool everything works as it should. Judging by the fact that out of the ~150 mods I'm currently using there are only 4 or 5 with this issue (not to mention the multitudes of zip archives I work with everyday), and also by the fact that @bigheadzach says they've also encountered this problem on a Mac before (which means it's not Linux-specific), I'd be willing to bet it's an incompatibility with the software used to create those problematic zip archives (e.g. a specific version of WinRAR or WinZip or even 7zip for Windows). So if I could offer a suggestion, if it's not too bothersome for you, you could try using a different software to compress the next release of RimHUD, and then I can check if that resolves the issue. If not... well. One thing at a time

Nope. When I open 'RimHUD-v1.1.0.2.zip' (with the 'v' before the version number - that's the one causing issues for me, the sources are OK) its contents are as shown in the first attachment, and extracting it results in a flat structure as shown in the second attachment, complete with backslashes in the filenames and everything. But then again I'm on Linux, so slashes of whatever kind in filenames are nothing new to it.

Anyway, don't fret about it, if I'm the only one having this problem then it's no big deal since the other two archives do the job properly. As I said, I was just curious


[attachment deleted due to age]

So... am I the only one encountering the following "issues"?

1) The RimHUD-v1.1.0.2.zip archive on the GitHub releases page is just a flat archive with files named after the actual, proper folder structure (e.g. there is a file called 'RimHUD/About/About.xml' in archive root instead of a file called 'About.xml' in a folder called 'About' in a folder called 'RimHUD' in archive root).

2) The 2 source code archives are properly organized.

Would this mean that one should download the source archive and forget about the "proper" release archive?

The issues are trivial really, I'm just curious

EDIT: I just noticed that it also happens with a couple of other mods as well. I assume the non-source archives were manually created and then uploaded to GitHub? If that is so, it might be an incompatibility with the compression software used. Could you by any chance be using a Mac?