TAF mod version control tries to separate mod installation from mod version control.
The installation side of things would ideally deal with engine related factors: eg getting the right combination of dlls for the user's platform, installing community patch etc
The mod version control side of things would ideally only modify game data files typically rev31.gp3.
In current practice, the delineation is muddied because different mods like to package their own dlls and totala.exe hacks.
As a mod version maintainer, I would like to be able to add a new version by just uploading new game files to version control, no dlls or executables.
As an an engine installation maintainer I want to be able to set one community patch to be installed regardless of mod or mod version finally being targeted.
TAF mod version control tries to separate mod installation from mod version control.
The installation side of things would ideally deal with engine related factors: eg getting the right combination of dlls for the user's platform, installing community patch etc
The mod version control side of things would ideally only modify game data files typically rev31.gp3.
In current practice, the delineation is muddied because different mods like to package their own dlls and totala.exe hacks.
As a mod version maintainer, I would like to be able to add a new version by just uploading new game files to version control, no dlls or executables.
As an an engine installation maintainer I want to be able to set one community patch to be installed regardless of mod or mod version finally being targeted.