(09-18-2014, 07:52 PM)TheGreatCthulhu Wrote: Hm... The idea is good, but IMO, while this would work well for somewhat more advanced users, it could turn out to be somewhat messy for those who are not too tech-savvy. (By users I mean those who download and play mods, not mod developers.)
Blah, they'll have to cope with it! Should be equivalent of unzipping a file..
(09-18-2014, 07:52 PM)TheGreatCthulhu Wrote: Right. Or in case of a full conversion, it could specify what exactly to launch.
Now, there should be some sort of convention on where to store these config files and how to handle the replacements, otherwise, if there are several mods using this feature, they could (partially or completely) overwrite each others files, and could generally make a mess. What if one mode replaces a certain file, but another mod wants to use the original one?
Very good point.. There would have to be some sort of log file which stores information on the currently 'active' (default namned shader) - or, less complicated;
Mod A has it's shaders namned as 'Defaultname.glsl'
There is a file named 'Defaultname_original.glsl' (The original shaders - which would be overwritten by Mod A)
Mod B isn't allowed to replace shaders if the folder contains 'Defaultname_original.glsl'
A full backup of shaders could probably be stored in a separate folder.