http://www.shsforums...-unused-in-bg2/
{btw, Hurricane, excellent work! Glad to see another 'modder-of-mods' showing his mad skilz in such great fashion. When are you gonna officially register an account?}
...and it got me thinking: maybe there's room for more optimization.
Since its early days, I wondered why folders BGT\Base and the BGT\Modify existed, because if you read the DevDoc, it repeatedly states that the files in those folders are modified (created?) by setup-BGT.TP2. Are the files touched a second time by TP2, or the code to touch them the first time is in there but not used afterwards?
I'm not criticizing this. I can understand that it's easier to have the modified files at-hand, ready-to-use, than processing them again in each player's install. Plus back in the good-ole-days, pc processor power was a bottleneck. I also can imagine that it prevented the headache of user-error reports, if they were missing some important files in their base install, then BGT had those files ready.
Now having read Hurricane's thread, perhaps it's time to reconsider: having all the file modifications done by TP2-patching—pull the original files direct from the BG1 install, modify on-the-run from the TP2 code.
This way, coders can see/confirm the modifications done to the files, update them in-future if we discover better changes, and add new code for extra features. Both BGT\Base and the BGT\Modify (and other redundant folders) could be deleted, saving a nice bit of chump-change in storage (every less megabyte helps when downloading…).
We could probably do some optimizing of PreSetup.bat and EndSetup.bat too.
Thoughts?
Edited by Azazello, 04 January 2012 - 11:41 PM.