MCM Mod Name Glitch

[Bluegunk]

For some reason my MCM suddenly decided to call Nether's Follower Framework:    $FF_ModName .  

I checked the various String files, and this is how the mod is described in the Strings.  All the languages are the same structure. It should show up as NFF or Nether's Follower Framework, or similar.

 

I tried reloading the mod. No effect. This is also on a brand new start - no prior saves.

 

Could anyone please suggest what else might be holding this corrupted name?  I can't see NFF in SKSE plugins, etc.

 

Thanks.

 

Edited September 22, 2024 by Bluegunk

[traison]

The mod name is passed as a script property named ModName. In the case of NFF version 2.8.3b this is set to a static string: "Follower Framework". There is no $FF_ModName in the translation files. Maybe you have a different version.

 

 [05] nwsFollowerFramework.esp (037E31C6) \ Quest \ 05034A76 <nwsFollowerMCM>

 

Filter for: by Value "modnam"

Check: siblings

[Bluegunk]

Hello again!

 

 

I'm using NFF 2.8.6b, April 2024.  I'm on a fresh new start, all the old saves wiped away and this broken MCM entry keeps popping up. I tried starting without NFF, and adding it later. Still get the corrupt entry. I've re-installed it a couple of times, too.

 

The NFF Translations English file has this to say:

; MCM ------------------

$FF_ModName    NFF

$FF_Title    Nether's Follower Framework
$FF_Version    Follower Framework Version

$FF_Page1    Activity
$FF_Page2    Gameplay

 

In the ESP:

 

 

[Bluegunk]

Actually, perhaps I ought to be asking this on Nether's Discord?

 

And have done so. So, perhaps put things on hold a moment, please, Traison.  If I get a reply, I'll come back.

Edited September 22, 2024 by Bluegunk

[traison]

...and the translations file is not getting overridden by anything? You're actually viewing the one that is served up by the usvfs to the game?

[Bluegunk]

You nailed it.

 

On Discord we found Dialogue Tags, for whatever reason, has a copy of the Nether Follower Framework English string file. In it, the MCM info is incorrect.

Never would have thought they had a copy of that string file.

 

Thanks for your help, Traison! I'll mention it to the Dioalogue Tabs author.

[traison]

In situations like these, where sanity checks don't add up, open related files from the Data tab in MO2 and check the Conflicts tab of the problematic mod. The answer is almost always there.

 

For Vortex users I'd advice them to ignore Vortex in these situations, and instead open up a Windows Explorer window to inspect the Skyrim Data directory. The files you see there are the files the game will use, whatever Vortex is telling you is irrelevant. This is in some sense the exact opposite to what to do on MO2 funnily enough.

[Bluegunk]

Thanks. I do use the Data tab in MO2. For some reason I didn't think of it this time around. D'Uh.  Maybe I'm getting too ancient for all this.   👴