Constructing & Using Mod Group Feature in xEDIT

[tjax323]

I seem to have this up and running for SSE using MO 2. Took me a bit until I realized I needed to make it a "mod" in the data folder for MO (or just in the data folder for NMM). I thought it was supposed to be in the xEdit folder reading the STEP instructions, but I think that might have been more on me than the instructions. I just got confused reading "In the xEdit installation folder...".

 

Anyway, to ensure I'm doing this right, is it okay to type multiple groups in just the one ".modgroup" file using notepad++ or must I have  separate ".modgroup" file for each group I want to have as an option? I've attached screen print if this makes it easier to understand the question I'm trying to ask.

 

My intention is to conflict resolve my load order in more manageable sections (i.e. STEP's sequential installation sections), and once I have it conflict resolved, I intend to create a group for each section in that MO profile so that it is not as daunting as I start the next section's conflict resolution. Thus, I want to ensure I set this up correctly and I'm hoping I can add more groups in one file instead of having to add a separate file for each group I want to create. Any and all advice is appreciated. I just hope I'm on the right path so I don't have to start over.

 

Thanks much---- tjax

 

Note: I did read the 12/9 post here. I just didn't want to piggy back on to a "solved" thread.

Edited December 28, 2016 by tjax323

[tjax323]

Grant, you got it, bud.

 

I was under the impression to install this feature, one had to add this user-created file (see links in original post) "xEdit.modgroups", and place it in the data file, which was wrong. That's what one should do with "other modgroup files" if, for example, you want to to put some co-file patches in. Read that as modgroup files #2, 3, 4..... The first one belongs in the xEdit folder in order for the feature to work. Simply put one must have the first & necessary modgroup file in the xEdit folder with the xEdit exe file to "trigger" the feature. My snafu was creating it the data folder, where I understand it's okay to have additional modgroup copies for additional mod groups. I initially created xEdit.modgroups in the xEdit folder to get the name right, but copied (not cut) the file into data, which I erroneously thought it should be in. It worked, because I had the same file in both xEdit and data during testing. So when I "cleaned up", I kept the file in data while deleting the one in xEdit (backwards) . It wouldn't work, of course, and it took me a while before I figured out I'd done it backwards.

 

I'm going to mark this answered with this response, so that if anyone reads this later on, it might save such a person an hour's worth of frustration I experienced. If so, it was worth keeping up.

 

In case anyone is wondering about my initial question regarding whether one could have multiple groups in just one modgroup file, yes. I figured that out just by doing it and seeing what would happen after I recovered from my stupid mistake. It did work & is currently working (xEdit ver 3.2).

Edited December 29, 2016 by tjax323

[tjax323]

Argh!!! I don't know how I do this to myself. Please ignore the part about putting it directly in the data file. I confused initial setup with co-files., which might be useful if I decide to archive any of my own patches.

 

Note to Moderator: I might come back to ask some questions, but this is essentially an NVM post as I answered my own questions with testing. Please feel free to delete my post. I fear someone else could come across this causing that person unnecessary confusion. If you'd prefer to keep the post up, I will be happy to write down what I realized and did in case it may help. Just say the word, or use your eraser.

Edited December 28, 2016 by tjax323

[GrantSP]

We always prefer to have posts remain up so if you could outline what your small snafu was that would be helpful.

 

PS. We all make stupid mistakes from time to time, don't worry about it, it's part of the learning process.