That actually fixed it, thanks for the help
Happy to help. Happens on a few games, not sure why, but check the flag on the .sh to see if it is marked as executable:
That's what it should look like:
~/games/Bad-Memories-0.9.5-market via v3.12.3
❯ ls -alh Bad-Memories.sh
-rw
xr-
xr-
x 1 user group 1.7K Sep 9 2022 Bad-Memories.sh
And that's what it looks like "out of the box":
~/games/Bad-Memories-0.9.5-market via v3.12.3
❯ ls -alh Bad-Memories.sh
-rw-r--r-- 1 user group 1.7K Sep 9 2022 Bad-Memories.sh
I am using Bad Memories because we are here, but it happens to many games.
and if you want to know where the linux executeable is check the sh file itself:
LIB="$ROOT/lib/$PYTHON-$RENPY_PLATFORM"
RENPY_PLATFORM="$(uname -s)-$(uname -m)"
case "$RENPY_PLATFORM" in
Darwin-*|mac-*)
RENPY_PLATFORM="mac-x86_64"
;;
*-x86_64|amd64)
RENPY_PLATFORM="linux-x86_64"
;;
*-i*86)
RENPY_PLATFORM="linux-i686"
;;
Linux-*)
RENPY_PLATFORM="linux-$(uname -m)"
;;
*)
;;
esac
basically it tells you that the we want the lib directory and in there one of the following. So if you go to the lib folder you can see which is which. but like in this case:
lib/py3-linux-x86_64/Bad-Memories
which also requires the executable flag because the .sh file just really executes that one.
Happy hunting.
W