Hi,
It looks like Zero-K for Steam on Linux now checks for Zero-K.exe in a "bin" folder under the install directory, and because Steam downloads the exe to the top level installation folder, and not under "bin", does a second round of installation.
The script looks like this:
#!/bin/sh
installdir=$( dirname "${0}" )/bin
cd "$installdir"
if [ -f "$installdir/Zero-K.exe" ]
then
mono Zero-K.exe "$@"
else
if [ -f "$installdir/setup-zerok.sh" ]
then
/bin/bash setup-zerok.sh "$@"
else
zenity --info --title "Error!" --text "Zero-K installation file was corrupted\! Please remove installation and redownload."
fi
fi
It should probably be more like this:
#!/bin/sh
installdir=$( dirname "${0}" )
cd "$installdir"
if [ -f "$installdir/Zero-K.exe" ]
then
mono Zero-K.exe "$@"
else
if [ -f "$installdir/setup-zerok.sh" ]
then
/bin/bash setup-zerok.sh "$@"
else
zenity --info --title "Error!" --text "Zero-K installation file was corrupted\! Please remove installation and redownload."
fi
fi
Also if the setup-zerok.sh script would be at the top level install dir, this problem would probably not exist, since it would only download Zero-K.exe if newer than the one provided by Steam, and Zero-K wouldn't need to run the self-updater and re-download all mods and maps.