By default they've got Protected status meaning they go into helpless downed stat, have to have had their HP reduced to 0 by the player in order to die. Unless there's some kind of modifier I didn't know about that will make the command kill an NPC even if they have Protected status? Killing the settler yourself will make entire settlement hostile(Plus any companion who is with you), lasts a while so it's annoying. This persists even after killing everybody there and I believe it lasts longer based on how many are killed.killall
If you're at level 3, just killall and regress away.
Doesn't work because they need certain keywords in order to function properly as settlers(in order to be assignable/movable).player.placeatme 00020593 1 <"1" being how many settlers you want
It's annoying but that's what I do. Killed like 10 one time and settlement remained hostile(even when adding settlers from 0 population or moving some from elsewhere, they immediately become hostile) for over an in-game week so I just reloaded. I think if you kill only one they're hostile for like 3 to 5 days but I haven't done that in a long time, guessing it might stack if you killed multiple. A little too annoyingly long for me, even if I unlock FPS while Waiting/Sleeping via Load Accelerator's Shift+Page Up shortcut.so i guess I'll have to just send them all away, or send away some....
Nice thanks! Even has an ESL version! Love it when they have that, so I can just install & forget. No worries about it taking up ESP slots.I use Banish Settler Button.
https://www.nexusmods.com/fallout4/mods/30011
You basically create a button thingy for like 1 steel, then go to any campfire/stove craft a blackspot for 1 steel. Trade it to a settler then push the button and it removes settlers with the black spot.
I used it to get rid of the female ghouls, cant stand the voice for the settlers.
Awesome thanks! A definite must have and solves the topic!After you click the button to banish it takes about 2-3 seconds for it to vanish. That is even in a settlement I have pushed the budget up 2-3 times.
Not sure how it works exactly, all I know it is pretty simple and easy to use and the fact you have to trade an item means no accidently removing the wrong settler.
Not correct.By default they've got Protected status meaning they go into helpless downed stat, have to have had their HP reduced to 0 by the player in order to die.
Yes it does.Doesn't work because they need certain keywords in order to function properly as settlers(in order to be assignable/movable).
I missed this earlier....By default they've got Protected status meaning they go into helpless downed stat, have to have had their HP reduced to 0 by the player in order to die.
Interesting! I will have to try it out. I'll use glitchy Never-Ending Laser Musket. It loads ALL your Fusion Cell ammo into one shot so you can get over 1000 times damage multipliers!I missed this earlier....
That is not entirely true. Protected units can still die to drowning. They also can die if they take too much damage at once and your script processing is lagged or slow (as in too high fps.) It is a rare thing, but it can happen.
I must have some mod interferingNot correct.
killall *generally*wont kill unique NPC's. Settlers yes it will. Do it all the time.
The down side to it, is it will take out your turrets too.
Interesting! I will have to try it out. I'll use glitchy Never-Ending Laser Musket. It loads ALL your Fusion Cell ammo into one shot so you can get over 1000 times damage multipliers!
Hmm even at Water World I still get settlers sitting on the bottom of the ocean in helpless mode. Maybe I have some kind of mod making it so they can't die from drowning or falling(Tried ModPos Z 10000)
I missed this earlier....
That is not entirely true. Protected units can still die to drowning. They also can die if they take too much damage at once and your script processing is lagged or slow (as in too high fps.) It is a rare thing, but it can happen.
Protected units can still die to drowning. They also can die if they take too much damage at once and your script processing is lagged or slow (as in too high fps.) It is a rare thing, but it can happen.
Thanks for the info! I've added this to the Vanilla Mechanics article as unconfirmed. Can anyone confirm this one in code/in game?.
That is how it worked in Oblivion/Skyrim. There's a "breath underwater" magic effect & if you're Argonian or an underwater creature you get an ability that includes constant "breath underwater"I would take a look at mirelurks. There must be some attribute or ability there that tells the code they breathe water. Most likely a 1/0 type ability which you could flag on settlers?
I mean I would give it to an NPC & then make them shoot a settler with StartCombat {Ref ID}. Maybe I will try it out with a bleeding effect weapon too. I could go to empty Cheat Room cell, use MoveTo Player to bring a Settler along then spawn some enemy like a Raider, OpenActorContainer 1 to give them the weapon then use a Stealth Boy so they don't attack me. It actually occurs to me that I am not sure how a Never-Ending Laser Musket will function when used by an NPC, since it appears to be buggy when used by the player. I doubt it is intentional by Bethesda to use up all of your fusion cells in 1 shot and that's likely why you can't obtain them other than by forcing a Laser Musket to have Never-Ending Legendary effect, might be a decision by Bethesda to omit them. It's kind of funny though & I'm mildly curious to figure out how much damage it can do, like if I do SetAv Health 1000000 on some enemy then check before/after HP values. I wonder if 1000 fusion cells = 1000x damage multiplier? You also can't normally obtain Never-Ending Missile Launcher, Never-Ending Fatman, Explosive Gatling Laser(it's a step above Explosive Minigun due to fire rate).The problem with that is if you do that damage it will void the protected status silly. You need attacking mobs with high weapons. Like I said it is a rare occurrence. Also I think any legendary weapons on the mobs with bleeding can do it.
Wow that's pretty interesting stuff. I guess the same probably has happened to me but I always figured there simply is a chance of leaving. It usually happens a lot if happiness is really low but I figured it can happen even if happiness is high, if settlers are idle and/or homeless. I guessed that if there are any idle/homeless settlers, there is a low chance of one of them leaving. If I don't visit a location for a while(Maybe 20 in-game days passing) & it's not a city plan/having recruitment beacon, even in fairly self sustaining ones I sometimes can find settler count has gone down by 1 or 2.Not sure if the in game code can confirm it. However the general consensus among all the high play time Steam posters is we agree that is the case. The combat death is really rare, I think I have lost maybe a half dozen provisioners in 4000 hours. Deaths due to drowning is very common at Warwick and Spectacle Island.
How do I put it? It is like how the game code says you can not have more than 4 idle settlers at a settlement because then the recruiting beacon ceases to recruit. Yet if you set up a settlement with a high happiness you can come back a week or two later and be way over 4 idle settlers.
So technically the code is right, but the game play says otherwise. Those with extensive play time are more apt to see this depending upon their playing habits.This is because the settlers are not given the idle flag until you are present in the cells with them.
Wow that's pretty interesting stuff. I guess the same probably has happened to me but I always figured there simply is a chance of leaving. It usually happens a lot if happiness is really low but I figured it can happen even if happiness is high, if settlers are idle and/or homeless. I guessed that if there are any idle/homeless settlers, there is a low chance of one of them leaving. If I don't visit a location for a while(Maybe 20 in-game days passing) & it's not a city plan/having recruitment beacon, even in fairly self sustaining ones I sometimes can find settler count has gone down by 1 or 2.
We use essential cookies to make this site work, and optional cookies to enhance your experience.