Posted November 06, 2025
Thank you so much for this downloader. I only just discovered this and it works great!
Is it possible to get a %version% variable for different game/DLC installer versions?
--list details already shows the version number for each game, so I imagine it would be possible.
Of course, using such a variable for directory names could present some problems:
1. Some games have no version number, so maybe these could output "none"?
2. Rarely a version number will have '/' in them. I've only run into one game that had this - System Shock Remake (2023).
"transformations.json" might be used for avoiding these edge cases?
I ask because my collection is currently sorted as:
./(gametitle)/(platform)/(version#)/[installers_go_here]
and if applicable:
./(gametitle)/extras/[extras_go_here]
./(gametitle)/(platform)/patches/[patches_go_here]
./(gametitle)/(platform)/(version#)/DLC/[DLC_installers_go_here]
Because DLCs should always be for the same version of the game that is downloaded, I place them in a subdir with the base game installers. Avoids redundancy with version number directories. I wouldn't mind the DLCs being named separately per DLC, but I think that's already possible. I separate patches into subdirs too, though this might already be possible too. If not, a variable for patch names could solve that.
Speaking of, is --subdir-dlc intended behavior to store DLC installers and extras in the same folder? DLC and extras appear to get lumped together. I understand that the extras are technically "DLC", but there's a separate argument for --subdir-extras, so I would have thought DLC installers would be exclusively for --subdir-dlc. Any chance this will change in the future? or perhaps another option such as "--subdir-dlcinstallers"? I can't get this to work with my current folder structures.
One last question:
Is it possible to use --exclude in gamespecific configs? (ie. "exclude" : <string>) This might already be possible, but the examples didn't mention it and I couldn't figure out how to get it working if it does. I often find it's easier to imply "--include all" with the default config and than exclude specifics I don't want.
Anyway, huge thanks to all the work done on this project! Being able to download Galaxy builds without Galaxy is liberating and maintaining my collection will be much easier thanks to this tool!
Is it possible to get a %version% variable for different game/DLC installer versions?
--list details already shows the version number for each game, so I imagine it would be possible.
Of course, using such a variable for directory names could present some problems:
1. Some games have no version number, so maybe these could output "none"?
2. Rarely a version number will have '/' in them. I've only run into one game that had this - System Shock Remake (2023).
"transformations.json" might be used for avoiding these edge cases?
I ask because my collection is currently sorted as:
./(gametitle)/(platform)/(version#)/[installers_go_here]
and if applicable:
./(gametitle)/extras/[extras_go_here]
./(gametitle)/(platform)/patches/[patches_go_here]
./(gametitle)/(platform)/(version#)/DLC/[DLC_installers_go_here]
Because DLCs should always be for the same version of the game that is downloaded, I place them in a subdir with the base game installers. Avoids redundancy with version number directories. I wouldn't mind the DLCs being named separately per DLC, but I think that's already possible. I separate patches into subdirs too, though this might already be possible too. If not, a variable for patch names could solve that.
Speaking of, is --subdir-dlc intended behavior to store DLC installers and extras in the same folder? DLC and extras appear to get lumped together. I understand that the extras are technically "DLC", but there's a separate argument for --subdir-extras, so I would have thought DLC installers would be exclusively for --subdir-dlc. Any chance this will change in the future? or perhaps another option such as "--subdir-dlcinstallers"? I can't get this to work with my current folder structures.
One last question:
Is it possible to use --exclude in gamespecific configs? (ie. "exclude" : <string>) This might already be possible, but the examples didn't mention it and I couldn't figure out how to get it working if it does. I often find it's easier to imply "--include all" with the default config and than exclude specifics I don't want.
Anyway, huge thanks to all the work done on this project! Being able to download Galaxy builds without Galaxy is liberating and maintaining my collection will be much easier thanks to this tool!