Best Answer Tannin , 26 January 2015 - 04:46 PM
The sResourceArchiveList is turned into short-names and mapped back to regular file names for every application run through MO.
If an application sees something different than the game this may have two reasons:
a) it uses a different list of archives (i.e. hard-coded) in which case the application is inheritantly unreliable in this regard anyway.
b) the application reads the archive list in a different way than the game. I.e. an application could open the ini file as a txt file and parse it manually. There is no way MO could then "fix" the list. Again one could argue that if the application reads the archive list in a different way than the game it's the applications fault if it gets different results.
A little known fact: ini files can be placed in the registry and the regular windows ini-reads (which skyrim uses) would transparently fetch the values from registry instead of the ini files. Doing this for skyrim might even make sense to improve startup time. Of course tools that don't use windows ini-reads would not get the registry values.
This, combined with the fact that ini files are not a standardized file format and therefore every method of reading them might produce different results (i.e. because of different syntax for comments, different character encoding support, ... ) means that all tools that use different means of reading ini files than the game should also, technically at least, be considered unreliable. Go to the full post