Instalar Steam
iniciar sesión
|
idioma
简体中文 (Chino simplificado)
繁體中文 (Chino tradicional)
日本語 (Japonés)
한국어 (Coreano)
ไทย (Tailandés)
български (Búlgaro)
Čeština (Checo)
Dansk (Danés)
Deutsch (Alemán)
English (Inglés)
Español - España
Ελληνικά (Griego)
Français (Francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (Húngaro)
Nederlands (Holandés)
Norsk (Noruego)
Polski (Polaco)
Português (Portugués de Portugal)
Português - Brasil (Portugués - Brasil)
Română (Rumano)
Русский (Ruso)
Suomi (Finés)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Informar de un error de traducción
add "enable" at the end
ssq ms09
prid 47ec4
ForceRefIntoAlias emogeneOld
ForceRefIntoAlias emogene
MoveTo 518ce
enable
https://www.nexusmods.com/fallout4/mods/47634/
The 2019 patch actually fixed it, but it would seem that the NG patch has brought it back, in true Bethesda fashion. Regardless the mod ought to work.
https://gamefaqs.gamespot.com/boards/164593-fallout-4/76213833
Here below the complete sequence of commands:
ssq ms09
prid 47ec4
ForceRefIntoAlias emogeneOld
ForceRefIntoAlias emogene
MoveTo 518ce
enable
I had this happen to me a fair few times, had to use the console, so I did some changes/investigation on how I was doing things, now what triggers this to happen is taking the Castle early without the minutemen. I did not test it with the minutemen so can't comment on that. Under no circumstances take the castle if anything avoid it and entering the cell area, and you will not get this bug for the Cabot quests if you are leaving Preston in Concord.