Please help! SetStage not working

[Willow McPlier]

I'm trying to reset the Dark Brotherhood Quest (currently at stage 50) so that I can get the 'Destroy DB!' quest (DB02 stage 220) instead of Sanctuary (DB02 stage 200). I go to the console and type in-

SetStage DB02 10

It shows up in the box. When I check my quests, nothing happens. I've been trying to fix it for nearly and hour and nothing has worked. Please hel!

[Zsrai]

Why would you try that? Just load an old save. Don't use the console if you don't know what the ♥♥♥♥ you're doing with it.

[Willow McPlier]

I don't have any saves that old. I've risen up nearly 20 levels since then, I dont want to basically replay the game, I just want to reset the one quest

[fauxpas]

Unless you reload an old save from before you started messing with the console you'll have no choice but to start over again since all you can and have accomplished is introducing script errors into your game and they WILL eat your save to the point where it eventually won't even load.


But hey, if you want to destroy your game, go ahead, why should I care?

[Jouchebag]

Basically, if you need to ask for help with console commands then you shouldn't be using console commands.

[fauxpas]

Not to mention having a good sense of what can and can't be done using the console.

[Zsrai]

Originally posted by Willow McPlier:

I don't have any saves that old. I've risen up nearly 20 levels since then, I dont want to basically replay the game, I just want to reset the one quest

Well, now you know that you should save more than once every real life day then. Live and learn. Especially about now messing with the console or anything quest related if you don't know what you're doing.

P.S. - You can't "reset" a quest.

[fauxpas]

Yet another way to kill your save, never turn off mods midplay either.

[fauxpas]

Originally posted by Toast:

Originally posted by fauxpas:

Yet another way to kill your save, never turn off mods midplay either.

Never? Eh, maybe. I say try it. I'm still doing alright going off the same save progression. Maybe you'd like to school me about it. I'd be grateful to learn something new. Honest. :ss13ok:

Short version is that disabling mods doesn't do anything to clean up the script triggers that are baked into your save, which leaves orphaned scripts floating around in your save just waiting to strike.


Turning those mods back on doesn't solve the issue either as what typically happens is that you get duplicate (and sometimes conflicting) script triggers baked into your save, which is even worse.

[alexander_dougherty]

Originally posted by Willow McPlier:

I'm trying to reset the Dark Brotherhood Quest (currently at stage 50) so that I can get the 'Destroy DB!' quest (DB02 stage 220) instead of Sanctuary (DB02 stage 200). I go to the console and type in-

SetStage DB02 10

It shows up in the box. When I check my quests, nothing happens. I've been trying to fix it for nearly and hour and nothing has worked. Please hel!

Data is baked into saves, so the game knows you've already gone past that stage. So you reset it, it looks and goes "hey, the next stage is already completed, and the next? oh there's the stage it's at" and presto your back to step x again (just like you never typed the command, and it does it quicker than you can notice).

[alexander_dougherty]

Originally posted by Toast:

Originally posted by fauxpas:

Short version is that disabling mods doesn't do anything to clean up the script triggers that are baked into your save, which leaves orphaned scripts floating around in your save just waiting to strike.


Turning those mods back on doesn't solve the issue either as what typically happens is that you get duplicate (and sometimes conflicting) script triggers baked into your save, which is even worse.

Mmmm... yeah, alright. Duplicate scripts are bad, m'kay. I think I can appreciate that. I'm sure that by now I have loads of them too. I'm doing fine though. It's probably negligible for the most part.

Probably isn't. Have you read up on save bloat?

[Mewfii]

All i use console for is tcl pcb tgm and palyer.additem 000000f 99999999, I cheat but still try and be realistic, if you can this that...

[Jouchebag]

Resetting a quest also doesn't reset dungeons, bosses, unique items, quest trigger switches, etc.

If you need to beat a certain boss to continue the quest and you already killed him, resetting the quest will not bring him back and you'll be forced to use more console commands to continue.


The most common problem with borked scripts in saves is decreased stability over time. This usually results in simple, occasional CTDs. Those could occur with as little frequency as once every 10 hours or as often as once every 15 minutes depending on how badly broken the save is.

In worse cases you could have a completely corrupted save that won't even load or loads once every 2-3 tries.

[Grumpy]

objective measurement?

if you crash but its only happen in that playthrough, you cant track it back to mods and you know you used at some point critical console commands in the past

[smr1957]

This is not in response to Toast who is either really a nattering nit wit, or is trolling and just acting like one (though I suppose it is also possible that they truly are a totally ignorant know nothing who doesn't even know enough to begin an attempt to learn), this is for those who may be new and actually want to take the time to learn why you SHOULD NOT REMOVE MODS MID-PLAYTHROUGH (it is also linked in the PINNED!!!!! topic Helpful Links And References):

You CANNOT Remove Mods Mid-Playthrough
http://steamcommunity.com/app/489830/discussions/0/1520386297681801135/

[Jouchebag]

Originally posted by Toast:

Originally posted by Grumpy:

objective measurement?

if you crash but its only happen in that playthrough, you cant track it back to mods and you know you used at some point critical console commands in the past

Very objective.

And if this random crashing should happen on a brand new game, I should assume time travel is involved?

No, you should assume your mod list is broken somehow.