-
Notifications
You must be signed in to change notification settings - Fork 17
SSGL First Setup
If you have Problems with the Setup, you can also always hop into the SSGL Discord Server, we are a friendly Bunch.
When you start SSGL the first time it creates a Application Configuration Directory which you can find here:
%APPDATA%/ssgl-doom-launcher on Windows
$XDG_CONFIG_HOME/ssgl-doom-launcher or ~/.config/ssgl-doom-launcher on Linux Systems
~/Library/Application Support/ssgl-doom-launcher on Macs
And here are your Settings, Packages and Sourceports stored as JSON Files.
The Directory where ALL your Mods and iWADS are stored, SSGL is able to differentiate between iWads and Modfiles while crawling through the Directory structures. This directory has not to be Flat, you can even filter through the last 3 Directories in SSGL itself.
SSGL "sees" the following Mod Fileextensions:
- PK3
- PK7
- WAD
- DEH
- BEX
- BEH
- DEH
- CLD
- ZIP
- RAR
- 7z
SSGL can "identify" the following iWads
- chex
- chex2
- doom
- doom2
- doom64
- freedm
- freedoom1
- freedoom2
- hacx
- heretic
- heretic1
- hexdd
- hexen
- plutonia
- strife0
- strife1
- tnt
If you configure a Sourceport with Config and Savefile Seperation, SSGL uses and manages this directory for Savefiles and Configfiles based on the Sourceport and the Package.
Oblige is a Random Map generator if you need help to compile it on MacOS here i have written up how i did it.
To save a config in Oblige, first setup your wanted settings in Oblige - after that:
Menu -> Config Manager then in the Config Manager hit Save
And Save this Build Configurations as an .txt File in a seperate Directory (see Oblige Build Configs)
The Path to the Oblige Binary or Oblige.exe
The Path to the Directory where your Oblige Build Configurations are.
Select the Sourceport file here, a Compatibility Table as also Recipies for the different Sourceports will come
Gets defined automatically by name of the Sourceport, you can change that name if you for example want to manage different Versions of a specific Sourceport
SSGL is able to manage and load Sourceport Configfiles based on a "Package", so you can configure your Sourceport and Keybindings to your liking for every Package seperately.
If this Checkbox isnt activated always the global Config of the Sourceport are loaded.
Sourceport parameter for "selecting" a config when starting (defaults to GZDooms -config)
Required when Seperate Config by Package is active
Gets automatically filled out when you select a default Config file, this is the name of the Configfile to generate. (example: gzdoom.ini)
You can define here a "global config file" from your Harddisk which gets copied over everytime you create a Package. If this field isnt defined - The Sourceport created default will be used.
SSGL is able to manage and load your Savegames based on a "Package", so you only see the Savegames which are compatible with your Package in the Ingame load menu, or load the last Savegame automatically if you start a Package from the Package View.
If this Checkbox isnt activated always the global Save Directory of the Sourceport is used.
Required when Seperate Savegames by Package is active
Save Directory Parameter for the Sourceport (defaults to GZDooms -savedir)
Required when Seperate Savegames by Package is active
Load Game Parameter for the Sourceport (defaults to GZDooms -loadgame)