Post by cymbalchick2 on Jun 26, 2020 19:04:43 GMT -5
My question is this:
How do I figure out how to find which mods are conflicting?
For example, when you download a mod and it says "mod will conflict with abc.xml and xyz.xml," and "will conflict with mods that use 1234.xml," how do I figure out if my mods have these so I can remove conflicting mods? Ever since I installed EL, some of my mods have been conflicting with voting, showing bills, and even opening Evergreen Harbor. Is there a simple way to figure this out? The 50/50 method seems to mess up my game. And, if there is a way to figure out how to do this tuning or whatever it is, is there a way that I can fix it for my own personal use? Can this also be used to find broken/outdated cc whether it be CAS or furniture, and can that be fixed as well?
Post by MizoreYukii on Jun 27, 2020 10:46:17 GMT -5
The issue sounds like you're using outdated mods rather than random conflicting mods, especially because nothing happened before the patch. There is a list of updated/broken mods here, please go through it and clean out your mods. Unfortunately, there is no way to quickly check if a mod conflicts or not. You just have to remember what mods you download, do the 50/50 (either the normal way, or with an override folder), or open each file and check. Or even go back to the download pages and note what the creator says. There used to be a conflict detector but it hasn't worked in years, and random mods that don't conflict are flagged all the time. Like an outfit override for Father Winter was flagged as conflicting with a pancakes recipe. Completely unreliable, lol. Anyhow, if you do encounter mods that are actually altering the same files for different reasons, please follow this tutorial.
Post by MizoreYukii on Jun 27, 2020 13:10:34 GMT -5
You place them into the overrides folder, head in-game and test whatever the mods are supposed to alter. If the mod alters the phone for example, test the phone and look for whatever was changed in the mod and if it appears. If it doesn't work as intended, it's a conflict.
I just remembered Scumbumbo made his own conflict detector and tested it, it does work still (the other one for sure doesn't). Use this one for detecting package conflicts! It won't fix or detect actual broken mods though from patches, those you need to find and remove yourself.
If you are having problems seeing the CAPTCHA, please clear your browser's cache and cookies and ensure that you do not have any browser addons or extensions that interfere with the display of the CAPTCHA. Then, close the CAPTCHA window and click on the register button to open the CAPTCHA again.