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
It maybe crashing for you, but what people are saying is, it may not actually be the mod directly doing it. as in if you ran it by itself it should work fine.
Its more likely it is conflicting with another mod or it could be a combination of 3 or 4 mods that cause it, where it may work fine with others etc. There is no real way of knowing which mod is conflicting, sometimes it is trial and error.
Internet. You don't have to memorize anything, you just bookmark the link to the wiki's page that lists all the console commands and how they're used.
https://www.nexusmods.com/fallout4/mods/13285/
https://www.nexusmods.com/fallout4/mods/21497
Again,, why do any of that when the Terminal mod lays everything out in neat menus. You click on what you want and it's there. Can't be any easier. Unless the item doesn't show up in the CT menus. Then you'd have to get it via a console command. But that's usually only for mod items. There is a mod menu in CT, and unfortunately it doesn't have everything. But stuff that is in the base game or the DLC's, is ready for the taking..
That mods does absolutely nothing but reorganize your settlement workshop menu WHEN you tell it to.
You are having an issue with another mod.
for me it doesnt crash never has either