Does anyone know how to fix a settlement that is permanently under sentinel attack?

[Jaggid Edje]

In my main save, my settlement has permanently been "Settlement Status: Sentinel alert level high!" for the last year and a half (as shown when viewing "The Settlers" in the alert notifications). The result is that every time I visit it, I'm under attack by corrupt sentinels.

They don't respawn if I kill them all while I remain at the settlement, but they do any time I leave and return. That notification also persists in the lower right of the UI, no matter where I am.

And no, I do not have Traces of Metal causing this. I finished that whole quest chain (and all other non-repeatable quest chains) a long time ago on this playthrough. It also shows a different message in the notification are of the UI.

The notification I'm seeing is specifically the one for the settlement itself which normally gets cleared once you defeat the sentinels....it simply just does not clear, ever, on this particular save. I have a dozen other saves where it's all working normally.

Anywho, I'm wondering if anyone has any advice on how I can resolve this. I'm open to any kind of solution, even save editing. I just have 0 idea what to look for to edit in the save.

I did already try adjusting, specifically, the Sentinel alert level for the settlement, but it doesn't help long term...as soon as the settlement gets up to the level where it would be attacked, which always happens over time, it gets stuck again.

[Azure Fang]

I'm sure I already know the answer to this, since it's you, but I still have to ask to be thorough: Does this happen with all mods disabled?

The only times I've heard of this happening is with older mods that touch Settlement assets and with ToM active (which you've already discounted for your case).

As a longshot, it's also possible the alert state of your settlement might have become corrupted. Boot up the save editor, go into raw JSON, into "BaseContent>SettlementStatesV2", hit CTRL+F and search for your Steam username (or settlement name, either way). When you find it, grab the value of "LastAlertChangeTime" and convert it into a human-readable time (such as via https://www.epochconverter.com/ or similar). If the timestamp is for a date in the future, a date impossibly in the past (1970's, etc.), zero, or negative, change it to the unix timestamp for "now" and see if that fixes it.

[Krastifari]

robots... beep boop!

[Jaggid Edje]

@Azure Fang, yah, it remained a problem even with all mods disabled.

On the bright side, the problem is gone (at least for now). I did two things yesterday, after posting this, that I haven't done in a really long time:
1. I went into full offline mode (steam itself offline) and,
2. I actually talked to the visitor that arrived a the settlement (the settlement has long since been basically capped, so I haven't been doing that).

I'm not sure which if either of those things resolved the issue, but suddenly the constant attacks have stopped. We'll see if that continues once I go back online.

I checked the LastAlertChangeTime and it was just a little before 'right now'.

[Azure Fang]

Originally posted by Jaggid Edje:

@Azure Fang, yah, it remained a problem even with all mods disabled.

On the bright side, the problem is gone (at least for now). I did two things yesterday, after posting this, that I haven't done in a really long time:
1. I went into full offline mode (steam itself offline) and,
2. I actually talked to the visitor that arrived a the settlement (the settlement has long since been basically capped, so I haven't been doing that).

I'm not sure which if either of those things resolved the issue, but suddenly the constant attacks have stopped. We'll see if that continues once I go back online.

I checked the LastAlertChangeTime and it was just a little before 'right now'.

Your point 2 makes me wonder if the alert state is tied to the change queue. After I've played out the Warframe update coming on the 2nd, I might test that for funsies.

Glad you got it to stop, at least.

[Khalum]

Originally posted by Azure Fang:

I'm sure I already know the answer to this, since it's you, but I still have to ask to be thorough: Does this happen with all mods disabled?

The only times I've heard of this happening is with older mods that touch Settlement assets and with ToM active (which you've already discounted for your case).

As a longshot, it's also possible the alert state of your settlement might have become corrupted. Boot up the save editor, go into raw JSON, into "BaseContent>SettlementStatesV2", hit CTRL+F and search for your Steam username (or settlement name, either way). When you find it, grab the value of "LastAlertChangeTime" and convert it into a human-readable time (such as via https://www.epochconverter.com/ or similar). If the timestamp is for a date in the future, a date impossibly in the past (1970's, etc.), zero, or negative, change it to the unix timestamp for "now" and see if that fixes it.

My settlement is also permanently "under attack" so I gave your suggested fix a go. Didn't change anything unfortunately. I *think* this broke when Worlds pt1 removed sentinels from my planet - the event is queued but can't resolve because the sentinels that would attack aren't allowed to spawn. Just a theory though.

[Jaggid Edje]

I find it interesting, at least, that I'm not the only one that has had this issue @Khalum.

For me it started quite a while before the Worlds Update though, like nearly a year before. (And my planet still has hostile sentinels)

[Khalum]

Okay, I decided to spend a little more time on this while I'm at it and I think I fixed it: There's a "Stats" array (in raw JSON) for your settlement, and the last value appears to be the sentinel aggression factor. I guessed this because it was exactly 100 for my settlement, which I interpreted as 100% aggression. Just set it to 0 and the "under attack" status should be gone.

[Jaggid Edje]

For me that was only a temporary solution. That stat grows over time, until it reaches 100% and you get attacked again. It did stop the attacks for me, just like it did for you, but once it grew back to 100%, it became stuck there again. (I did mention that in my original post in this thread)

[Khalum]

Ooh, right. Well, I guess we're just unlucky then. ^^

[Jaggid Edje]

I dunno, I consider myself kind of lucky, actually. While other people post having bugs like "My multi-tool vanished", "My Living Ship turned into a Hauler", etc. All I have experienced is "I get an opportunity to get sentinel loot every time I visit my settlement".

I'll take our glitch over those other ones any day!

[Jaggid Edje]

Originally posted by Khalum:

Ooh, right. Well, I guess we're just unlucky then. ^^

I'm just returning to tell you that my problem settlement remains problem free, even now that I have returned from the expedition and am back in online mode. Hopefully yours stays problem free for you too.

[GrumpyGnome]

I have this bug and looks like it is going to stay. No mods, tried the suggestions here, uninstalled reinstalled and the settlement is stuck in sentinel alert level high! The best I can do is hope for an accidental fix to an accidental circumstance. Been waiting for over a month for it to go away.

[Jaggid Edje]

Originally posted by GrumpyGnome:

I have this bug and looks like it is going to stay. No mods, tried the suggestions here, uninstalled reinstalled and the settlement is stuck in sentinel alert level high! The best I can do is hope for an accidental fix to an accidental circumstance. Been waiting for over a month for it to go away.

Yah, the problem came back for me as well around a week or two after I posted above saying that it went away.

I've been experiencing the issue since last year but can't figure out exactly what causes it. At this point I've just given up trying to.

[Despistao]

la rotacion de "el asentamiento esta siendo atacado" es cada 4 dias reales, no es ningun fallo, ni mal funcionamiento

[Jaggid Edje]

Originally posted by Despistao:

la rotacion de "el asentamiento esta siendo atacado" es cada 4 dias reales, no es ningun fallo, ni mal funcionamiento

You might want to read again. What we're saying is that it is always being attacked with no way to clear that state. That's a bug. "Always" =/= "every 4 days".

For that matter, every 4 days isn't exactly accurate either. There's a rating for the settlement which determines the rate the aggression meter grows. It can be faster or slower depending on what was built at the settlement and some (albeit rare) settlement decisions.