One of my go to mods with a permanent place in my load order. Thank you.
Also, is it possible to get the MLOX maintainers to remove the patch recommendations for your mod? That way people don't break their game based on well-meaning advice form a helper program.
Thank you for this great addition to my new favourite game! I can't beviele I installed MGSO3, updated mlox, mwse and MGE xe, then installed further 20 mods and the game works with no hickups. It's freeking old and I expected problems, none found.
ATTENTION! I could use some help. Until I put this together I had never tried my hand at creating mlox rules. I tested what is in the readme pretty thorougly, but if anyone has any feedback to offer I would appreciate it.
You don't actually need a Require rule when you have a Patch rule.
With a Patch rule if you have the two mods being patched but not the patch, then mlox will show the message. If you have the patch but not all the mods being patched, then mlox will show the message.
When I add these into mlox_base.txt I'll put a link to here on Nexus in. Not really needed if someone's downloaded and adding rules to their ow mlox_user.txt
And thanks for taking the time to write up these rules, they'll be in the next update.
Edit: Had a proper look. Expanded the LaFemme and Adamantium Armour entries to include mods which merge in those plugins or alter them in some way.
For "TLM + Expanded Sounds.esp" (setting aside "TLM - Complete.esp") you have "TLM - Light Sources (Clearer Lighting).esp" as a requirement for the patch but you also have an Order rule for "TLM - Light Sources (Lanterns).esp" Does someone need to be running either "TLM - Light Sources (Clearer Lighting).esp" or "TLM - Light Sources (Lanterns).esp" (or both) to need the patch?
Thanks for the info. As for TLM, it is either "TLM - Complete.esp" or "TLM - Light Sources (Clearer Lighting.esp)" that is required. Depends on whether they are using the complete or modular version. Technically, you don't NEED "TLM - Light Sources (Lanterns).esp" (I have no idea how this would effect TLM, but it makes no difference to my patch) even if using the modular version, but if it is in the load order it should come before the patch, which is why I created the rule that way.
Update: also, I created separate Order rules intentionally, not wanting to force mlox to order each of the required plugins (leaving that to the rules created for the individual mods). This seemed to be how other patch rules were designed. Since these are merge patches, they don't care what order the other plugins are in, so long as these load after.
I used to create Order rules in fairly big, monolithic blocks. However, with the way mlox works (chunks up your load order, with the edges of those chunks being defined by Order rules, and then moves the chunks around so all Order rules are met) this led to problems with a mod wanting to be loaded both before and after another mod. Long story short, the way you've grouped them is the best way to do it to avoid future problems.
That's how I understood it also. I've updated the readme (on the Nexus, not the one in the archive yet) to remove the Requires rules since you said they aren't needed. If I understand, everything else is correct? Sorry for the noob questions. My modding experience is primarily with the Fallout series.
Everything else looks cool. Very few people actually go to the trouble of writing mlox rules, even simple Order ones. So, I wouldn't say you're being n00bish here at all
Give Feedback
9 comments
Also, is it possible to get the MLOX maintainers to remove the patch recommendations for your mod? That way people don't break their game based on well-meaning advice form a helper program.
Cheers!
You don't actually need a Require rule when you have a Patch rule.
With a Patch rule if you have the two mods being patched but not the patch, then mlox will show the message.
If you have the patch but not all the mods being patched, then mlox will show the message.
When I add these into mlox_base.txt I'll put a link to here on Nexus in. Not really needed if someone's downloaded and adding rules to their ow mlox_user.txt
And thanks for taking the time to write up these rules, they'll be in the next update.
Edit:
Had a proper look. Expanded the LaFemme and Adamantium Armour entries to include mods which merge in those plugins or alter them in some way.
For "TLM + Expanded Sounds.esp" (setting aside "TLM - Complete.esp") you have "TLM - Light Sources (Clearer Lighting).esp" as a requirement for the patch but you also have an Order rule for "TLM - Light Sources (Lanterns).esp"
Does someone need to be running either "TLM - Light Sources (Clearer Lighting).esp" or "TLM - Light Sources (Lanterns).esp" (or both) to need the patch?
Update: also, I created separate Order rules intentionally, not wanting to force mlox to order each of the required plugins (leaving that to the rules created for the individual mods). This seemed to be how other patch rules were designed. Since these are merge patches, they don't care what order the other plugins are in, so long as these load after.
I used to create Order rules in fairly big, monolithic blocks. However, with the way mlox works (chunks up your load order, with the edges of those chunks being defined by Order rules, and then moves the chunks around so all Order rules are met) this led to problems with a mod wanting to be loaded both before and after another mod. Long story short, the way you've grouped them is the best way to do it to avoid future problems.