HGL
crude-lavender
Running .sh scripts in Heroic.
Hello. I have a game that I want to launch via a shell script. However, when adding the script to heroic, pressing play doesn't do anything. Running the script manually works just fine.
Solution:Jump to solution
You'll have to use an absolute path to
onscripter-en & make that path available in the sandbox, yes12 Replies
crude-lavenderOP•2mo ago
If you're wondering what the script is, (dunno if that's important,) it's just
onscripter-en --window-width 1280 /home/liams/Games/Tsukihime-Pack/Tsukihime/Game/
It's being run natively.conventional-tan•2mo ago
How do you own this game?
correct-apricot•2mo ago
@aidalgol ONscripter is an open source implementation of a popular visual novel engine.
@Freikugel Based on the video it looks like you're running into a Flatpak permission problem. The path to the script that Heroic is given by the file picker is different from the working directory in your terminal. You may need to grant the Heroic Flatpak access to the location where the visual novel is stored.
crude-lavenderOP•2mo ago
I tried giving it access to ~/Games/Tsukihime-Pack/Tsukihime/Game/ using flatseal, but it still doesn't wanna work.
but yeah, it does seem to be a flatpak permissions issue since the RPM executes the script just fine
Try spawning a shell in the Flatpak container & running your script through there
To start a shell, run
flatpak run --command=bash com.heroicgameslauncher.hglcrude-lavenderOP•2mo ago
works fine
Interesting
What's in the game log of Heroic now?
(run the
/gamelog command if you don't know how to get to that)To help you, we need a game log. Please see the following images on how to get it.
conventional-tan•2mo ago
It was the game folders that made ask.
crude-lavenderOP•2mo ago
https://0x0.st/KBc2.log
wait would i need to give it permissions to access ~/.local/bin too?
Solution
You'll have to use an absolute path to
onscripter-en & make that path available in the sandbox, yescrude-lavenderOP•2mo ago
Yeah using the absolute path in the script fixes it, makes sense. I was thinking that I didn't need to since it was in ~/.local/bin but ig that makes sense since flatpak does flatpak things