I'm also using a bash script for startup, but if you want use a desktop shortcut you could define it in this way:
Code:
[Desktop Entry]
Name=Civ4:BtS with Mod
Comment=Start Civ4:BtS with given mod
Path={YOUR_PATH_TO_CIV4BTS}
#Exec=wine Civ4BeyondSword2015.exe "mod= CloseToHome_2.0.5"
Exec=env WINEPREFIX="{YOUR_WINEPREFIX_FOR_CIV4}" wine BTS_Wrapper.exe multiple mod= "PB Mod_v9"
Icon=Civ4BtS-1
Terminal=false
Type=Application
Categories=Game;
Notes:
• I inserted an example startup for the BTS_Wrapper.exe and one for Civ4BeyondSword2015.exe
• You as to adapt {YOUR_PATH_TO_CIV4BTS} and {YOUR_WINEPREFIX_FOR_CIV4}
• If you only use the standard-prefix for all wine programs you could omit the definition of the WINEPREFIX variable.
• The *.desktop-files do not support environment variables like $HOME on its own. So use the full paths or encapsulate your command with 'sh -c'
• If you want a proper Icon for the entry you need to convert the *ico-File manually because its format is not supported directly:
E.g. with Imagemagick's convert tool:
Code:
convert {YOUR_PATH_TO_CIV4BTS}/Assets/res/Civ4BtS.ico ~/.local/share/icons/Civ4BtS.png
Creates Civ4BtS-0.png, Civ4BtS-1.png, and Civ4BtS-2.png
• Maybe you noted the 'multiple' argument in the startup command. This is useful to start multiple instances of Civ4.
• An other useful argument is '/fxsload'. This can be used to load a save game. Good for debugging stuff
A drawback is the syntax. You need to give the full path in Windows-Path-Style.
Example call:
Code:
WINEDEBUG=-all WINEPREFIX="/home/{USERNAME}/.local/share/wineprefixes/wine32" wine BTS_Wrapper.exe "/fxsload=\"C:\\users\\{USERNAME}\\Documents\\My Games\\Beyond the Sword\\Saves\\single\\Test.CivBeyondSwordSave\"" multiple mod= "PB Mod_v9"