1
Wish list / Override folder
« on: December 23, 2006, 03:45:53 pm »
This has been smoldering for a while, and the revival of the Custom soundtracks thread prompted me to actually post this.
What I have in mind is a folder (called "override", in the main PS folder) which contains the complete PS folder structure (except override itself, of course), but empty. The VFS system would check for any file that is needed in this override folder's substructure before looking at the built-in files in the standard location. This is like an advanced version of the override folder used in for example NWN (where it was mostly used for updates, which is bad).
With the override folder / substructure, you would put the modified version of a file in the same place as the original, just in the override substructure, and leave it there. In case of zip files, you would create a zip file containing only the file(s) you changed, nothing else, and put that in the appropriate place, naming it like the original zip file.
Example:
original location of archive:
/PS/art/characters.zip
modified files from archive:
dermm.cal3d
appropriate override .zip file:
/PS/override/art/characters.zip
contents:
dermm.cal3d
The reason is two-fold.
First, it eases modding. Right now you need to change the contents of the zip files, and possibly keep a backup of the original contents elsewhere.
Second, it removes the need to write-protect things for the updater to not override them, with the additional benefit that one always gets a fully updated client while retaining the modded parts, without the need of file-shuffling. Also, currently one has to reassemble any modified zip files each time there is an update to that file.
This isn't an important thing, not even necessary, but something to maybe look at in the future when things are more mature and stable.
What I have in mind is a folder (called "override", in the main PS folder) which contains the complete PS folder structure (except override itself, of course), but empty. The VFS system would check for any file that is needed in this override folder's substructure before looking at the built-in files in the standard location. This is like an advanced version of the override folder used in for example NWN (where it was mostly used for updates, which is bad).
With the override folder / substructure, you would put the modified version of a file in the same place as the original, just in the override substructure, and leave it there. In case of zip files, you would create a zip file containing only the file(s) you changed, nothing else, and put that in the appropriate place, naming it like the original zip file.
Example:
original location of archive:
/PS/art/characters.zip
modified files from archive:
dermm.cal3d
appropriate override .zip file:
/PS/override/art/characters.zip
contents:
dermm.cal3d
The reason is two-fold.
First, it eases modding. Right now you need to change the contents of the zip files, and possibly keep a backup of the original contents elsewhere.
Second, it removes the need to write-protect things for the updater to not override them, with the additional benefit that one always gets a fully updated client while retaining the modded parts, without the need of file-shuffling. Also, currently one has to reassemble any modified zip files each time there is an update to that file.
This isn't an important thing, not even necessary, but something to maybe look at in the future when things are more mature and stable.