Zero byte files

[FarmitzDugan]

This looked really promising for a project I am working on. When I run it on my region files I just get 1024 zero byte files. Are you still working on this? I would love to get it working.

[sudofox]

Can you upload one of your region files for me to test against?

[FarmitzDugan]

Thanks for replying. I tried to run it on this...
r.-1.-1.mca.zip

Here is the screenshot of terminal when it is done running:

[sudofox]

Thanks for replying. I tried to run it on this...
r.-1.-1.mca.zip

Here is the screenshot of terminal when it is done running:

Sorry for the late reply, I've been super busy and didn't see it. I'll check it out really soon!

What OS are you using? It looks like it takes a different set of arguments for the date call

[FarmitzDugan]

Ah, I am using mac os Catalina. To be honest I have found another solution to get the data I need. I would be happy to keep troubleshooting with you but just know it is less urgent than before.

[fer-os]

I have been having this issue as well. I used the sh file in terminal and it returned a ton of blank .nbt files. Mac Catalina v10.15.3

[sudofox]

Unfortunately I don't have access to a Mac to test on, so I don't see being able to fix this in the foreseeable future.

It's a bit surprising people are actually using this haha maybe I ought to rebuild it in something better than abusing bash and xxd

[ultimatespirit]

This issue arises because your script relies on a GNU date extension flag -d not specified in the POSIX standard here. I don't know what $timestamp looks like to comment exactly on how to replicate that behaviour using BSD Date (the version macOS uses) but many times it is possible to replicate the behaviour of -d through the BSD date extension flags -j and -v.

That being said, I don't particularly recommend trying to fix tooling / POSIX incompatibilities through yet more non-POSIX features (now distro dependent too!). You'd probably be better off changing to an awk format or some other standardised method of displaying that timestamp.

For the macOS users currently attempting to use the script, the date is solely used for a verbose info statement it seems, so you can just remove the date command from that line or change it to gdate if you have GNU date installed.