Updates here! FYI I added a table of settings for reference on the description page. Please check it out to customize FP to your liking!
v1.15.0 Rebuilt against MO2 dev branch to support dev builds. No noticeable change for regular MO2
v1.14.0 - Your choices are now automatically pre-selected, including choices you manually de-selected in previous installs. You can toggle this behavior off in the plugin settings. - Improved behavior for mods on Nexus with multiple FOMODs. I added a new heuristic-based mod-name-matcher type thing to find the 'most accurate' mod to match. Basically, if you have a mod and its optional both with FOMODs, it will no longer do the thing where reinstalling the main file will name it something else / not find the previous choices! Pretty big win overall, since now you're less likely to install 2 versions of the same FOMOD file on accident. - Fixed behavior when hitting 'Enter', now goes to the next step / installs as expected. v1.13.0 - [feature] Properly bundle translations into the archive. NOTE: THIS CHANGES HOW YOU INSTALL THE MOD. NOW YOU SHOULD EXTRACT AT THE MO2 ROOT DIRECTORY, LIKE BETHESDA PLUGIN MANAGER (sorry for caps) - [feature] Add optional notification panel to see useful logs in the window. (show_notifications) - [feature] Uncheck previously unchecked choices when restoring options (basically, if you uncheck a default setting, this will happen again when you restore previous choices) - [feature] Dashed border for mods that were unchecked in previous installs - [feature] Setting to always restore previous choices without having to hit the button (always_restore_choices) - [feature]Make image/description resizable and persist their sizes. Also persist sizes of left/right panes. - [change] Removed 'hide images' button and left it as a top-level plugin setting only (show_images) - [bugfix] Fix edge case trying to restore choices that are now disabled (https://github.com/aglowinthefield/mo2-fomod-plus/issues/34) - [bugfix] Fix empty image spawning a big empty image viewer if you click it - [bugfix] Fix crash with Water for ENB German edition (and maybe other mods, idk. Forgot to remove a debugging line)
Here's an example of the 'previously unchecked' border in action, as well as the WIP notifications area (disabled by default).
v1.12.0 - Support for color selection. See the possible choices in the MO2 settings for FOMOD Plus. Based on the gruvbox color scheme. I wanted to keep things easier than writing one's own QSS. Check the description for a preview of the colors! - Fix an issue where an empty flag was not being matched to an unset flag. COTN Dawnstar FOMOD and a few others have had this come up for specific cases. - Fix URL regex once more. Wrote lots of test cases so all those links better work now!
Next up: Still debugging issues with Linux and certain FOMODs sending a few people a 'bad allocation' message. I haven't been able to replicate yet, though I've come close. Also, next release will have proper translation files and the installation method will change. I'll leave notes in the release when this happens~
removing old entries to save space. I'll start using the changelog as well starting at 1.5.0, so check there for history. If you really want <1.3.0 changes, let me know.
Afraid not, there's really no mod that can feasibly do this, and if they promise it it's probably more dangerous than useful.
Since this has been asked a few times, I can give the general reason why:
Take a simple FOMOD like Base Object Swapper. At the end of the day, it installs "the same DLL" no matter which option you pick. (it's not the same DLL, but for the purposes of retroactive inspection, it basically is). BaseObjectSwapper.DLL. The trick is, in the FOMOD package there are 3 DLLs supplied that might be structured like
Based on your choice of game version in the FOMOD, it targets one of those sources to be popped into the destination (the mod root). So looking backwards, there's no way we can deduce which one you chose with 100% accuracy. We _could_ re-evaluate the conditions and decide you _probably_ went with whatever was auto-selected (and that would probably work in this simple case!) but this is the simplest case I can think of where even something with one output file can't be 100% accurately mapped to a user choice.
It gets even trickier with things like meshes and textures, as you can imagine. There's no way for us to know the 'source' of the file in your mod directory retroactively, and I would rather not inject possibly inaccurate guesses into the process.
Is it because you want Bethesda Plugin Manager? I posted a working 2.5.2 DLL in the comments of that mod. I can mirror it here.
If anyone else is staying on 2.5.0 because of Bethesda Plugin Manager, replace it's DLL with this one and you can upgrade to 2.5.2: https://www.mediafire.com/file/mi811ntoaswxb1f/bsplugins.dll/file
NOTE: Building against MO2 dev libraries is causing an issue with gameVersion checks. Please verify any options for your Skyrim game version as the auto-selection is currently broken. Working on a fix.
Hello. thanks so much for this mod. when you say it now needs to be installed in the mo2 root directory are you saying it now is not installed in the plugins folder and is installed in whatever your main mo2 folder is (the same spot where the main modorganizer.exe is in?) ??
Let me tell you my favorite thing about this mod is the Previous Choices and the ability to click links in the description, I promise you this is by far the best thing I used in a long time... Much Appreciated bro and thank you for your efforts.
the error in the last sticky makes installing FSMP impossible, because it chooses the wrong game version, which the installer would get right by itself - and which is not changeable by hand.
left side with fomod plus, wrong version, right side without fomod plus, correct version
edit: latest version chooses 'Not yet', which is as bad as a random one
Yep, I have to manually extract the version I want.you confirm our suspicion that ppl using this plugin aren't on their first rodeo and know what to do (disable plugin or fish correct version out of zip file! so we won't change the installer (we'd get tons of noobs who don't know their skyrim version, again), hoping for a fix here.
Now if only I could find the mod that had the option between Immersive Citizens and Ai Overhaul, I can't remember which mod it was :'( Edit: It was NPC AI Process Position Fix NG lol
Hi! I love this mod, but I would like to point out a problem I have been facing with your FOMOD Scanner.
The problem I have encountered is that if you install a mod with a FOMOD and then install an optional file or update file that doesn't have a FOMOD and merge it with the main plugin will result in the FOMOD Scanner removing the FOMOD Tag from the plugin in question. I would recommend that you for example make a system where if a mod has been tagged by the scanner, then that tag will persist even if the FOMOD is "gone" and maybe add a purge option on the FOMOD scanner that will completely clear all FOMOD tags and then scan the mod list again.
Aside from that small problem, I find this tool to be an invaluable asset for any modder!
Yeah this should be the default behavior. I actually wrote the scanner the way it is now because I was accidentally adding FOMOD data where it shouldn't be, back in the early versions. Once I get this MO2 versioning stuff sorted out I'll include that change.
Not worth much but throwing my hat in and requesting MO2 2.4.x support. Any newer versions after the one I'm using have messed up windows magnifier/DPI/scaling problems, making it a real strain on the eyes with my particular display, bad enough that I couldn't tolerate it and quickly reverted back 2.4.5.
Hey so just a heads-up for anyone who uses FOMOD Plus with the newest MO2 dev builds: It seems like this plugin doesn't get along with a few FOMODs for some reason and MO2 instantly crashes upon running some FOMODs. I currently am on the latest 2.5.3 - Dev Build 7 version of MO2.
Funny enough, some FOMODs work perfectly fine, I even can use the FOMOD Plus features in these cases. But if I take for example a mod from PowerOfThree (his mods mostly have the same FOMOD structure) The program crashes instantly. MO2 doesn't write a crash dump and FOMOD Plus' log doesn't show much either.
Here's my latest FOMOD Plus log when trying to install Dialogue History from PO3:
464 comments
v1.15.0
Rebuilt against MO2 dev branch to support dev builds. No noticeable change for regular MO2
v1.14.0
- Your choices are now automatically pre-selected, including choices you manually de-selected in previous installs. You can toggle this behavior off in the plugin settings.
- Improved behavior for mods on Nexus with multiple FOMODs. I added a new heuristic-based mod-name-matcher type thing to find the 'most accurate' mod to match. Basically, if you have a mod and its optional both with FOMODs, it will no longer do the thing where reinstalling the main file will name it something else / not find the previous choices! Pretty big win overall, since now you're less likely to install 2 versions of the same FOMOD file on accident.
- Fixed behavior when hitting 'Enter', now goes to the next step / installs as expected.
v1.13.0
- [feature] Properly bundle translations into the archive. NOTE: THIS CHANGES HOW YOU INSTALL THE MOD. NOW YOU SHOULD EXTRACT AT THE MO2 ROOT DIRECTORY, LIKE BETHESDA PLUGIN MANAGER (sorry for caps)
- [feature] Add optional notification panel to see useful logs in the window. (show_notifications)
- [feature] Uncheck previously unchecked choices when restoring options (basically, if you uncheck a default setting, this will happen again when you restore previous choices)
- [feature] Dashed border for mods that were unchecked in previous installs
- [feature] Setting to always restore previous choices without having to hit the button (always_restore_choices)
- [feature]Make image/description resizable and persist their sizes. Also persist sizes of left/right panes.
- [change] Removed 'hide images' button and left it as a top-level plugin setting only (show_images)
- [bugfix] Fix edge case trying to restore choices that are now disabled (https://github.com/aglowinthefield/mo2-fomod-plus/issues/34)
- [bugfix] Fix empty image spawning a big empty image viewer if you click it
- [bugfix] Fix crash with Water for ENB German edition (and maybe other mods, idk. Forgot to remove a debugging line)
Here's an example of the 'previously unchecked' border in action, as well as the WIP notifications area (disabled by default).
v1.12.0
- Support for color selection. See the possible choices in the MO2 settings for FOMOD Plus. Based on the gruvbox color scheme. I wanted to keep things easier than writing one's own QSS. Check the description for a preview of the colors!
- Fix an issue where an empty flag was not being matched to an unset flag. COTN Dawnstar FOMOD and a few others have had this come up for specific cases.
- Fix URL regex once more. Wrote lots of test cases so all those links better work now!
Next up: Still debugging issues with Linux and certain FOMODs sending a few people a 'bad allocation' message. I haven't been able to replicate yet, though I've come close. Also, next release will have proper translation files and the installation method will change. I'll leave notes in the release when this happens~
removing old entries to save space. I'll start using the changelog as well starting at 1.5.0, so check there for history. If you really want <1.3.0 changes, let me know.
Since this has been asked a few times, I can give the general reason why:
Take a simple FOMOD like Base Object Swapper. At the end of the day, it installs "the same DLL" no matter which option you pick. (it's not the same DLL, but for the purposes of retroactive inspection, it basically is). BaseObjectSwapper.DLL. The trick is, in the FOMOD package there are 3 DLLs supplied that might be structured like
SkyrimSE/BaseObjectSwapper.dll
SkyrimAE640/BaseObjectSwapper.dll
SkyrimAE1170/BaseObjectSwapper.dll
Based on your choice of game version in the FOMOD, it targets one of those sources to be popped into the destination (the mod root). So looking backwards, there's no way we can deduce which one you chose with 100% accuracy. We _could_ re-evaluate the conditions and decide you _probably_ went with whatever was auto-selected (and that would probably work in this simple case!) but this is the simplest case I can think of where even something with one output file can't be 100% accurately mapped to a user choice.
It gets even trickier with things like meshes and textures, as you can imagine. There's no way for us to know the 'source' of the file in your mod directory retroactively, and I would rather not inject possibly inaccurate guesses into the process.
Hope this clears it up!
I can not use MO2 2.5.2, I use MO2 2.5.0 for some reason.
Could you please make this mod support for MO2 2.5.0?
Thanks a lot!
If anyone else is staying on 2.5.0 because of Bethesda Plugin Manager, replace it's DLL with this one and you can upgrade to 2.5.2: https://www.mediafire.com/file/mi811ntoaswxb1f/bsplugins.dll/file
Much Appreciated bro and thank you for your efforts.
left side with fomod plus, wrong version, right side without fomod plus, correct version
edit: latest version chooses 'Not yet', which is as bad as a random one
Yep, I have to manually extract the version I want.you confirm our suspicion that ppl using this plugin aren't on their first rodeo and know what to do (disable plugin or fish correct version out of zip file!so we won't change the installer (we'd get tons of noobs who don't know their skyrim version, again), hoping for a fix here.
Edit: It was NPC AI Process Position Fix NG lol
edit: Nevermind, just realised I was still running 2.5.0
The problem I have encountered is that if you install a mod with a FOMOD and then install an optional file or update file that doesn't have a FOMOD and merge it with the main plugin will result in the FOMOD Scanner removing the FOMOD Tag from the plugin in question. I would recommend that you for example make a system where if a mod has been tagged by the scanner, then that tag will persist even if the FOMOD is "gone" and maybe add a purge option on the FOMOD scanner that will completely clear all FOMOD tags and then scan the mod list again.
Aside from that small problem, I find this tool to be an invaluable asset for any modder!
Funny enough, some FOMODs work perfectly fine, I even can use the FOMOD Plus features in these cases. But if I take for example a mod from PowerOfThree (his mods mostly have the same FOMOD structure) The program crashes instantly. MO2 doesn't write a crash dump and FOMOD Plus' log doesn't show much either.
Here's my latest FOMOD Plus log when trying to install Dialogue History from PO3:
[INFO] [INSTALLER] FomodPlusInstaller::install - modName: Dialogue History, version: 2.1.2.0, nexusID: 114238[INFO] [INSTALLER] FomodPlusInstaller::install - tree size: 1
[DEBUG] [INSTALLER] FomodPlusInstaller::getExistingFomodJson - modName: Dialogue History nexusId: 114238