Skip to content

1.0.2-5: Redid custom script
Compare
Choose a tag to compare
@rankynbass rankynbass released this 03 Nov 03:21
· 21 commits to main since this release
v1.0.2-5
c0f0cdf
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

I think including a user-editable launch script is a good idea. However, my initial implementations were buggy. So I've reverted the default behavior. There are now two .desktop files, "XIVLauncher Native" and "XIVLauncher Custom". The former will just run the launcher. It should always work. The second one will run ~/.local/bin/xivlauncher-custom.sh, which you can edit to add your own environment variables and such. I've used it to run the launcher through gamescope successfully, and I currently use it to run with a custom mangohud config and frame rate limit, while using amdvlk instead of radv for drivers.

From the terminal:

  • Running /usr/bin/xivlauncher with no arguements just launches XIVLauncher. This is the same as the "XIVLauncher Native" .desktop file.
  • Running /usr/bin/xivlauncher custom will check for $HOME/.local/bin/xivlauncher-custom.sh, and launch it if it's found and has valid bash syntax. This is equivalent to the "XIVLauncher Custom" .desktop file.
    • If the script is found, but is broken, it'll back it up and create a new one.
    • If it doesn't find the custom script, it will created it.
    • If the path $HOME/.local/bin doesn't exist, it will be created first. This fixes an error that was reported. This path is not part of the XDG basedir specs, but it is part of the systemd file heirarchy, and Fedora, openSUSE, Enterprise Linux, and most distros with systemd use it.
Assets 4
Loading