Pull request #6 is breaking new server setup

[aASDa213ASD]

So since the day you merged this PR #6, if you are trying to create a new server on a new hardware that has not yet been authorized, you will get stuck on the very beginning of start.sh. It looks this way:

No errors, no logs, just hang. Why it happens is pretty silly. While this part of start.sh works flawlessly w/out any authorization:

echo "Checking for hytale-downloader updates..."
$DOWNLOADER_BIN -check-update

This one, however won't work unless your machine-id is already authenticated:

AVAILABLE_VERSION_RAW="$($DOWNLOADER_BIN -print-version 2>&1 || true)"

The hang is because this command requires input, you can check by running this command manually:

So please, do something about it, because right now you simply CANT boot the server UNLESS you authorized the machine-id.
For those who need a hacky way to bypass this as of now - just run this command manually:

docker exec -it hytale hytale-downloader -print-version

Proceed with authorization and run hytale-start so that this stupid downloader finally downloads server files.
From there you can follow the words from README file in this repository to make auth persistent via docker attach hytale

[Slowline]

Hey, sry can you recheck with the newest version? The messages from the -print-version command where omitted i've added back the pipe so it lands in stderr

[aASDa213ASD]

Much better, can be closed:

I'll add this to my Makefile PR as well.