Need some help fixing another mod's bug with a homemade patchwork mod

[Servietsky]

Hey guys

 

So I've been using the UFO4P, but ran into a pretty cumbersome bug : some items will cause a CTD when being inspected. Thus far it's only been armor items. If those are legendaries, they CTD when being picked up (auto-inspect). Disabling the UFO4P fixes the bug, but apparently it's a no-no.

 

I don't expect it's going to be fixed soon and I'd rather not start over my save, so I want to stop armor legendaries from auto-inspecting by making a mod for it.

 

I need serious help because I've never modded anything in my life, and my coding knowledge is very basic.

 

Here's what I've found out with my own digging :

- Legendary items have a "FeaturedItem" keyword which tags the item for auto-inspect on first pickup. I found this in the DefaultObject's (whatever that is) description "Keyword to indicate a reference is a featured item, triggering the inspect menu the first time the player activates it".

- The FeaturedItem keyword is used by a bunch of things, including several "mod_Legendary_" object mods which are themselves used by a "LegendaryItemQuest" quest which I assume is a fake quest simply used to create legendaries. The object mods have a property with the operation "ADD" and value "FeaturedItem".

 

So that seems pretty straightforward to me. Delete the FeaturedItem keyword so that no item will ever auto-inspect (not a good solution imo), or go through each mod_Legendary_Armor object mod and remove the property that adds FeaturedItem to the object (the better solution).

 

But I'm a noob so there's a very high chance I'm wrong and about to break some things without knowing it, if it even works.

 

That's about it. I'm looking for confirmation that this is the right way to do it or guidance on how to properly do it. Thank you for taking the time to help !

[bill8872]

I never had that happen with UFO4P, so I doubt it is that. What I suspect is you have another mod affecting Legendary's, and one of the two are affecting the same keywords.

Open all your mods with FO4Edit, and check UFO4P to see where the conflict is.

[Servietsky]

See, none of my mods affect legendaries, armor, weapons, or anything related to gameplay.

 

Here's my load order :

Fallout4.esm
DLCRobot.esm
DLCworkshop01.esm
DLCCoast.esm
DLCworkshop02.esm
DLCworkshop03.esm
DLCNukaWorld.esm
Unofficial Fallout 4 Patch.esp
SaveManager.esp
Companion Fall Damage Immunity.esp
console.esp

And here are the mods not listed in there (idk why NMM doesn't display them in the load order) :

 

Full Dialogue Interface

No more cash register sound

Emogene Takes a Lover Fix

Two other UFO4P users have had and reported the problem in the last two weeks, both of which use none of my other mods (according to their posts, of course).

So I agree, it's very weird that we're only three people having this problem, and it's been 6 months since the last release : plenty of time for the bug to be reported more than 3 times.

BUT ... disabling the UFO4P fixes the bug. Enabling only the UFO4P with no other mod does not fix the bug.

And most importantly, I've got no solution other than starting over a fresh save with UFO4P disabled, which I'd like to avoid.

So anyway ... the only idea I've got is making a patchwork fix. It's ugly and I don't like it, but I still like it better than losing 50 hours of gameplay.

Edit : I'll still try the FO4Edit thing of course, if it can provide a better solution.

Edited May 26, 2018 by Servietsky

[bill8872]

yes very weird so few are having this happen. They will only fix this if they can duplicate the issue on there end.

Wish I could help with this one, as it has never happened to me.

[Servietsky]

So not sure if that's what I should've done but checking for conflict losers with the UFO4P shows this https://i.imgur.com/IiDWRZe.png so I guess it's not in conflict with any other of my mods.

[bill8872]

The DLC's do not count as far as the red goes. UFO4P is the reason for that. If nothing is conflicting with UFO4P, then try validating the game files through Steam. It might be possable a game file is missing, or croupted.