Myrddin

I've tested a little bit and discoverd a problem with the "hidden flag" in the settings.json. If an existing entry in one of the ini files has the hidden flag in settings.json this entry generates a message that the entry is in the wrong ini file. If the hidden flag for this entry is removed the error message disappears.

Hi Tannin, thanks for your answer. Most of the warnings i got apply to settings which skyrim itself has written to the ini files. I can't believe that all of these settings should be wrong. Most other settings i took from the S.T.E.P. Wiki. As stated by you above i contacted you via private message (mainly because my native language is german).

I didn't change the ini's before doing the upgrade so the checking seems to be messed up with this version. I reverted back to MO 1.2.17 just to be save.

After upgrading to MOD Organizer 1.2.18 i recognized that when the Ini Configurator is started there are a lot of entries in the MOD Organizer log section regarding ini entries which stated that they are in the wrong ini file. IMO they are right in place where they are . mo_interface.txt Is this a new bug introduced with MO 1.2.18? rgds Myrddin

You can download and copy the hook.dll which Tannin provided via the issue tracker to your MOD Organizer directory. Then MOD Organizer 1.2.16 will work with jar-files (Java executables) again. https://issue.tannin.eu/tbg/modorganizer/issues/950