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
Do you have Workshop Framewor? It may solve the issue. Strongly recommended anyway, for any settlement building gameplay.
I'm sure it couldn't hurt if I installed it.
Installing Workshop Framework does not hurt, but I would advice moving the character away from settlement, before activating mod in ongoing game. Mod divides settlement quest from 1 single (very slow and troublesome) quest to several quests, so staying inside the settlement will not initialize the effect for remaining visit.
Workshop Framework has several similar things that can help you to solve issues. However, game can not do retroactive changes to script data already baked in to save files. There are always issues in solutions like this.
If this does not work, then I would contact the settlement blueprint author directly. They might know what else might be going on.