Triggering an rival runner's quest. No indicators whatsoever.
Bungie name: Asphyxxia#4910
Platform: PC/Steam
Description of issue:
Can't recall the name, but one of priority contracts requires breaking in the Processing Armory which locks the immediate area down and spawns a few waves of UESC, including two Commanders. As the title suggests, using the Processing Armory when anyone on the map has the contract triggers the lockdown, regardless of whether that runner is still on the map or alive. What was meant to be a quick trip to the Armory before exfil, turned into an unsolicited firefight with UESC and ended with my demise due to missing final exfil.
If it's a rival runner's quest, even if contested, shouldn't trigger quest related events unless me or someone on my crew has that contract. Alternatively, there should be a way to tell a rigged or normal armories apart as this does not happen under normal circumstances. While I understand that some contracts can be sabotaged by rival runners, it's often telegraphed that a POI has a contract, but not in this instance.
Date and time: Roughly 15 minutes prior to this post.
Repro steps: Unlock Processing Armory while a rival runner in any given match has the aforementioned contract regardless of their status.
Comments
Hello there,
Thank you for your report and additional information.
We are aware of the issue with Processing Armory lockdown / red barriers misbehaving when a MIDA priority contract is in play. We are currently investigating this issue.
Please sign in to leave a comment.