timppu: I may have asked about this before... but in case you have a local library of GOG offline installers downloaded with gogrepo, how "compatible" is it with lgogdownloader, in case you switch to using lgogdownloader?
Does lgogdownloader download to a similar directory structure as gogrepo, placing each game's files under similarly named subdirectories? I recall lgogdownloader at least places extras differently, so is it then that in the worst case all extras need to be redownloaded (unless one moves them to a separate subdirectory manually for each game)?
The directory structure is set using various --subdir-* options.
Default options:
--subdir-installers ""
--subdir-extras "extras"
--subdir-patches "patches"
--subdir-language-packs "languagepacks"
--subdir-dlc "dlc/%dlcname%
--subdir-game "%gamename%"
Templates:
%platform% --> platform string (windows/linux/mac)
%gamename% --> name of the game
%gamename_firstletter% --> first letter of %gamename%
%dlcname% --> %gamename% of dlc
Default values result in directory structure that is something like this
gamename
โโโ dlc
โ___โโโ dlcname
โ_______โโโ extras
โ_______โ___โโโ dlc_extra.zip
โ_______โโโ patches
โ_______โ___โโโ dlc_patch.exe
โ_______โโโ dlc_installer.exe
โโโ extras
โ___โโโ extra1.zip
โ___โโโ extra2.zip
โโโ languagepacks
โ___โโโ languagepack1.exe
โโโ patches
โ___โโโ patch1.exe
โโโ linux_installer.sh
โโโ mac_installer.pkg
โโโ windows_installer.exe
timppu: Does lgogdownloader recognize that this and that games/files have already been downloaded and are present, even if they were not downloaded with lgogdownloader?
If the files are present in directory structure that matches what is set using --subdir-* options then lgogdownloader doesn't care how the files were originally placed there and will treat them as if they were downloaded with lgogdownloader
There are some exceptions to this:
1. It's not possible to use --repair --no-remote-xml before XML data is for the games is cached. lgogdownloader will try to get the XML data and save it automatically when trying to download a file so --no-remote-xml option should start working after the first run with --download
2. Using --repair with extras is not possible unless XML data is created for them first