the Sim Settlements forums!

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Jammer's Walk

RandomMeister

New Member
Messages
0
Hello!
So i have a bug, where ive just taken over Snshine Co as my raider base of operations, then went over and vassalized Abernathy farm. After that, i was supposed to go back to Jammer and report. But he WALKED all the way down to Murkwater Construction Site? Then he stood there saying "Shit, gunners-" and so on, but it didnt activate anything seeing he wasent in my base, at all.
So im stuck now, i cannot move him, wait for him or kill him. He just likes his new home too much...
 
I have the same problem too. Jammer went and hung out at the Castle for me though. When I talk to him he just acts like a regular settler.
 
Are either of you getting new settlers in your settlements or is an AWOL Jammer the main issue?
 
In my game I just took over my first outpost, Starlight, and when the quest said to go talk to Jammer, the map show him in Nuka World. The 'Door' icon for his location is over the Nuka Transit center.

Does anyone have Jammer's ID so I can console summon him back?

Thanks!
 
I had one raider show up, but that's it. I don't know what happened to all the ones that Jammer sent with me to claim the outpost. Otherwise, Jammer is the main issue I seem to be having. He mentioned something about gunners after I claimed a vassal, then he lolnop and went walkabout.

This was on a preexisting save though. I started a new save this morning and I'm gonna see how that goes, but I've been getting a lot of CTD lol. I don't that that's Sim Settlements related though.
 
My regular settlements (Sanc. and RR) have settlers showing as normal. I haven't put a recruitment beacon up at Starlight, my first and only Outpost.

Jammer is still in Nuka World. I'm hoping he comes back. I'm just running a around with Cait doing Jet and picking locks. :)
 
I'm having this problem as well. Claim an outpost and vassal , Jammer wanders off to a random settlement, says he wants to use it as a base of operations, says something about gunners attacking then pretty much switches to why are you bothering me type dialog. This has happened twice so far, once he wandered to nordhagen and the second time to taffington.

I went back to an earlier save on the taffington play and took over taffington as my outpost (hoping he would wander there again) and low and behold he looks like he is on his way here, it also made him city leader. I'm guessing something is wonky with the script where he wanders to a random settlement rather than the outpost settlement like he should (should note I tried to use sanctuary as an outpost the first time, red rocket the second time and I had assigned a city leader and started the cities before I took them over as Jammer's I love you, maybe having the leader already assigned had something to do with the weirdness)? Will update again after he gets here and I get a vassal settlement going.

Vassal settlement is setup and when I returned to report in, I got the gunner's dialog, like they are attacking but don't, then its back to nothing is going on type of dialog or trade window.
 
Last edited:
This thread has been reported. :pilot

Thank you-all for taking the time to report what you are experiencing in game. :clap

:happy
 
In my game, Jammer's PRID is 19009CCE
Moveto player

Bam. There he is. My quest is progressing now. Sweet.

I don't know why I didn't think of it earlier, but I just went back to an earlier saved game, got his ID.
Duh.
 
In my game, Jammer's PRID is 19009CCE
Moveto player

Bam. There he is. My quest is progressing now. Sweet.

I don't know why I didn't think of it earlier, but I just went back to an earlier save a D got his ID.
Duh.

Rudy "Thank You" that alone will be a big help for other pc players :clap
 
This may help too. Hopefully.
I experienced the same "Gunners" bug once I subdued a 2nd settlement.
Using console commands I found the quest ID.
Then the stage I was on: 160
Then I looked up all the quest stages to see if I could force it to move forward. The quest stages for this quest stopped at 80: Return to Jammer.

50 = Kill Jared
60 = Kill Tower Tom
70 = Kill Red
80 = return to Jammer

Somehow the remaining quest steps didn't show up in the list and yet I was on objective 160.

Hope that helps!

Edit: wiki link for quest console commands
http://fallout.wikia.com/wiki/Fallout_4_console_commands
 
this did not help me sorry to say ive even tried the oldest save i have
 
Last edited:
This may help too. Hopefully.
I experienced the same "Gunners" bug once I subdued a 2nd settlement.
Using console commands I found the quest ID.
Then the stage I was on: 160
Then I looked up all the quest stages to see if I could force it to move forward. The quest stages for this quest stopped at 80: Return to Jammer.

50 = Kill Jared
60 = Kill Tower Tom
70 = Kill Red
80 = return to Jammer

Somehow the remaining quest steps didn't show up in the list and yet I was on objective 160.

Okay 151 was where I was hung at the nonexistent gunners, setstage kgConq_Raidergang 152 advanced it to after the attack. nice!.
 
How did you guy get the console commands to escalate the quest to work?
As I keep getting the "not found for parameter quest", as I'm also stuck on the Gunner's not showing.
 
The quest ID has to be exact when you type it in. I got that same error but realized I misspelled it.

setstage kgConq_RaiderGang 152

Then I had to rope Jammer out of Nuka World.
prid 19009CCE
moveto player

The dialog is wonky for a bit, but it levels out and I can progress the quest line.

Tip: Once I had Jammer in front of me, I used the dialog options to re-assign him to my hq. Seemed to do the trick.
 
I can see what's wrong, I kept writing kq instead of kg. Now I'm back on track again.
Thanks. =)
 
Spawning him in with his ID didn't work for me. So I advanced the quest to stage 152 and then ordered him to change base to a settlement I had already conquered, rather than the one he wandered off to. That worked for some reason.
 
Top