Dark Brotherhood Bug - Nazir and Narfi

[GhostFactory]

So I was going through the Dark Brotherhood questline, got my first set of contracts from Nazir and (spoilers maybe :P ) was asked to kill Narfi. I didn't want to kill him, so I tried to complete the quest using console commands. The command I used was:

setstage dbsidecontract01 255

I realise that I went a *little* too far and it marked the whole quest as completed, but Nazir doesn't count it as so. The other contracts I can say to him are done, but the dialogue option for Narfi doesn't appear and now I can't get the 2nd set of contracts. Anyone know of a fix?

I tried resetquest, setobjectivecompleted, setstage (for an earlier stage), even recycling, disabling and enabling both Narfi and Nazir, but nothing. I can't load a previous save either (I kinda deleted them without thinking).

[Helrato]

Why would you join an assassins guild if you have no intention of being an assassin?

[Gapk]

I guess this is the people that later complains about Skyrim bein buggy as hell when they are using without knowing console commands like candy

[GhostFactory]

I joined because I wanted to see the questline for myself. I knew I had to kill Narfi, so I tried to avoid it as best I can (everyone else I don't care that much about), I just always felt bad or him, ya know?

As for console commands, I admit I'm not the best at them, only the basics, but I do realise most of the bugs I encounter are either my fault, either in a mod or in the vanilla game. I just didn't expect this to happen.

So anything other than this would be much appreciated...

[ELF EYES]

a safer way to do the kill and also let the person live its kill then do this ~` then click on npc then type resurrect then hit enter then go on

[GhostFactory]

I'll try it hopefully it works. Thank you :-)

[smr1957]

Regarding use of console commands:

Ilja:
Console is a debug tool. It does not pass event and AI scripts, or undo scripts that have been already been ran. I have stressed several times that using resurrect is among those commands that you should never use in Skyrim.

If the character you resurrected was dead, then using the command does not undo death scripts that have already been ran. Game AI gets confused and in 99% of cases you will just have a no-good character wandering around. In worse cases, death scritps will have run other scripts and suddenly "alive" character starts to cause conflicts in the game.

If the character you "resurrected" is alive (and in this case a quest character), then scripts affecting to this character now has double targets, messing up the game AI royally.

Load a save from before using unsafe console command. Do not try to undo it in any other way, because Skyrim stores script data to save files and there is absolutely no way to clean them 100% from them. Even Bethesda didn't manage to do so.

http://steamcommunity.com/app/72850/discussions/0/451848854985133583/

Also:
Re: Resurrecting Named Characters (quoted from post by Ilja)

"You should never resurrect any named characters in Skryim. Game runs death scripts for each of them. Using resurrect command does not undo these scripts and there is no known way to reverse them.

Resurrecting character that has death script records in save file usually ends up badly. In best case scenario you get a useless NPC that is not tied to any quest and is cut out of the progress. In worse case scenario you get NPC that is comes constantly more and more bugged, tangling game scripts even further and ends up making a real mess out of your game.

Resurrect is among commands that has been classed as dangerous and should not be used in a game. It is a developer test command and should be treated as such. If you already made a mistake of using that command, then load a save before that." -Ilja

And:
cfs111
If you don't know what you're doing, using console commands can cause your game to malfunction! Executing the wrong command can cause your game to stop working normally; furthermore, you may not become aware of such malfunctions right away, and you may not be able to trace their cause. They can cause problems like making quests impossible to complete, altering your game's display, all kinds of game behaviors, your ability to play your character, and your ability to play the game at all. Solutions are not always easy, and may involve losing saved games or reinstalling your game.
Create a permanent saved game before using the console. (This mitigates only some kinds of risks.) If you need to use the console to fix a glitch, try to use the least powerful command possible.

[GhostFactory]

Oh..ok

[Uncle64]

Originally posted by smr1957:

Regarding use of console commands:

Ilja:
Console is a debug tool. It does not pass event and AI scripts, or undo scripts that have been already been ran. I have stressed several times that using resurrect is among those commands that you should never use in Skyrim.

If the character you resurrected was dead, then using the command does not undo death scripts that have already been ran. Game AI gets confused and in 99% of cases you will just have a no-good character wandering around. In worse cases, death scritps will have run other scripts and suddenly "alive" character starts to cause conflicts in the game.

If the character you "resurrected" is alive (and in this case a quest character), then scripts affecting to this character now has double targets, messing up the game AI royally.

Load a save from before using unsafe console command. Do not try to undo it in any other way, because Skyrim stores script data to save files and there is absolutely no way to clean them 100% from them. Even Bethesda didn't manage to do so.

http://steamcommunity.com/app/72850/discussions/0/451848854985133583/

Also:
Re: Resurrecting Named Characters (quoted from post by Ilja)

"You should never resurrect any named characters in Skryim. Game runs death scripts for each of them. Using resurrect command does not undo these scripts and there is no known way to reverse them.

Resurrecting character that has death script records in save file usually ends up badly. In best case scenario you get a useless NPC that is not tied to any quest and is cut out of the progress. In worse case scenario you get NPC that is comes constantly more and more bugged, tangling game scripts even further and ends up making a real mess out of your game.

Resurrect is among commands that has been classed as dangerous and should not be used in a game. It is a developer test command and should be treated as such. If you already made a mistake of using that command, then load a save before that." -Ilja

And:
cfs111
If you don't know what you're doing, using console commands can cause your game to malfunction! Executing the wrong command can cause your game to stop working normally; furthermore, you may not become aware of such malfunctions right away, and you may not be able to trace their cause. They can cause problems like making quests impossible to complete, altering your game's display, all kinds of game behaviors, your ability to play your character, and your ability to play the game at all. Solutions are not always easy, and may involve losing saved games or reinstalling your game.
Create a permanent saved game before using the console. (This mitigates only some kinds of risks.) If you need to use the console to fix a glitch, try to use the least powerful command possible.

1+
Reposting it so others that suggest console read it.

The only solution for solving the issue is to load one old save before you have tinkered whit console.

[GhostFactory]

Yeah... reloading an old save isn't possible. :\

[Uncle64]

Ok, you are playing and use autosaves. Then you perhaps have learn something today then.
When it comes to Skyrim. Dont rely on them.

[GhostFactory]

One does not simply rely on autos saves. I have forevery broken the brotherhood haven't I. .... :'(

[Uncle64]

And you should turn off cloud save, since that dont work as it should for Skyrim.
You only have like 4-6 saves there.

Why cant you revert to one old save?

[alexander_dougherty]

Don't use console command slike setstage unless you absolutely have to, like a bugged quest.

Avoiding killing an NPC doesn't count.