Your newest version is completely broken due to a syntax error in the plugins\pluginfinder\plugin\pluginfinder\modules\pluginfinder_install.py file. With this issue none of the installation buttons will work and you won't be able to install any plugins. The solution to this is to replace line 69: self._installFromFile(str(tempName), pluginId) with self.installFromFile(str(tempName), pluginId) (basically just remove that underscore).
If anyone is having issues with the latest version, you can fix it by doing that yourself until the author fixes it.
Replaced it, seems like it was the result of some unfinished cleanup after testing! If you come across anything else, feel free to drop a message in discord and I'll usually see it pretty quickly!
No, but you can get the download url from the directory to make a meta file; https://github.com/Kezyma/ModOrganizer-Plugins/blob/main/directory/plugin_directory.json
Better to download from nexus and get the meta from there though, if you're doing WJ lists, makes it less likely for updates to break the list.
Hi @Kezyma MO2 does not respond when I click on pluginfinder. I've been waiting for a long time but nothing is opening. The mod organizer just freezes. I have to terminate it and start over.
hi Kezy just wondering why doesn't your plugin finder detect plugins installed through mo2 folder? for example I downloaded your root builder here in nexus and not through this mod so it doesn't detect that I installed it already.
While technically possible, it's tricky to do as I'd need a way to determine the exact files that are meant to be in each plugin before they're installed, and on top of that, I'd have to write a horrible regex of some kind to try and work out what version is installed, which is no easy feat.
Maybe one day I'll do something like that (and anyone's welcome to do those things and add them to the repo), but it's mostly just because it'd take me a lot of time that I don't really have.
I am getting an error upon loading MO2 after updating Plugin Finder by using Plugin Finder:
Install Plugin Finder as per the documentation (copying the 'pluginfinder' folder into '...\MO2\Plugins' folder)
Load MO2 and run Plugin Finder. (There's a delay as it presumably does first time run installation/download of repository)
I then get the list of plugins displayed within the finder as shown in linked image: https://postimg.cc/z3LP1NBD
I then click on the "Install/Update" button to update from v1.2.3.0a to v1.2.4.0a of Plugin Finder.
Update completes, but... Plugin Finder no longer initialises upon load of MO2, and returns the following message in MO2:
--------------------------- Error --------------------------- failed to initialize plugin E:/MODS/MO2/plugins/pluginfinder: Traceback (most recent call last): File "E:/MODS/MO2/plugins\pluginfinder\__init__.py", line 5, in <module> from .pluginfinder.plugins.pluginfinder_browser import PluginFinderBrowser ModuleNotFoundError: No module named 'pluginfinder.pluginfinder.plugins.pluginfinder_browser'
--------------------------- OK ---------------------------
I keep getting prompted to update from v1.2.3.0a to v1.2.4.0a in Plugin Finder after a clean install of the latest releases from Nexus v1.2.4 or Github v1.2.4.
Ahh, that's annoying, I believe I know why though. Easy fix: Go to MO\plugins\data\PluginFinder\ Open InstalledPlugins.json Right near the top it'll say something like "pluginfinder": { "Version": "1.2.3a" Change 1.2.3a to 1.2.4a and save the file
Give Feedback
44 comments
For support and/or help, please check the dedicated Discord server for my mods and/or the Documentation website.
plugins\pluginfinder\plugin\pluginfinder\modules\pluginfinder_install.pyfile. With this issue none of the installation buttons will work and you won't be able to install any plugins. The solution to this is to replace line 69:self._installFromFile(str(tempName), pluginId)withself.installFromFile(str(tempName), pluginId)(basically just remove that underscore).If anyone is having issues with the latest version, you can fix it by doing that yourself until the author fixes it.
If you come across anything else, feel free to drop a message in discord and I'll usually see it pretty quickly!
Thanks man.
Btw, I still had to edit it manually after installing latest upload of v2.0.0 of this plugin to Nexus at 02 Dec 2023, 7.24PM.
Maybe the fixed version hasn't been posted to Nexus yet?
Better to download from nexus and get the meta from there though, if you're doing WJ lists, makes it less likely for updates to break the list.
https://imgur.com/a/h0wa4WP
With MO 2.5.0 I get following error message if I want to start 'Plugin Finder' (version 1.2.6)
Had to delete everything and reinstall it, it's working again.MO2 does not respond when I click on pluginfinder. I've been waiting for a long time but nothing is opening. The mod organizer just freezes. I have to terminate it and start over.
Maybe one day I'll do something like that (and anyone's welcome to do those things and add them to the repo), but it's mostly just because it'd take me a lot of time that I don't really have.
You are B R I L L I A N T .
Thanks for your work.
Great mod - thanks for sharing. :)
I am getting an error upon loading MO2 after updating Plugin Finder by using Plugin Finder:
---------------------------
Error
---------------------------
failed to initialize plugin E:/MODS/MO2/plugins/pluginfinder: Traceback (most recent call last):
File "E:/MODS/MO2/plugins\pluginfinder\__init__.py", line 5, in <module>
from .pluginfinder.plugins.pluginfinder_browser import PluginFinderBrowser
ModuleNotFoundError: No module named 'pluginfinder.pluginfinder.plugins.pluginfinder_browser'
---------------------------
OK
---------------------------
Please can you help?
B
I keep getting prompted to update from v1.2.3.0a to v1.2.4.0a in Plugin Finder after a clean install of the latest releases from Nexus v1.2.4 or Github v1.2.4.
Is there another version I can manually install?
Go to MO\plugins\data\PluginFinder\
Open InstalledPlugins.json
Right near the top it'll say something like "pluginfinder": { "Version": "1.2.3a"
Change 1.2.3a to 1.2.4a and save the file