Skip to content

Environment Variables

Marvin1099 edited this page Jun 24, 2024 · 6 revisions

You can use Environment variables in from of the script to Access some functionality, You may want to use the config file instead of the Environment variables, but sometimes it may not be possible to use the config file, in that case you can use the following:

  • FORCE_UPDATE_WEMOD=1 to force update wemod.exe
  • REPO_STRING=DaniAsh551/wemod-launcher sets the repo link part to use for download
    to use replace DaniAsh551/wemod-launcher with the desired username and reponame
  • PACKAGEPREFIX=true to make a zip of your active prefix
  • WEMOD_LOG=wemod.log sets the WeMod log path
    to use set wemod.log to the desired path
  • WINE_PREFIX_PATH=$PPath to set the path of the wineprefix
    if you are using a extenal runner (like GE-Wine on Lutris)
  • SCANFOLDER=$PrefixFolder to change the folder to look for the prefixes in (Like /home/$USER/games).
    Keep in mind this folder is expected to have many prefixes so don't use a prefix folder but the parent folder.
    For example /home/$USER/games/planet-crafter/pfx/drive-c/ is 3 folders to deep,
    you want to use /home/$USER/games instead.
  • SELF_UPDATE=False to block launcher auto updates.
  • TROUBLESHOOT=False or True to disable / enable the troubleshooter.

Example

If you are using Environment variables your Launch Options may look like this:

PACKAGEPREFIX=false FORCE_UPDATE_WEMOD=1 /home/$USER/wemod-launcher/wemod %command%