Conty

Conty

It is possible to start x86 games using the container Conty. This can be enabled by either enabling AUTOCONTY (in this case Conty will always be used automatically when a 32bit game exe was found) or by enabling USECONTY (in which case Conty will be used, no matter which architecture the game exe has - for example useful for games using start scripts) Both options can be found in the corresponding game-menu

Alternatively AUTOCONTY can also be enabled, by simply dropping a game into the Steam Category Conty

If Conty is enabled either way, the conty.sh executable will be searched in this order:

• CUSTCONTY - A variable pointing to an absolute path to a conty.sh executable (can be set in the Global Menu or in the 'requester' described below)
• $CONTYDLDIR/$CONTY (usually resolves to ~/.config/stl/downloads/conty/conty.sh) (this is the place where stl autodownloads the executable - see 'requester' below)
• in $PATH (conty.sh in $PATH will be used)

requester:

If all above attempts fail, a requester will open where one can choose between:

• DOWNLOAD CONTY (automatically downloads conty.sh to $CONTYDLDIR/$CONTY - see below)
• SELECT LOCAL CONTY (opens a requester for conty.sh - the selected executable is saved as CUSTCONTY into the global config)
• SKIP CONTY (Conty will be skipped this time)

download:

When selecting download the latest version of Conty is automatically downloaded from the projectpage. If the sha256 checksum of the downloaded file doesn't match, the download will be removed. If UPDATECONTY is enabled (in the Global Menu, it is enabled by default) a function will automatically check for an available update and fetch it if available. The previous conty.sh file won't be backed up, as they are too big to automate this. A version.txt besides $CONTYDLDIR/$CONTY will be written/updated when a download was successful.