Menu
What's new
By:
Filters
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!

No Response Recruitment and Slavery Questions

A

Adamo

Member
Messages
38
I've seen some people talk about some of these things, but it didn't cover all of my concerns so I thought it was best to open up a new thread to ask a couple questions.

Are we sure that recruits should show up with a beacon? That doesn't seem to be happening for me, but I would like to troubleshoot it if we know it should be happening. Jammer recruits seem to work OK. Do we need to use the regular recruitment beacon or the Nuka-World raider one? I was also wondering... does anyone know if raiders that are recruited using the Nuka-World beacon will actually be hostile to my gang? I think @kinggath mentioned that the game thinks they're the same gang, so he could take advantage of the map icons, but I'm not sure. I don't know how to tell if the hostile raiders that came by are from my beacon or just randoms walking around the world.

How should I expect to be able to get more slaves? The first time I took on a vassal it seemed to work OK: settlers and civilians still live there, somewhat happily, and work stuff. I tried to vassalize Somerville, though, I think all of the civilians died, but the settlers were still alive; HOWEVER, these were just those three settlers at Somerville, and I think the game does have them in a different state than most, since the kids and that one adult aren't commandable without console commands, so it's hard to be deductively sound on this. Is it expected that the Civilians will all die, leaving only settlers? I thought the expectation was that all "settlers" would be civilians at a computer-managed outpost, and so then I would expect them to not die but be enslavable once they're downed, right?

This leads to a specific question: how long should I have after a successful vassal attack to enslave people before they go back to doing whatever it was they were doing? I realize now that I'm assuming one mode to get slaves is to run a vassal attack and then take some of them as slaves to send back to your outpost. Is that thing, or is the only way to get slaves to run a new slaver outpost attack? Maybe the best general question I can ask, instead, is: how do YOU get new slaves? So I can make sure this works for me. Because NEED MOAR SLAVES.

Thanks.
 
Until I get the 4.0.1 patch out with some fixes to deal with the blatant issues, like people suddenly dieing for no reason, there's likely going to be a lot of questions like this that I'll refrain from answering now, as it will just lead to more confusion.

I can say in general, the way you get slaves, is to start by doing a Slave Outpost, which you get access to after you complete the first two raids for Jammer. Once you capture a Slave Outpost, you gain the Slaver perk, which includes the ability to craft Slave Collars.

Then in the future, you can either do Vassal attacks or Slave Outpost attacks to gain more. The difference, is that Vassal attacks, you're leaving the settlement in control of the settler/civilians to take advantage of their resources without you needing to manage them, and when the NPCs are knocked down in the Injure state, you can collar them and send them to any outpost. The Slave Outpost attacks will convert any surviving NPCs into slaves after you complete the attack to convert the settlement into an Outpost.

Though like I said, there are several issues, that are not consistent, people are running into I'm still trying to solve so that information like the above holds true. Right now, depending on the mods you have, or the order you're doing things in, some stuff just gets weird.

Ultimately, I'll be making a series of in-depth videos to explain all of these mechanics, and also get them written up for the wiki, so you have a final place to confirm if things are working as intended.
 
OK, thanks. It sounds like my gameplay is in the right direction, then, and we're just working out some bugs. I will help if I can... I'll see if you have instructions somewhere to submit save game files.
 
kinggath said:
. . . and when the NPCs are knocked down in the Injure state, you can collar them and send them to any outpost.
Click to expand...

I'm guessing you need to do this as you down them during the raid because once the attack is over, they get right up.
 
Ain't Much said:
I'm guessing you need to do this as you down them during the raid because once the attack is over, they get right up.
Click to expand...
They're actually supposed to say seated for about 20 seconds, but yes, the idea is you would do that while your raiders are cleaning up the last couple of stragglers. Getting lots of reports about the collar mechanic being unreliable, so I'm going to have to do a bunch more testing during raids to see what's going on.
 
Cool. I'd like to suggest perhaps enhancing the notice during the raid where it says "Subdue any remaining ______ to also say "Collar now!" Ha!
 
I have a saved game where I am about to attack Warwick and the attack is confirmed to have the issue, @kinggath, but the problem is I have about 60 mods. I can't find the text file with my mod list, but I had planned to post on that thread to help with the eliminations. I looked for a few file names suggested online, but haven't had time to look deeper for the list after not finding those. I also thought I remember you explained somewhere how to submit a saved game, but I haven't found it, yet. Maybe it was in a video.
 
I attacked Starlight to enslave
I stunned a settler at the beginning of the battle, i went near him, but there was no option to enslave.
The settler was sitting, a bunch of gunners arrived, i launched a granade and the settler died together with the gunners; arent settler supposed to be unkillable ?

At the end of the battle a settler was sitting idle. I pressed Q by mistake instead of W and:
All my raiders appeared red, like they were enemies even if they didnt shot me; probably a graphic glitch.
The sitting settler raised and started attacking, i shot him and he died; he didnt come back sitting, he lost his head and died, but there was no explosion; think this is the problem going to be addressed

Question is: how i'm i supposed to use the collar? when the first settler went down i had no option to enslave, at the end of the battle all subdued settlers were already collared.
 
I believe my conditions to show the Enslave mechanic aren't working correctly. Most people report it works for a split second between when they are down and they stand up, which means I screwed up something just before launch. :(

Will get it fixed ASAP.
 
Once they are enslaved, do they actually go to work? My slaves stand around and in some instances when arriving back at a settlement, they stand in the same place. In workshop they are showing assigned, but it would be nice if they physically did their animations at the work they are assigned. None of them move around or do anything at all work-animation wise.
 
It seems like they work fine for some settlements and not for others. I haven't done any deductively-sound tests to know for sure. I definitely have at least some slaves who just stand around doing nothing. This *SHOULD* earn them a good lashing.
 
They continue to use the same AI package, so if they are standing around - it's the same issues that can occur with the vanilla NPCs: navmesh problems, lack of assignments, too much scripting in your save causing AI to be sacrificed, too many NPCs in the area, etc.
 
If it's just a graphic problem, they are strolling idle but they are working, it's not a big issue; after all once you removed weeds and given fertilizer you dont need to talk to your tatos to have them grow.

Raiders working farms are producing half because they dont like it and are not good, it's ok; i noticed that also slaves produce half; is it as wanted or a bug?
 
You must log in or register to reply here.
Top