Detecting Mod Organizer

[markdf]

Is there any way for an application to detect whether it's being run in Mod Organizer? I'm developing a tool that would strongly benefit from being able to detect whether it's accessing the virtual file system or not.

[Greg]

You might ask @Tannin, the developer of Mod Organizer on github.

https://github.com/TanninOne/modorganizer/issues

[Kesta]

Add recognition of a parameter like -modorganizer in your code, and tell your users to add it in the application's arguments when they add it through MO.

 

This is very little work for your users (most of them will most likely be used to this with stuffs like DynDOLOD), and very little for you as well.

 

 

Other than that, you could try to force your app out of MO's vfs, and then compare the content of the actual Data folder with the vfs. But this could prove extremely hard to do, especially considering the first option.

 

Last alternative : Put your actual code in a .dll, and build two apps dependent of it : A regular one, and one as MO's plugin, though I'm not sure how convenient it is to create an actual plugin for MO.

Edited July 5, 2016 by Kesta

[markdf]

After messing around in the console, it looks like vfs files show up with no owner field. I think maybe it would be enough to check the Data directory for the presence of files with no owner. Does that sound reasonable?

 

FNIS auto detects whether it's being run from MO, I wonder what it does? Maybe it checks its own file permissions.

[Tannin]

Just check if hook.dll (or usvfs_x64.dll for MO2) is loaded using the getmodulehandle api.