Dumb question - the package/core/override folder structure

[t87]

I think it's a pretty straightforward question (though I had a bit of a hard time searching for it in the forums)

 

Does the folder structure of the files in the packages/core/override folder matter at all? What happens when there's a duplicate? I imagine that as more and more mods come out, we're going to be running into more and more of the "compatibility" issues that are already surfacing with mods that modify chargen xml and ones that modify dialogue.

 

It seems like folder structure doesn't matter at all, so I can name folders and put mods in them as needed? (Like.. "Head Morphs" to contain a bunch of random .mor files for the companions)

 

Thanks!

 

(I am not asking about the source priority rules that are going to further complicate when we start to see more files in the modules/override folders, just about the packages/core/overrides)

[Bridgepiece]

Not sure if the file structure matters, any completed mod is wrapped up into a DAZIP anyways.. As for the naming convention, there is a 'tutorial' on the wiki that runs down Bioware's naming system..

[TGBlank]

Folder structure can be as deep as you want, as far as i know (i've personally tested up to 5 folders deep). Otherwise, the folder names tell the game in which order to load (the game loads them alphabetically).

 

So if you have a.mor in folder A, and a.mor in folder Z, the one you'll see ingame is the one from folder Z.

 

Additionally, the dazips are loaded first, and then the override folder. So if something in the override conflicts with something in a dazip, the override is the one that shows up.