Reply to Re: Martridge - The DMOD Wizard
If you don't have an account, just leave the password field blank.
Apologies for double-posting but I thought it might be good for sake of completeness to list all known standard paths before I forget, as they don't appear to be catalogued anywhere.
* Dink 1.08 and earlier on 95-XP, installed in Program Files, will only load mods from subdirs as per its registry key or dinksmallwood.ini maybe.
* Dink 1.08 on Vista and later, path in Program Files (x86) (assuming x64), DFarc2 will install to VirtualStore instead due to lack of permissions and engine exe launch from there without its knowledge. Will not load from DFarc3's alternate install path or anywhere else.
* Freedink on Windows, has its own installer but is most commonly dropped into the 1.08 install path. Will load anything (including main data with --refdir) from anywhere with the right paths specified.
* Yedink on Windows, as above except different exe name.
* Freedink on GNU/Linux after a proper install will be available from $PATH as "freedink".
* Yedink on GNU/Linux, assuming someone's building from source and then installing should be the same except with a different name.
* RTDink on Windows, old releases would install to Program Files (x86), and will continue to install automatic updates there (not sure of this). Initial releases did not support -g and only loaded from "dmods" subdir through included launcher.
* RTDink on Windows more recently, installs to AppData/Local, will load from anywhere with -g. Custom main data path cannot be specified, and --refdir determines what shows in the inbuilt launcher list. Might need registry to determine where it's at.
dmods:
* Old DFarcs: <=1.08 install path subdirs only plus VirtualStore on Vista and up.
* DFarc3, $HOME/dmods subdirs on GNU/Linux, and optionally on Windows too with "alternate install path". Probably does VirtualStore otherwise.
* RTDink: subdirs of installpath/dmods/
* Freedink/Yeoldedink will place save files in $HOME/dmods if the path can't be written to, such as in program files, or the main data in /usr/share/games/wherever installed by the package manager.
Everything outside of this may be considered user-specified unless there's something I forgot.
* Dink 1.08 and earlier on 95-XP, installed in Program Files, will only load mods from subdirs as per its registry key or dinksmallwood.ini maybe.
* Dink 1.08 on Vista and later, path in Program Files (x86) (assuming x64), DFarc2 will install to VirtualStore instead due to lack of permissions and engine exe launch from there without its knowledge. Will not load from DFarc3's alternate install path or anywhere else.
* Freedink on Windows, has its own installer but is most commonly dropped into the 1.08 install path. Will load anything (including main data with --refdir) from anywhere with the right paths specified.
* Yedink on Windows, as above except different exe name.
* Freedink on GNU/Linux after a proper install will be available from $PATH as "freedink".
* Yedink on GNU/Linux, assuming someone's building from source and then installing should be the same except with a different name.
* RTDink on Windows, old releases would install to Program Files (x86), and will continue to install automatic updates there (not sure of this). Initial releases did not support -g and only loaded from "dmods" subdir through included launcher.
* RTDink on Windows more recently, installs to AppData/Local, will load from anywhere with -g. Custom main data path cannot be specified, and --refdir determines what shows in the inbuilt launcher list. Might need registry to determine where it's at.
dmods:
* Old DFarcs: <=1.08 install path subdirs only plus VirtualStore on Vista and up.
* DFarc3, $HOME/dmods subdirs on GNU/Linux, and optionally on Windows too with "alternate install path". Probably does VirtualStore otherwise.
* RTDink: subdirs of installpath/dmods/
* Freedink/Yeoldedink will place save files in $HOME/dmods if the path can't be written to, such as in program files, or the main data in /usr/share/games/wherever installed by the package manager.
Everything outside of this may be considered user-specified unless there's something I forgot.
