I placed the extracted file file inside C:\Modding\MO2\plugins however the tool didn't appear in the tool drop down It doesn't even appear to register the existence of the plugin
Make sure you're on MO2 version 2.5+ (maybe 2.4 at the oldest) and that you have restarted MO2 after installing. If that doesn't work, then go to tools > settings > diagnostics > log level > debug and then restart MO2 and go to the MO2 Logs Folder and copy the contents of mo_interface.log to pastebin for me to check.
If anyone want to use this plugin on a version lower than 2.50 (I'm using 2.44), you can do so by opening InstallMultipleMods.py with your favorite text editor and replacing the lines 7 8 and 9:
from PyQt6.QtCore import QCoreApplication from PyQt6.QtGui import QIcon from PyQt6.QtWidgets import QFileDialog
with these lines:
try: from PyQt6.QtCore import QCoreApplication from PyQt6.QtGui import QIcon from PyQt6.QtWidgets import QFileDialog except ImportError: from PyQt5.QtCore import QCoreApplication from PyQt5.QtGui import QIcon from PyQt5.QtWidgets import QFileDialog
This way it should work with both 2.50+ and older versions. It worked with 2.44 at least, I haven't tested with other versions, though.
All of my plugins require Mod Organizer version 2.5.0+ (either the latest version from Nexus or the newer ones on Github) as that was when MO2 was updated from Qt5 to Qt6. I'll add this to the description. Sorry for the confusion.
Открой "InstallMultipleMods.ру" через notepade или твой текстовый редактор и измени следующие строки: from PyQt6.QtCore import QCoreApplication from PyQt6.QtGui import QIcon from PyQt6.QtWidgets import QFileDialog
на from PyQt5.QtCore import QCoreApplication from PyQt5.QtGui import QIcon from PyQt5.QtWidgets import QFileDialog
Thank you for this mod, I LOVE it! I'm currently redoing my Skyrim mod list, and this plugin is helping tons! One thing, could you add it as a button right next to the single mod install button, and also add a keyboard shortcut (maybe Alt + M, instead of Ctrl + M)? That would help out tons! Thanks again, keep up the good work!!!
When does the error occur? Usually "RuntimeError: Extraction failed: Data error" happens when there is an issue with the archive or the tool that is decompressing the archive has an issue. My plugin does not handle archive processing and only tells MO2 to install the archive.
This usually happens when downloading halfway through the modlist I'm trying to achieve.
Some extra information that might be the cause for the case: I'm trying to install Fallout Anomaly from Wabbajack, the installation in the end failed and I was using this mod to download the modlist that Wabbajack was able to intsall in the end.
I have another hopeful feature request—I'm not sure if it's possible. Unless it's a FOMOD that requires a selection, could all other mods be installed with their default names without manual confirmation (similar to Vertex)? If a default name matches a previous mod, automatically append a number (1 for the first duplicate, then 2, 3, and so on). Alternatively, option two could be to install everything using the archive name directly.
Go to Tools > Settings > Installers > Simple Installer > and change silent to True This should set it to immediately install the mod with the default name. Sometimes default names are bad though so I made some changes so that it chooses the archive name as the default name for better or for worse. You can download the plugin with my changes here. You can also add common prefixes or suffixes in Tools > Settings > Tool > Install Mod(s) + Naming > NamePrefix, NameSuffix
Wow, it's like magic, you're super amazing!!! (The benefit of naming files by archive name is that I can arrange the mod installation order when naming the archive (sorted by name), so I can just install them in name order directly. Vortex's mod overwrite handling is really too complicated.) (And Vortex takes a long time to process something unknown before installing a bunch of mods.) --------------------- By the way, I have an additional feature suggestion: For mods that require selecting (FOMOD), when I install it for the first time, MO2 could remember my selection and save it somewhere in the MO2 folder, associating it with the mod archive's hash value. This way, when I install the whole mods again, it can be done completely automatically! (There could be an option at the start of the installation to choose whether to go fully automatic or manually select (if it is a fomod case) in case the fomod installation requires a new choice this time.)
Or, perhaps an even more wonderful solution: The selection records from the first time a FOMOD is installed could be stored in a metadata file within the mod archive folder (this way, I not only save the mods but also the selection configuration). This plugin could not only read the mod archive for installation but also read this special metadata file.For example, it could record the selections of each FOMOD in a metadata file.Alternatively, it could save them separately. For instance, the mod file for "bijin npc 1.2.1.rar" could be "bijin npc 1.2.1.select".In this case, the plugin would first read the .select files then read the mod archives before proceeding with the mod installation.
62 comments
big time save from doing the same process over and over
now all i need to do is click a button over and over
from PyQt6.QtCore import QCoreApplication
from PyQt6.QtGui import QIcon
from PyQt6.QtWidgets import QFileDialog
with these lines:
try:
from PyQt6.QtCore import QCoreApplication
from PyQt6.QtGui import QIcon
from PyQt6.QtWidgets import QFileDialog
except ImportError:
from PyQt5.QtCore import QCoreApplication
from PyQt5.QtGui import QIcon
from PyQt5.QtWidgets import QFileDialog
This way it should work with both 2.50+ and older versions. It worked with 2.44 at least, I haven't tested with other versions, though.
Amazing plugin, by the way, thank you!
I have added your changes to version 0.0.6
After installing the mod as you said to in the description, opening MO2 gives me this error before opening:
failed to initialize plugin
C:/Modding/MO2/Plugins/InstallMultipleMods.py: Traceback
(most recent call last):
File "C:/Modding/MO2/Plugins/InstallMultipleMods.py", line
7, in <module>
from PyQt6.QtCore import QCore Application
ModuleNotFoundError: No module named 'PyQt6'
After clicking ok, MO2 works fine, save for the plugin not appearing.
Please advise
so everyone will blessed
u two are really hero, thanks so much
still confused why MO2 be like this, easier like older just drag at tab download and install all without do anything
from PyQt6.QtCore import QCoreApplication
from PyQt6.QtGui import QIcon
from PyQt6.QtWidgets import QFileDialog
на
from PyQt5.QtCore import QCoreApplication
from PyQt5.QtGui import QIcon
from PyQt5.QtWidgets import QFileDialog
Plugin "Install Mod(s)" failed: RuntimeError: Extraction failed: Data error
At:
C:/Modding/MO2/plugins/InstallMultipleMods.py(87):_installQueue
C:/Modding/MO2/plugins/InstallMultipleMods.py(69): display
Usually "RuntimeError: Extraction failed: Data error" happens when there is an issue with the archive or the tool that is decompressing the archive has an issue. My plugin does not handle archive processing and only tells MO2 to install the archive.
Some extra information that might be the cause for the case:
I'm trying to install Fallout Anomaly from Wabbajack, the installation in the end failed and I was using this mod to download the modlist that Wabbajack was able to intsall in the end.
This should set it to immediately install the mod with the default name.
Sometimes default names are bad though so I made some changes so that it chooses the archive name as the default name for better or for worse.
You can download the plugin with my changes here.
You can also add common prefixes or suffixes in Tools > Settings > Tool > Install Mod(s) + Naming > NamePrefix, NameSuffix
(The benefit of naming files by archive name is that I can arrange the mod installation order when naming the archive (sorted by name), so I can just install them in name order directly. Vortex's mod overwrite handling is really too complicated.)
(And Vortex takes a long time to process something unknown before installing a bunch of mods.)
---------------------
By the way, I have an additional feature suggestion: For mods that require selecting (FOMOD), when I install it for the first time, MO2 could remember my selection and save it somewhere in the MO2 folder, associating it with the mod archive's hash value. This way, when I install the whole mods again, it can be done completely automatically! (There could be an option at the start of the installation to choose whether to go fully automatic or manually select (if it is a fomod case) in case the fomod installation requires a new choice this time.)
Or, perhaps an even more wonderful solution: The selection records from the first time a FOMOD is installed could be stored in a metadata file within the mod archive folder (this way, I not only save the mods but also the selection configuration). This plugin could not only read the mod archive for installation but also read this special metadata file.For example, it could record the selections of each FOMOD in a metadata file.Alternatively, it could save them separately. For instance, the mod file for "bijin npc 1.2.1.rar" could be "bijin npc 1.2.1.select".In this case, the plugin would first read the .select files then read the mod archives before proceeding with the mod installation.