Script conflicts

[Wolfmod]

Is there any way, a utility of some sort, that would allow players to find script conflicts? I use FO4Edit but that doesn't tell me if a texture has a bad pixel count or if a script is badly written. All too often helpful individuals will say, "What you need to do is to uninstall all your mods and then one at a time..." and I want to take my Fatman missile launcher and shoot them. Apart from the fact that testing will destroy my settlements and my game, this advice ignores the fact that many not so stable mods will behave well when alone and don't cause problems until other mods are installed. You may install mod 1 with no problems then mod 2, mod 3, mod 4 and mod 5 and suddenly have a problem. You would then deduce that mod 5 is the culprit but if you continue mod 6, 7 and 8 may also have problems because mod 1 had a faulty script. Alone it did no harm.

 

Right now, the biggest issue with modding is the lack of troubleshooting tools. At least half the player base is running around the Commonwealth with random CTDs, blocked menu items, and other faults and instabilities. I have spent more time trying to fix my game than playing it. Can we please start a discussion on which utilities do what and whether they are still regarded as current.

[Reneer]

Is there any way, a utility of some sort, that would allow players to find script conflicts?

Short answer: No.

 

Longer answer: There are simply too many variables at play to have any hope of a "script conflict detector" being at all useful. Plus someone would have to define and operationalize just what constitutes a "script conflict" in the first place. Stating "well, a script must be bad / faulty" isn't helpful in figuring out how or even if a mod is at fault.

[Guest deleted34304850]

.

Edited July 22, 2019 by 1ae0bfb8