Single Status Update
Nice to see you active on the Wrye Bash threads ... Utomno beats me up when I ask questions over there ... Do you think I could use you to put a bug in his ear about adding the ability to read fomods for the next version. Converting to wizards is not something I'm any good with, and is the only reason WB isn't the only manager I use. LOL
I don't defend people's actions, sometimes people are more abrasive then they need to be. However, so am I. I tend to get impatient when people ask the same question that's already asked or when something is already covered in documentation. Another thing that annoys me is when people ask for an update to a request. So if Utumno is reacting to those, he may be doing so in a way that's common for most people.
The fomod support might be added at some point. However, until that happens, and it shows up, then know it may show up at some point. Besides, I have never ever, ever, found documentation on that anyway. I can't write in Python so I can't do that anyway. However, lets pretend I could and I found a Python module for parsing xml data. I wouldn't know what to look for and once I made support thinking I covered it all, then someone would come along with a new function I didn't see in any of the mod files I downloaded from the Nexus so the support would be incomplete.
The other problem I see with this is Gopher usually uses complex C scripts also. So to say that Wrye is fomod compatible would be inaccurate. It would be better to say, if it has the simple xml installer file, then it supports that. Anything else would not be supported.
All that has to be considered. So that's why I say, may, might, and best not to ask about it. It's on the GitHub site as a request so just leave it be.
Now I have told people in the past to use the functionality already built into Wrye Bash. Make sure you have Beta1 it works better.
Optional: Go to the mopy folder and use the default_ini file to make a bash.ini file. Remove the semicolon from the line sSkippedBashInstallersDirs to skip the NMM folders like cache and other things Wrye Doesn't use. I have NMM pointing to my Bash Installers folder so I can use NMM to download the files.
Feature: Open Wrye and chose the monitor external installer option. It will do a refresh so be prepared to wait. I even recommended a full refresh (even though it will do some kind of refresh again) if you haven't done it in a while. One it's done refreshing, then it will tell you to install your mod. You leave the dialogue box open and run NMM and install the mod choosing the options you want. Then you leave NMM open and return to Wrye where it's waiting for you to finish. Tell Wrye you are done and it will scan for changes. Then it makes a folder in your Bash Installers folder of all the files from that external installation. Valid files and locations though so you can't do this with EXE files and stuff.
After you have the installer folder, go back to NMM and uninstall the mod. Then go to Wrye Bash and install it. Now Wrye is tracking the files so it knows how to override them with other mods. Also if you did the Clean Data procedure those files are tracked now and left alone which cleans out your data folder of unneeded files.
Thanks for the reply, I didn't notice the notification icon until now ... sorry.
This should help me quite a bit. I wish I had seen the icon before I posted my "WB wish list" thread, but no harm done. I really am looking forward to trying the remote installer monitoring. I have less than 20 mods in NMM, all the rest were either simple mods, bain compatible, or choose from a,b,c,d fomods so it's really only a handful that are the issue. It's a shame that the most important ones also contain binary files. I don't suppose there's a secret feature that fixes that as well ;-)
Anyway, thank you for taking the time, I learned a lot, and will be giving the feature a test drive in short order ... hopefully I'll end up with only 2 or 3 files with binaries left in NMM.