Outpost Recovery Variant 7 - Objective Clarification in Description

[Ludicro]

The quest "Contact with [location] was recently lost. It's suspected that an extremist branch of the Church of Husk is using it for one their ascension rituals. Get rid of the husks, and any eventual cultists." does not state that the reactor must be destroyed for the quest to be completed.

My group and I ran up and down the outpost several times before we saw the marker was in the navigation terminal. Being told to overload the reactor would've saved confusion and our fuel rods.

[MKMoose]

This mission does not require destroying the reactor. If it did for you, it was either a bug, or it just seemed that way because the explosion killed whatever remained of the Husks and Cultists.

Do note that both humans and Husks are still alive for a while after being incapacitated. You will have to finish the Husks off since they regenerate, but in the case of humans that's not necessary and you can just wait until they bleed out or suffocate, which can take a few minutes.

It's also possible, though I would need to test that to be sure, that the game sometimes doesn't consider dead Husks as actually killed, and you might end up having to wait until the corpses despawn.

[Ludicro]

We moved all the bodies out of the reactor room and the target icon was still there. Plus the mission completed when we overloaded it saying something along the lines of "By overloading the reactor, you have disturbed the ritual...." which makes it sound intentional. There weren't even any cultists in there, just husks and husked crawlers (unless we count the husks in there being cultists which failed their ascension)

We made sure to finish all the husk off.

[SomeRandomNoobKekeke]

Bruh, and what kind of ritual were these husked crawlers performing?
This sounds like the game triggered wrong mission on the wrong outpost

[MKMoose]

There is no mission that requires a ritual to be stopped which only spawns Husks and Husked Crawlers. There's a few possible explanations at this point:

• it's a bug which caused the game to somehow trigger different parts of at least three missions - unlikely, but if real then we would require you to send the save file and the server logs if rpossible for any real chance to diagnose it further,
• you're playing with a mod that overrides the missions - you would need to check whether that mod is up to date and still supported; if so, contact the mod developer to report the oversight,
• your game files are corrupted in some way - if it's a legal copy of the game then verifying file integrity through Steam should do the job, otherwise good luck getting a better copy.

---

There is also literally no text in the vanilla game that contains both the words "ritual" and "reactor". These are the texts related to this mission:

<missionname.abandonedoutposthusks>Outpost recovery</missionname.abandonedoutposthusks>
<missiondescription.abandonedoutposthusks>Contact with [location1] was recently lost. It's suspected that an extremist branch of the Church of Husk is using it for one their ascension rituals. Get rid of the husks, and any eventual cultists.</missiondescription.abandonedoutposthusks>
<missionsuccess.abandonedoutposthusks>The ritual inside the outpost has been successfully interrupted.</missionsuccess.abandonedoutposthusks>
<missionfailure.abandonedoutposthusks>The outpost remains infested.</missionfailure.abandonedoutposthusks>
<missionheader0.abandonedoutposthusks>Ritual interrupted</missionheader0.abandonedoutposthusks>
<missionmessage0.abandonedoutposthusks>The husk ritual inside the outpost has been successfully foiled. Undock from the outpost to complete the mission.</missionmessage0.abandonedoutposthusks>

And this is the code for the mission, which notably doesn't have a targetitem="reactor" attribute which is responsible for the reactor meltdown requirement in some other missions:

  <AbandonedOutpostMission
    identifier="abandonedoutposthusks"
    tags="abandonedoutpost"
    achievementidentifier="abandonedoutpostdestroymonsters"
    type="AbandonedOutpostMonsters"
    reward="3000"
    difficulty="3"
    commonness="100"
    allowretry="true"
    sonarlabel="target"
    unhideentitysubcategories="abandonedmonster,abandonedhuman">
    <Icon texture="Content/UI/MissionIcons.png" sourcerect="256,256,256,256" color="214,50,48"/>
    <LocationType identifier="Abandoned" />
    <LocationTypeChange from="Abandoned" to="Outpost" requireddurationrange="2,3" cooldownafterchange="5" />
    <Characters>
      <Character identifier="husk" min="4" max="6" requirekill="true" />
      <Character identifier="husk" min="3" max="4" requirekill="true" multiplayeronly="true"/>
      <Character identifier="huskextremist" from="abandonedoutpostnpcs" requirekill="true" moduleflags="crewmodule" />
      <Character identifier="huskextremist" from="abandonedoutpostnpcs" requirekill="true" moduleflags="researchmodule" />
      <Character identifier="huskextremist" from="abandonedoutpostnpcs" requirekill="true" moduleflags="researchmodule" />
      <Character identifier="huskextremist" from="abandonedoutpostnpcs" requirekill="true" moduleflags="researchmodule" multiplayeronly="true"/>
      <Character identifier="huskextremist" from="abandonedoutpostnpcs" requirekill="true" moduleflags="researchmodule" multiplayeronly="true"/>
      <Character identifier="huskextremist_leader" from="abandonedoutpostnpcs" requirekill="true" moduleflags="researchmodule" />
    </Characters>
    <TriggerEvent state="0" delay="5" eventidentifier="huskextremists" campaignonly="true"/>
    <message header="missionheader0.abandonedoutposthusks" text="missionmessage0.abandonedoutposthusks"/>
  </AbandonedOutpostMission>

If there were no cultists, then it's also technically possible you're talking about a different mission altogether, but the same still applies - there's simply none that fully match your description.

[Ludicro]

I was guessing it was some sorta bug but I couldn't be sure. It could easily be one of the mods I have installed. Hopefully it doesn't happen again, if so, I'll dig a little deeper in my own game files to find the mod or what might've caused the bug.