[NoOne]

re-installing won't necessarily work either, so don't do that. you can specifiy a new game root, but not the data path during installation. that can only be done after installation completes.

use teh expert tab as people noted. type in new path for where you want the data folder kept.

you will have to manually delete the old data folder. Some things need to be left there... "Fonts" and "Skins" folder should remain where they are.

i leave all the loose files in the root Data directory because they are tiny in size and didn't want to go through the necessary trial and error for a few bytes of data. they aren't on my 2nd hdd, so they likely all need to remain too.

pro tip: each time you install a new patch, you need to re-do this. if you want to avoid the double installation of all that data, after the game installs BUT BEFORE you click "load ootp" at end of setup, go to the main OOTP directory. change Custom_Folders.ini -- when you open it, it will be obvious... data path=x:\blah\blah

don't change the app path.

by doing this, the first time you load the game it will install the data to the path you want, immediately. you won't have to wiat for it to install this data twice nor clean up after it.

i actualyl keep a 2nd copy of this custom_folders.ini in a safe place outside of ootp directory... whne i reach that point in the installation as explained above, i simply copy this file to the main ootp directory and save over teh freshly ruined one from installation.

otherwise it will install to default data directory, then you need to re-do the process and it re-installs the data directory to the spot you want, and you have to delete the old data directory again... quite the p.i.t.a.

i've asked for at least three years that they stop re-installing a default ini file... those are personalized settings that get revereted to default each time... makes no sense and only frustrates the end-user. especially when you know how frickin easy it is to avoid it entirely. when a data directory is moved it's common sense to clean up the old one too... any directory with non-matching files can be left unadultered if needed. perfectly safe... and avoids needless duplication and waste that most users will never notice if they do this.

not adhering teh the DRY principle! it's not jsut about the code. it applies well to most things.