Open Next-Door-Tech opened 1 year ago
Thank you for the report!
This is not actually a bug, missions always reset when you quit.
This is not actually a bug, missions always reset when you quit.
Ah. I know that's true for regular missions that happen while embarked on a passage between locations, but I figured that this mission would be different since it takes place while docked at a friendly Coalition outpost, and you can save and quit without losing progress at friendly outposts without leaving. (FYI, "Keeper of Silence" is the special Church Ecclesiast mission where you have to assassinate a Coalition security officer in an outpost who is interfering with Church operations.)
I suppose I should mention that the behavior here allows for the player to farm unlimited non-stolen gear (mainly ballistic vests, helmets, and health scanner goggles) from the operative since his inventory is not marked as stolen goods, and items removed from his body are kept through the save and quit.
I suggest you load the save file I attached above and follow my reproduction steps. This may be working as initially intended but I think this one may need to be reconsidered as undesired behavior.
What's the status of this ticket?
I guess no-one's gotten around to addressing it yet. After reading the newer comment, I agree this is something that should be addressed. Now when you save mid-mission in the outpost like this, it only "partially" saves the progress, meaning you get to keep the effects of the events, the items you got from the NPC and such, but can still retry the mission. I suppose we should also save the state of the mission.
Disclaimers
What happened?
After assassinating the target during the "Keeper of Silence" mission, if you save and quit before travelling to another station, the mission will still be active and the target will be alive when the save is reloaded.
An affected save file is attached. 1.0 Campaign.zip
Reproduction steps
Bug prevalence
Happens regularly
Single player or multiplayer?
Single player
-
No response
Version
v1.0.21.0
-
No response
Which operating system did you encounter this bug on?
Windows
Relevant error messages and crash reports
No response