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
disable
resurrect (or ressurect 1 not sure if it works in Fallout 4)
enable
However if you already tried the ressurect command this probably will not work either.
The main questions are what killed him and when I do not recall any of them being killed at least not outside an attack on the place that as far as I know only happens while we are present at the place.
- In best case they will come up and act normally, depending on which script ran and what point.
- In worse case you will get a useless NPC, with no proper alias checks, due to him being "dead."
- In worst case game messes up an alias check to character that was resurrected, which may break NPC behaviour and quest lines where these characters were involved.
Comment was not targeted exactly on Duke, but as general advice. Resurrecting named NPCs isn't really recommended. Severity of problem depends entirely if game can create alias checks to such character after resurrection, or not.And in my experience even reviving a quest NPC can go without bugs, had to bring back to life Barney Rook because the old man decided to die before i met him.
And always be sure you have a save to roll back to if something goes wrong no matter what you're up to.