Thanks for making this launcher portable in #364!
As https://theforceengine.github.io/Documentation.html states:
Note that TFE stores saves, set up info, screenshots, log files, and similar items under Documents/TheForceEngine/. A portable installation option, where all data is kept in the local directory, is planned for the future.
But that's not actually true, as there is already a way to avoid that by creating an empty settings.ini - see #571 for the documentation request of this.
In any case, what's still missing is a way to define a custom folder or even a subfolder, so as to separate the launcher's static data from the dynamic settings.
TheForceEngine/TFE_FileSystem/paths.cpp checks for settings.ini via bool isPortableInstall().
What I suggest is to support having a setting in that file like custompath_generic=.\data and/or custompath_darkforces=.\data\Dark Forces, which will make sure the following will be saved there:
[custompath_generic]\settings.ini
[custompath_generic]\settings_default.ini
[custompath_generic]\the_force_engine_log.txt
[custompath_generic]\the_force_engine_log.txt.1
[custompath_generic]\tfe_input_remapping.bin
[custompath_generic]\Replays\
[custompath_generic]\Saves\
[custompath_generic]\Screenshots\
[custompath_generic]\Temp\
Or - per @darkstar252's request in the comments:
[custompath_darkforces]\settings.ini
[custompath_darkforces]\settings_default.ini
[custompath_darkforces]\the_force_engine_log.txt
[custompath_darkforces]\the_force_engine_log.txt.1
[custompath_darkforces]\tfe_input_remapping.bin
[custompath_darkforces]\Replays\
[custompath_darkforces]\Saves\
[custompath_darkforces]\Screenshots\
[custompath_darkforces]\Temp\
i.e. all dynamic files and folder under just 1 root folder (or sub folder) e.g. custompath_generic=.\data will be a folder called dark under the launcher's own folder.
Thanks for making this launcher portable in #364!
As https://theforceengine.github.io/Documentation.html states:
But that's not actually true, as there is already a way to avoid that by creating an empty
settings.ini- see #571 for the documentation request of this.In any case, what's still missing is a way to define a custom folder or even a subfolder, so as to separate the launcher's static data from the dynamic settings.
TheForceEngine/TFE_FileSystem/paths.cpp checks for
settings.iniviabool isPortableInstall().What I suggest is to support having a setting in that file like
custompath_generic=.\dataand/orcustompath_darkforces=.\data\Dark Forces, which will make sure the following will be saved there:[custompath_generic]\settings.ini[custompath_generic]\settings_default.ini[custompath_generic]\the_force_engine_log.txt[custompath_generic]\the_force_engine_log.txt.1[custompath_generic]\tfe_input_remapping.bin[custompath_generic]\Replays\[custompath_generic]\Saves\[custompath_generic]\Screenshots\[custompath_generic]\Temp\Or - per @darkstar252's request in the comments:
[custompath_darkforces]\settings.ini[custompath_darkforces]\settings_default.ini[custompath_darkforces]\the_force_engine_log.txt[custompath_darkforces]\the_force_engine_log.txt.1[custompath_darkforces]\tfe_input_remapping.bin[custompath_darkforces]\Replays\[custompath_darkforces]\Saves\[custompath_darkforces]\Screenshots\[custompath_darkforces]\Temp\i.e. all dynamic files and folder under just 1 root folder (or sub folder) e.g.
custompath_generic=.\datawill be a folder calleddarkunder the launcher's own folder.