Great Stuff, it's nice for my heavily modded playthrough to have more of a guide for what I've done and haven't done, glad to see more Inis available for it.
The fix did not work but I think I know why after some testing.
The short answer: Create a data folder and then have your ini folder inside of this. So data\ini\ProgressTracker\. In addition, put a Fonts folder inside of that data folder as well. You can leave the Fonts folder empty it doesn't actually need anything but read the long version if you want to put something in there. Zip up this data folder and upload it to Nexus Mods and it should now install properly in MO2.
The long answer: From my testing, it appears that MO2 is putting the ini files right into the data folder. Not into any subfolder, just the root data folder. I think the reason it is doing this is because MO2 looks for what it considers valid data files/folders and the only ones in this mod are the ini files. So it assumes that that must be the data folder and it just dumps them right into the root data folder instead of the correct subfolder.
I was able to get it to install correctly by including a blank test.esp file since it recognizes that as valid data. Problem is that I thought a blank esp file would be confusing to an end user. "Why do I have this blank esp file?".
So instead I created a Fonts folder and MO2 recognizes it as valid data even when empty. Of course, an empty Fonts folder could also be confusing to the end user. "Why do I have this empty Fonts folder?". You could put a txt file in the Fonts folder explaining why you had to do it to alleviate any confusion.
Not the most elegant solution but not sure how else to do it, and in such a way, that doesn't cause too much confusion to the users.
yeeeeey thanks, i love that mod but yeah, theres a lot of mods that would be good to have tracked of
Edit: Excuse me, could you please add support to the "Collection of Cleanded" version of "Hackdirt The Deep Ones"? Is an optimized version of the mod n_n
13 comments
The short answer:
Create a data folder and then have your ini folder inside of this.
So data\ini\ProgressTracker\.
In addition, put a Fonts folder inside of that data folder as well.
You can leave the Fonts folder empty it doesn't actually need anything but read the long version if you want to put something in there.
Zip up this data folder and upload it to Nexus Mods and it should now install properly in MO2.
The long answer:
From my testing, it appears that MO2 is putting the ini files right into the data folder. Not into any subfolder, just the root data folder.
I think the reason it is doing this is because MO2 looks for what it considers valid data files/folders and the only ones in this mod are the ini files.
So it assumes that that must be the data folder and it just dumps them right into the root data folder instead of the correct subfolder.
I was able to get it to install correctly by including a blank test.esp file since it recognizes that as valid data.
Problem is that I thought a blank esp file would be confusing to an end user. "Why do I have this blank esp file?".
So instead I created a Fonts folder and MO2 recognizes it as valid data even when empty.
Of course, an empty Fonts folder could also be confusing to the end user. "Why do I have this empty Fonts folder?".
You could put a txt file in the Fonts folder explaining why you had to do it to alleviate any confusion.
Not the most elegant solution but not sure how else to do it, and in such a way, that doesn't cause too much confusion to the users.
Edit:
Excuse me, could you please add support to the "Collection of Cleanded" version of "Hackdirt The Deep Ones"? Is an optimized version of the mod n_n
Sorry, and thank you OwO