So guys if you have any ideas on how to expand this tool here is the place to do it.
NOTE: I am working with Wrye Mash right now, thus this project is on hold, unless I see any interest on it. When I am finished I will return and add bug fixes and GUI support.
==================================================================================================================== Mlox64 module, for use with Modset tool. ====================================================================================================================
Mlox64 Module v1.00 - a module for Modset tool, by: Polemos. fork of mlox v0.61 - the elder scrolls Mod Load Order eXpert, by John Moonsugar.
date: 10-26-2017
Note: Total respect to John Moonsugar, Dragon32 and abot. Mlox is 100% their work. My work on mlox64 was only to adapt mlox to work as a module for Modset tool.
Manual Install: =========== -Extract the contents of the compressed file you have downloaded. -Copy the "mlox64" folder from inside the extracted folder. -Navigate to your Modset tool folder and paste it inside the "addons" folder. -Create a shortcut for the tool and you are done.
Mlox64 is not designed to replace mlox in any way. It is designed to work only as a module for Modset tool. If you have only the regural Morrowind you don't need this tool. Anyway, mlox 64 does the following:
- optimally reorders your load order to avoid known problems, where "optimally" is relative to the quality and coverage of the rule-base. - warns about missing pre-requisites - warns about plugin conflicts - prints notes for things you might want to know about a mod, but may have overlooked in the Readme, or things discussed in forum posts you may have missed.
1) You need Modset tool from Nexus for mlox64 to work. 2) You must have runned Modset tool before you run mlox64. Afterwards you may run mlox64 as many times as needed. 3) You can run mlox64 either inside Mod Organizer or outside it. 4) Mlox64 gets the mod information from Modset tool, you to configure modset.ini accordingly before you run it. (modset.ini is part of Modset tool by the way, you will find it inside modset folder). 5) Be careful where you install mlox64, it has to reside inside the "addons" folder of Modset tool, nowhere else. 6) You need Modset version 2.90 and above to be able to use mlox64 module.
How to enable Mod Organizer to work with OpenMW, guide:
Spoiler:
Show
How to enable Mod Organizer to work with OpenMW.
WARNING: This guide takes into account that you are using Modset.
1. Download "Mod Organizer" from Nexus. Choose Mod Organizer v2_0_8_3b - https://www.nexusmods.com/skyrimspecialedition/mods/6194/? . Extract it where you want it to stay.
2. You'll need files named "Oblivion.exe", "OblivionLauncher.exe" and "Oblivion_default.ini" or "Skyrim.exe", "SkyrimLauncher.exe" and "Skyrim_default.ini" in your OpenMW directory to let MO recognize it as a directory of one of the supported games. These files can be simple empty text documents named exactly like mentioned above.
3. Next, run Mod Organizer. If it doesn't detect OpenMW automatically, browse to your OpenMW folder. It should detect the exes of Oblivion/Skyrim/whatever. You'll notice, that not even Morrowind.esm will be visible in the right window. We'll fix that in the next step.
4. You need to create a symbolic link named "Data" pointing to "Data files" folder. Note: The "Data files" folder is the folder that contain Morrowind's default ESMs, ESPs, BSAs, etc (for example Morrowind.esm or Bloodmoon.bsa etc). The folder name does not matter, but the contents do.
Hit your windows button and search for "cmd". Click on the cmd.exe.
Now type: cmd c/ mklink /J "Your OpenMW directory\Data" "Your OpenMW Directory\Data Files" Hit the enter button.
It doesn't work? Do not worry, here's an alternative: mklink /J "Your OpenMW directory\Data" "Your OpenMW directory\Data Files" You'll notice a link called "Data" in your OpenMW directory, if succeeded.
You may also try this nifty program: http://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html
5. Open up Mod Organizer again. You'll see that all your Esps/esms are listed there.
6. You must never remove those fake binaries and ini of Oblivion/whatever inside of your OpenMW directory. MO needs them to start.
Note: if a mod doesn't get recognized, its title turns grey and italic in the left column of the Mod Organizer Window.
What doesn't work: - No advanced parsing of bsa files from Mod Organizer because of their different structure. - fonts must be installed manually. - if a mod only contains folders named "Splash", "MWSE", "book art", "icons" or "distant land", it won't get recognized as a mod, since MO scans every mod directory for its validity but doesn't recognize these folder names. As a workaround, you need to create an empty dummy folder for example called "meshes" and the mod will get recognized. - Profile managing, a great feature of MO, doesn't work. The saves and inis are at completely different places compared to the ones in Oblivion and Skyrim.
What works: - Mlox does not work, you need Mlox64 instead. - With Modset all mod entries are added to OpenMW.ini (BSAs, ESPs, ESMs) when you run Modset from Mod Organizer. - With Modset TES3mp entries are automatically added as well. - Support for other programs will be added by Modset in the future.
This guide is based on Chenoa's guide at http://forums.bethsoft.com/topic/1471301-mod-organizer-for-morrowind/ .
It seems that MO2 v2.1.5 works out of the box with Morrowind and using the "mklink" command is no longer necessary, it even has a Morrowind themed splash logo when Morrowind is selected. Also, ini editing through MO seems to work as well. Although, it seems that Modset bypasses the /data files folder which I'm guessing would make it still a requirement to link the /data folder.
ModSet tool v2.90 log started. Logging errors and warnings of last operation.
All configuration files and folders found. Proceeding... TES3mp is enabled. Mod organizer is enabled. Warning: Bypassing default Data Files folder... 81 mod file(s) found...
mlox64 immediately closes upon starting it. I've (successfully) run the modset inside MO2, but mlox64 just refuses to work. Furthermore it's not adding any errors to the log, which remains stubbornly three lines long regardless of anything I try (even though the file time updates, so it's being regenerated each time). mlox64 is inside \modset\addons\mlox64 where it belongs, and I have up to date user rules and so on in the mlox64 folder.
Any thoughts or help would be appreciated, I'm nearly at my wit's end with this.
Hi, tool looks great but I'm a bit clueless about finding the path for the symbolic 'Mod_Organizer data_files_folder' to enter into modset.ini In MO2's log I see a line 'Data Path: ....' which points to a folder in appdata - but that folder is empty and doesn't work when I try it. Exploring the virtual folder just shows me the virtualized Morrowind's Data Files path (not OpenMW's). I don't think that I've changed any paths from defaults in Morrowind, OpenMW or MO2, and I can't seem to find any folders titled simply 'data'. Anybody have any ideas?
Please excuse me for my muddled explanations - basically, I'm trying to get your Mlox addon running in order to check my load order. I'm now trying it on your updated Modset - I have followed the instructions to create the symbolic link as I understand them - The link is now pointing to the 'mods' folder where all my actual mod folders are stored (one level up is the folder containing downloads, mods, overwrite, profiles, webcache folders). I am not sure if this is correct? I was under the impression that OpenMW / MO2 somehow merge this 'mods' folder virtually with the Data Files folder in original Morrowind to create the equivalent of an integrated Data Files folder?! Anyway, as it stands, both modset itself and mlox open and run but then close themselves very quickly - nothing seems to change in MO2 , although the Modset log.txt says that it has found x number of mods, but then nothing below. Again, I'm not really sure what is supposed to happen :p Thanks!
ModSet tool v2.92 log started. Logging errors and warnings of last operation.
All configuration files and folders found. Proceeding... Mod organizer is enabled. Warning: Bypassing default Data Files folder... 159 mod file(s) found...
1) Did you take this log with the mlox module? If yes, you may have it installed incorrectly. You need to have it inside the addons directory, e.g: ..modset\addons\mlox64
The files of the module have to be inside mlox64 dir, not in another folder. After that it will be detected and executed automatically (when you run modset).
2) The symbolic link of the "data" folder is needed only if your MO2 does not support Morrowind. At the time of the writing of the guide that was not the case. I will add a note about it.
Other than that, I don't see anything wrong with your ini, and your log (unfortunately) doesn't say much. I haven't visited this page for a long time and I didn't knew that people were using the tool. I will work with it now that I do. Other than that, I don't know how to help you right know, unless you have any more info that I might have missed.
No, that is from the log.txt in the Modset folder. Mlox files are in the folder structure you outline. Thank you for your help anyway, I'll carry on messing around with it and I'll post here if I make any progress.
I would like creating a simpler version. For what exactly are you using it for? OpenMW + Mlox, OpenMW + MO + mlox or some other combination (so I can focus on)?
No worries - must be tremendously difficult to get four separate programs to play nicely together! OpenMW + MO + mlox would be the Holy Grail. Getting mlox to check load order for OpenMW is not a straightforward process as far I can tell, even leaving aside the omwaddon issue.
This tool appears to still not be able to handle uppercase file extensions. Is there any way to fix this issue, short of renaming all my .esp files myself?
Changes: -Added support for omwaddon and omwgame file types. -Fixed extension capitalization problems (esp, esm,...) -Fixed "exit_on_success" setting to work.
I was having trouble trying to get my TES3MP server running with mods through MO2, so I just downloaded MLOX, tweaked the .ini to my own file structure, and it worked like a charm!
This is probably really dumb but I don't know about any "utilities" in OpenMW. Where do I get that from? is that just the place where my OpenMW launcher and exe is?
I'm trying to use it without MO, and now this keeps happening.
ModSet tool v2.50 log started. Logging errors and warnings of last operation.
All configuration files and folders found. Proceeding... TES3mp is enabled. 35 mod file(s) found... 39 mod entry/entries found in "Openmw.cfg"...
Error: 39 declared in "Openmw.cfg" but only 35 mod files found. Please check your mod folders for missing mod files.
Program End.
I really appreciate what you've done by making this tool, but I can't help but find it incredibly frustrating and it gives little help when something goes wrong.
EDIT: OK! FOUND THE PROBLEM!
Seems like this tool is case sensitive, so it can't read capitalised file extensions. It also doesn't know what omwaddon files are.
This updates the load order. It works for OpenMW. For some reason TES3MP is resetting the load order whenever it's launched however.
I think the problem is that this tool isn't editing the OpenMW cfg properly.
60 comments
NOTE: I am working with Wrye Mash right now, thus this project is on hold, unless I see any interest on it. When I am finished I will return and add bug fixes and GUI support.
Mlox64 module, for use with Modset tool.
====================================================================================================================
Mlox64 Module v1.00 - a module for Modset tool, by: Polemos.
fork of mlox v0.61 - the elder scrolls Mod Load Order eXpert, by John Moonsugar.
date: 10-26-2017
Note: Total respect to John Moonsugar, Dragon32 and abot.
Mlox is 100% their work. My work on mlox64 was only to adapt mlox to work as a module for Modset tool.
====================================================================================================================
Installation:
====================================================================================================================
Manual Install:
===========
-Extract the contents of the compressed file you have downloaded.
-Copy the "mlox64" folder from inside the extracted folder.
-Navigate to your Modset tool folder and paste it inside the "addons" folder.
-Create a shortcut for the tool and you are done.
Uninstallation:
-Just delete the mlox64 folder.
====================================================================================================================
Introduction:
====================================================================================================================
Mlox64 is not designed to replace mlox in any way. It is designed to work only as a module for Modset tool. If you have only
the regural Morrowind you don't need this tool. Anyway, mlox 64 does the following:
- optimally reorders your load order to avoid known problems, where "optimally" is relative to the quality and coverage of
the rule-base.
- warns about missing pre-requisites
- warns about plugin conflicts
- prints notes for things you might want to know about a mod, but may have overlooked in the Readme, or things discussed in
forum posts you may have missed.
(Taken from the original mlox readme).
====================================================================================================================
Notes:
====================================================================================================================
1) You need Modset tool from Nexus for mlox64 to work.
2) You must have runned Modset tool before you run mlox64. Afterwards you may run mlox64 as many times as needed.
3) You can run mlox64 either inside Mod Organizer or outside it.
4) Mlox64 gets the mod information from Modset tool, you to configure modset.ini accordingly before you run it.
(modset.ini is part of Modset tool by the way, you will find it inside modset folder).
5) Be careful where you install mlox64, it has to reside inside the "addons" folder of Modset tool, nowhere else.
6) You need Modset version 2.90 and above to be able to use mlox64 module.
====================================================================================================================
Bugs:
====================================================================================================================
-I don't know of any... yet. If you find any please type them in the bugs section in Nexus.
====================================================================================================================
Links:
====================================================================================================================
Original mlox:
https://www.nexusmods.com/morrowind/mods/43001/?
Modset tool:
https://www.nexusmods.com/morrowind/mods/45232?
====================================================================================================================
Version History:
====================================================================================================================
v1.00 Initial release.
Check included license files for software permissions etc..
====================================================================================================================
====================================================================================================================
WARNING: This guide takes into account that you are using Modset.
1. Download "Mod Organizer" from Nexus. Choose Mod Organizer v2_0_8_3b - https://www.nexusmods.com/skyrimspecialedition/mods/6194/? . Extract it where you want it to stay.
2. You'll need files named "Oblivion.exe", "OblivionLauncher.exe" and "Oblivion_default.ini" or "Skyrim.exe", "SkyrimLauncher.exe" and "Skyrim_default.ini" in your OpenMW directory to let MO recognize it as a directory of one of the supported games. These files can be simple empty text documents named exactly like mentioned above.
3. Next, run Mod Organizer. If it doesn't detect OpenMW automatically, browse to your OpenMW folder. It should detect the exes of Oblivion/Skyrim/whatever.
You'll notice, that not even Morrowind.esm will be visible in the right window. We'll fix that in the next step.
4. You need to create a symbolic link named "Data" pointing to "Data files" folder.
Note: The "Data files" folder is the folder that contain Morrowind's default ESMs, ESPs, BSAs, etc (for example Morrowind.esm or Bloodmoon.bsa etc). The folder name does not matter, but the contents do.
Hit your windows button and search for "cmd". Click on the cmd.exe.
Now type:
cmd c/ mklink /J "Your OpenMW directory\Data" "Your OpenMW Directory\Data Files"
Hit the enter button.
It doesn't work? Do not worry, here's an alternative:
mklink /J "Your OpenMW directory\Data" "Your OpenMW directory\Data Files"
You'll notice a link called "Data" in your OpenMW directory, if succeeded.
You may also try this nifty program: http://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html
5. Open up Mod Organizer again. You'll see that all your Esps/esms are listed there.
6. You must never remove those fake binaries and ini of Oblivion/whatever inside of your OpenMW directory. MO needs them to start.
Note: if a mod doesn't get recognized, its title turns grey and italic in the left column of the Mod Organizer Window.
What doesn't work:
- No advanced parsing of bsa files from Mod Organizer because of their different structure.
- fonts must be installed manually.
- if a mod only contains folders named "Splash", "MWSE", "book art", "icons" or "distant land", it won't get recognized as a mod, since MO scans every mod directory for its validity but doesn't recognize these folder names. As a workaround, you need to create an empty dummy folder for example called "meshes" and the mod will get recognized.
- Profile managing, a great feature of MO, doesn't work. The saves and inis are at completely different places compared to the ones in Oblivion and Skyrim.
What works:
- Mlox does not work, you need Mlox64 instead.
- With Modset all mod entries are added to OpenMW.ini (BSAs, ESPs, ESMs) when you run Modset from Mod Organizer.
- With Modset TES3mp entries are automatically added as well.
- Support for other programs will be added by Modset in the future.
This guide is based on Chenoa's guide at http://forums.bethsoft.com/topic/1471301-mod-organizer-for-morrowind/ .
ModSet tool v2.90 log started.
Logging errors and warnings of last operation.
All configuration files and folders found. Proceeding...
TES3mp is enabled.
Mod organizer is enabled.
Warning: Bypassing default Data Files folder...
81 mod file(s) found...
Any thoughts or help would be appreciated, I'm nearly at my wit's end with this.
data files = C:\MegaMorrowingMO\Morrowind\Data Files\
Mod_Organizer data_files_folder = C:\MegaMorrowingMO\Morrowind\Data Files\
I've set these folders as the same. I've also tried the path to the instance location in AppData/Local/ModOrganizer/. No luck, I'm stuck.
Error: "Openmw.cfg" path not declared or incorrect in "modset.ini".
Error: Mod Organizer profile folder path missing or incorrect in "modset.ini".
but yet my paths seem correct:
[Settings]
exit_on_success = True
[OpenMW settings]
openmw.cfg = C:\Users\Jérémy\Documents\My Games\OpenMW
data files = G:\GAMES\Bethesda Softworks\Morrowind\Data Files
[TES3mp settings]
TES3mp_enabled = True
insert Russian crc32 = True
pluginlist.json = G:\GAMES\Bethesda Softworks\Morrowind\tes3mp.Win64.prerelease.0.7-alpha\server\data
[Mod Organizer settings]
Mod_Organizer enabled = True
Mod_Organizer data_files_folder = G:\GAMES\Bethesda Softworks\Morrowind\Data Files
Mod_Organizer root_folder = G:\GAMES\Bethesda Softworks\Mod Organizer 2
Mod_Organizer profile_folder = C:\Users\Jérémy\AppData\Local\ModOrganizer\Darkorius\profiles\Graphic Overhaul MrMoonshine
[Mod Organizer fixes]
Mod_Organizer autolock_mods = True
Mod_Organizer workaround_fix = False
What I'm doing wrong here ? Can you help me please ?
In MO2's log I see a line 'Data Path: ....' which points to a folder in appdata - but that folder is empty and doesn't work when I try it. Exploring the virtual folder just shows me the virtualized Morrowind's Data Files path (not OpenMW's). I don't think that I've changed any paths from defaults in Morrowind, OpenMW or MO2, and I can't seem to find any folders titled simply 'data'. Anybody have any ideas?
I'm now trying it on your updated Modset - I have followed the instructions to create the symbolic link as I understand them - The link is now pointing to the 'mods' folder where all my actual mod folders are stored (one level up is the folder containing downloads, mods, overwrite, profiles, webcache folders). I am not sure if this is correct? I was under the impression that OpenMW / MO2 somehow merge this 'mods' folder virtually with the Data Files folder in original Morrowind to create the equivalent of an integrated Data Files folder?!
Anyway, as it stands, both modset itself and mlox open and run but then close themselves very quickly - nothing seems to change in MO2 , although the Modset log.txt says that it has found x number of mods, but then nothing below.
Again, I'm not really sure what is supposed to happen :p
Thanks!
ModSet tool v2.92 log started.
Logging errors and warnings of last operation.
All configuration files and folders found. Proceeding...
Mod organizer is enabled.
Warning: Bypassing default Data Files folder...
159 mod file(s) found...
Ini:
[Settings]
exit_on_success = False
[OpenMW settings]
openmw.cfg = C:\Users\Paul\Documents\My Games\OpenMW
data files = C:\games\Morrowind\data files
[TES3mp settings]
TES3mp_enabled = False
insert Russian crc32 = True
pluginlist.json = C:\Games\tes3mp\mp-stuff\data
[Mod Organizer settings]
Mod_Organizer enabled = true
Mod_Organizer data_files_folder = C:\Games\OpenMW 0.45.0\Data
Mod_Organizer root_folder = C:\Games\MO2\
Mod_Organizer profile_folder = C:\Games\Morrowind Mods\profiles\Default
[Mod Organizer fixes]
Mod_Organizer autolock_mods = True
Mod_Organizer workaround_fix = False
You need to have it inside the addons directory, e.g:
..modset\addons\mlox64
The files of the module have to be inside mlox64 dir, not in another folder. After that it will be detected and executed automatically (when you run modset).
2) The symbolic link of the "data" folder is needed only if your MO2 does not support Morrowind. At the time of the writing of the guide that was not the case. I will add a note about it.
Other than that, I don't see anything wrong with your ini, and your log (unfortunately) doesn't say much. I haven't visited this page for a long time and I didn't knew that people were using the tool. I will work with it now that I do. Other than that, I don't know how to help you right know, unless you have any more info that I might have missed.
Thank you for your help anyway, I'll carry on messing around with it and I'll post here if I make any progress.
I would like creating a simpler version. For what exactly are you using it for?
OpenMW + Mlox, OpenMW + MO + mlox or some other combination (so I can focus on)?
The bug you have, seem to plague other users too.
OpenMW + MO + mlox would be the Holy Grail. Getting mlox to check load order for OpenMW is not a straightforward process as far I can tell, even leaving aside the omwaddon issue.
Changes:
-Added support for omwaddon and omwgame file types.
-Fixed extension capitalization problems (esp, esm,...)
-Fixed "exit_on_success" setting to work.
Lightly tested though... not enough time.
ModSet tool v2.50 log started.
Logging errors and warnings of last operation.
All configuration files and folders found. Proceeding...
TES3mp is enabled.
35 mod file(s) found...
39 mod entry/entries found in "Openmw.cfg"...
Error: 39 declared in "Openmw.cfg" but only 35 mod files found.
Please check your mod folders for missing mod files.
Program End.
I really appreciate what you've done by making this tool, but I can't help but find it incredibly frustrating and it gives little help when something goes wrong.
EDIT: OK! FOUND THE PROBLEM!
Seems like this tool is case sensitive, so it can't read capitalised file extensions. It also doesn't know what omwaddon files are.
This updates the load order. It works for OpenMW. For some reason TES3MP is resetting the load order whenever it's launched however.
I think the problem is that this tool isn't editing the OpenMW cfg properly.
You are right about your observations and in turn I appreciate your comments.
I am focused on the wrye mash development for OpenMW (which includes support for omwaddon and stuff) and I haven't updated modset for a long time.
The truth is that there were very few bug reports when I was working on it and not much interest...
If you are still interested I can fix the problems, add support for omwaddon files and make a new release.