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
Then execute in the console by using the command "bat filename" without the quotes filename being what we named the txt file we saved in the folder the fallout4.exe file is located.
But if we wanted to for example add a lot of building materials we would need to know the load order of the DLC or mod the item comes from then run something like this.
Its up to each individual how they want to play the game Personally I prefer the chalange when actually playing the game however when creating then testing a mod sometimes we have to cut corners or it would take years to fully test and debug one for release.
Especially when we add perk and level restrictions to certain parts.
As someone recently pointed out to me: The Workshop Extended (IIRC) mod allows an unlimited build mode.
Otherwise the bat files a lot of people use are functional, but seriously clunky. Seems unnecessary.
As for clunky, why have a mod running constantly rather than typing "bat buildmats" and its done.
I couldn't have said it better!