Solved Raider freeloaders and Jammer's unauthorized block party!

[Grim Experiments]

Hi Guys,

I'm hoping you might have a solution or at least some insight into some strange happenings after the 4.1.1. update. I have 4.1.1. Three-in-One & Conqueror, also the Workshop Framework 1.17 which seems wasn't updated this time.

I returned to my outpost after about 1-2 days in game time, after I updated, and when I got there I discovered about 42 raiders (not including some I found on the roofs of various plots I found later). I only had 9 when I left the day before. The thing is that my hud says I have 18 and I figured it was just a little glitch, so I'll just run some raids, but the raider boards says I have insufficient (0) troops.

I noticed on a post from about 2-days ago that someone said try to assign them manually in the workshop. So I tried:

• About 10 can be assigned outside of workshop. My standard clowns.
• 20 can be assigned inside workshop but that doesn't do anything and they don't become assignable outside.
• The final 10 can't even be selected in workshop. These guys aren't like the plot associated guys but they might be visitors and things just got blown out. I have switched that off to see if it helps.

If anyone else has experienced this please, let me know!

Thanks!

EDIT: I changing what few troops I can control doesn't change my assualt troop availability count either.

 

[Raider106]

Hi Guys,

I'm hoping you might have a solution or at least some insight into some strange happenings after the 4.1.1. update. I have 4.1.1. Three-in-One & Conqueror, also the Workshop Framework 1.17 which seems wasn't updated this time.

I returned to my outpost after about 1-2 days in game time, after I updated, and when I got there I discovered about 42 raiders (not including some I found on the roofs of various plots I found later). I only had 9 when I left the day before. The thing is that my hud says I have 18 and I figured it was just a little glitch, so I'll just run some raids, but the raider boards says I have insufficient (0) troops.

I noticed on a post from about 2-days ago that someone said try to assign them manually in the workshop. So I tried:

• About 10 can be assigned outside of workshop. My standard clowns.
• 20 can be assigned inside workshop but that doesn't do anything and they don't become assignable outside.
• The final 10 can't even be selected in workshop. These guys aren't like the plot associated guys but they might be visitors and things just got blown out. I have switched that off to see if it helps.

If anyone else has experienced this please, let me know!

Thanks!

EDIT: I think I discovered the 0 troops thing. There were no warrior assignments. I need to do that manually now it seesm.

Hello this happens to me too i have 30 raiders in my main base and have 28 attackers a days after i discovered something weird and is what i have 0 attacker and when i notice all the raiders what are assigned to warriors now automaticly are assigned to guards and now i have to put them manually to warriors beacuse they are guards and they arent assigned to anything.

 

[Grim Experiments]

Yeah, thanks but I tried that. I have at least 10 warriors now but it states I have none. I should note that I got rid of the 10 who were "visitors", but these other guys hanging around aren't even Raider Recruits, they are just Raiders.

Did you notice anything like that? I think the post I mentioned previously said that you can assign to a plot and then all of a sudden they become Raider Recruits that you can change their role on but even that doesn't work for me.

Or did you notice or do anything else?

 

[Grim Experiments]

Whoa, just as I said that last post I reassigned their settlement through the workshop menu an voila, it worked!

Lol, thanks again Raider, it just takes a little experimenting.

EDIT: BUUUUUT that only worked for one raider, I might be at the limit. And I still don't have any "attackers available for assault". I need to keep fiddling.

EDIT2: Had everyone unassigned from roles. Now everyone is assigned as warrior. HUD shows 19 warriors, 1 worker (salvage beacon), 7 beds when there are 20. Still noone available for raids.

 

[kinggath]

The ones labeled just Raider are actually visitors. Sounds like that system is going nuts for you, best to disable it in the Immersion options, then leave the area and return to have them cleaned up.

Per you not being able to run raids with 19 warriors - I unfortunately can't replicate this - so my gut reaction is that this is a mod conflict or version problem (ie. your mod manager swapped the esp file but is still using the old ba2 files).

 

[Grim Experiments]

The ones labeled just Raider are actually visitors. Sounds like that system is going nuts for you, best to disable it in the Immersion options, then leave the area and return to have them cleaned up.

Per you not being able to run raids with 19 warriors - I unfortunately can't replicate this - so my gut reaction is that this is a mod conflict or version problem (ie. your mod manager swapped the esp file but is still using the old ba2 files).

Hmmm. That's an interesting idea. I doubt MO2 would be trying to grab the old ones but they are still on the drive and stranger things have happened. I'll give it a look. Yeah about 10 visitors left after I killed the setting but there were still 10 other raiders sticking around. Those "sticking around visitor raiders" were reassignable to the settlement, at which point they would convert to manageable/assignable conqueror raiders. I was going to move my outpost to see if that fires things up but I've been too busy with Uni. I'll try your method and maybe throw in a reinstall of the mod, just in case things went sideways. It isn't the end of the world. I will report back when I can in case someone else experiences something similar.

Thanks Gath

 

[Grim Experiments]

So I think I've done all the testing I can for the night. I was supposed to be preparing for an exam tomorrow but... priorities :D.

Reinstalled SS and Conq 4.1.1. Went back to a save prior to 3/8/19 update, encountered the same issue of no available troops and no scoutable locations (I was able to capture my first vassal and got notifications about scouting prior to this. Additionally all the local gangs have been run out of town and I have attended the illustrious court of King Richard the Turd).

Ran the same save with 4.1.0. and this was still happening. Turns out the new update didn't break the game. This had been happening for some time only I didn't notice because I was chatting with Jammer rather than using the war desk.
Most likely scenario? I suspect the questline with Jammer.... jammed at some point.

There were some strange happenings around the point when the Gunners attack. I can't necessarily place it chronologically because there were actually 2 other Gunner attacks before Jammer decided to speak about it. After the final attack however, I spoke with him regarding the quest I returned from and on second discussion he discussed the gunner attack and how we may seek retribution. Things seemed fine.

I don't know if this is normal but the options now with everything jammed up are:
1. Have any suggestions? - Ideas about a slave ring.
2. Ready the troops! - We don't have the numbers.
3. Why do we need this place? - Relocation choice.
4. We could do with some new recruits. - Gimme, gimme, gimme!
Note: Jammer also won't discuss bounties. I don't know if he is supposed to though.

Is there any way around this? Any way to kick things off again? I suspect it wouldn't be as simple as advancing the quest like vanilla. Anyone have an idea?

Thanks.

 

[Grim Experiments]

I suspect this will serve no-one, considering the bug was likely associated with the previous patch and now appears to be fixed. Required a reload of a much earlier save. I probably selected a save further back than necessary, but I wanted to kill Preston again... I mean play it safe. Same mod load and everything, so maybe rather doing some elimination, just load up an old save and see if the same is happening. SOLVED.

Edit: I feel I would be remiss if I didn't point out that there was one important thing changed. Timescale, I had been running it a 1/10, rather than 1/20 default. Changing this didn't fix the problem but that doesn't mean it wasn't involved. Probably unnecessary info but I prefer to be thoreau. Lol.