Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
You will have issues in your game and in some time your game will be borked.
Dont make suggestions you dont know what they actually do.
In your case you first make one copy of the dead one that have got one script run that tells the game that the NPC is dead.
After that you actually restore the copy, that dont have anything to do whit the dead npc.
DONT.
Here's an in depth view of Console Commands (probably more than most want to read, but absolutely necessary seeing the misunderstanding that so many have regarding the use of them and their effects).
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/
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.
Mini tutorial on the console here;
General Discussion and Tutorial Pages
http://steamcommunity.com/app/72850/discussions/0/485622866435280490/
http://steamcommunity.com/app/72850/discussions/0/451848854987583992/#c451848855002328904
From: http://en.uesp.net/wiki/Skyrim:Form_ID
"With unique NPCs however, a second copy will usually cause problems with quests and such. In that case, one could move the NPC to the player with the command sequence:
prid <RefID>
moveto player
For most items, creating extra copies does no harm, so player.additem <BaseID> <quantity> can be used to add the desired quantity of items to the player's inventory. Quest-specific items, however, will suffer from the same problems as unique NPCs, since the quest will often be tied to specific RefIDs for objects, not their BaseIDs. Also, RefIDs can only be used if the object in question is loaded into memory; visiting the cell of the object can assure this. See the console article for further commands and uses of form IDs for other types of things."
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
IN ADDITION:
Ilja:
I think it is best to explain resurrect a bit further. I might actually make a full post about it.
Biggest risks come down to scenes. Each character participating scenes has an alias. These aliases are required to be filled by Papyrus, when the scene starts. Here are few common cases about how the use of console can affect to them.
Scene starts, but character is dead. There is no character to fill alias. If script does not intercept the event, then Papyrus will try to fill the alias - over and over again. This will reserve all available Papyrus time, often preventing other scripts from running.
In this case locating the missing character, resurrecting them and bringing them to scene to fill alias can be helpful. Of course, you would need to have a log and know what you are looking at, including how to get rid of such character later, so that using console would not break the game even further.
Second scenario. Scene starts. Game considers one of the participants dead, but player has actually resurrected that character. Scripts may bring this character in to scene and attempts to fill alias. This may or may not work, depending on scene and other scripts (including mod scripts) running around.
Again, Papyrus will get stuck, trying to figure out which alias it needs to fill. Solution sounds easy: load a previous save and kill the character.
Reality is not that easy. Scene may have been initialized several saves ago, if you have been running around the area. Script to cut it may fail, because it is going against Bethesda's design, while trying to fill alias for a present "dead" character. Again: you might have to start making logs and trying to figure out when and where the scene got stuck - if you even figure out what is going on.
The more characters you have resurrected, the more changes the game has to use at some point initialize a scene. This also means that game has even more changes to fail filling aliases and completing the scene.
Civil War is a PITA in this. There are plenty of scenes and civilian characters are prompted to locations around times. This means that game will try to fill more than few aliases at the same time. Each character that is affected - and not necessarily even a quest giver or merchant - will be positioned.
For example: Battle of Whiterun, where some characters you have moved away from the city through HF DLC (or mods) will be there to get involved. If game finds such characters, then it will bring them in to scenes. Them being "dead" may still cause game to attempt fill aliases and cause Papyrus exceed it's limits.
I really do not recommend resurrecting characters, just because you can. If you do resurrect a character, then do that only for 1st scenario (if you know what you are doing) and then get rid of them for good. Otherwise: find and load an earlier save, where scene is not stuck.
http://steamcommunity.com/app/72850/discussions/0/133256959379908095/?tscn=1487016428#c133256959380839601
Once dead you are dead.
You can tell me anything.
I know, you dont.