Jake/Stranger does not appear & Sim Settlements 2 build options do not appear in build mod after chapter 2 release

[VoidProtogen]

Hey guys, new to the forum here but I am experiencing a bug in my new game that is causing Jake/The Stranger to not show up in Sanctuary, I'm not sure if this is because I built my first recruiting beacon at Red Rocket instead of Sanctuary but after weeks of sleeping or wandering the wastes he still will not show up to begin the Sim Settlements quest line. Additionally when I am in build mode the Sim Settlements category does not exist. I have searched the forums and done the usual google search to see how I can fix these issues and have picked up the magazine on the Sanctuary work bench,that did nothing,I made sure all my Sim Settlements 2 and associated mods are up to date and have removed all older versions prior to starting my new game as my old one continued to tell me that the workshop framework had been replaced and crashed me every time I went to Sanctuary so I'm at a loss for what to do in order to fix these issues. All of the mods I have downloaded as well as their load orders have remained the same since before Chapter 2 came out and Jake appeared as he should and I had access to the Sim Settlements 2 build menu so this seems to be stemming from the Chapter 2 download

 

[Synystyr1]

This sounds likely to be a mod conflict or load order issue. If you will please post your load order, someone might be able to help you identify the issue.

 

[yaugie]

The usual first steps are

• check you have everything up to date: Workshop Framework, Simsettlements 2, and Chapter 2
• make sure everything's in the correct order as listed on the Wiki here (note that "Unofficial Patch" is not required, that's just where it has to be in the order if you do have it)
• look for other mods that might be interfering with/altering the settlement system in general
• make certain the Recruitment Beacon is actually powered on (you'll have the signal in your own Pipboy's Radio if so)

 

[msalaba]

There is a chance this could be caused by a mod replacing the vanilla recruitment beacon. The "stranger" trigger is placing and powering the vanilla recruitment beacon.