LogFAQs > #931110938

Destiny posted...

then you probably killed someone that was important to their quest.

No, other people who've had the problem have specifically investigated that and dismissed it as the cause, because they didn't kill any quest-important NPCs (in some cases, they didn't even go to any of the places where those NPCs are supposed to be found, so literally could not have killed them).

In fact, some people have mentioned that, in spite of the quest autofailing, it still causes those NPCs to spawn where they need to be, and you can find them and talk to them, but their dialogue doesn't trigger the quest flags because the quest is already flagged as failed, so it's definitely programming fuckery and not just killing the wrong NPC too early.

Again, Obsidian support has already said they're aware of the problem and are working to fix it, which implies they understand it isn't just "Oops, you killed one random NPC and tanked an entire major questline" (though even if that WAS the case, that's shit-poor game design regardless). The problem is that there seems to be no way to avoid or fix it player-side, which means you can't use workarounds like "Don't go to X place before triggering Y step in the quest" or "Don't kill X NPC before completing Y step".

And because the player really has no control or way to prevent the bug from occurring, it means "Guess you'll have to start over and try again" isn't a viable solution either, because there's no guarantee you won't just hit the same bug again. Which becomes even more of a problem when you may have to play upwards of 20 hours before you even HIT that bug in the first place.
---

"Wall of Text'D!" --- oldskoolplayr76
"POwned again." --- blight family