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
the games exe or launcher will check for steam running first
from x:\...\steam\steamapps\common\gamename
to x:\games\gamename
As far as FO4 though, never really had an issue with the updates breaking mods. Update your mods and you shouldn't have an issue. Use 3rd party launcher called Fallout 4 Configuration Tool - By Bilago. Use that to configure your game and other options such as graphics, use it launch the game, as well as check the options to make the game config files read only. This helps incase you ever launch the FO4 launcher from stream, it won't be able to revert your game config files since they are now set to read only. The config tool however still can.
If you're still in need of a batch file for your custom Fallout 4 launcher, I'm posting one for you. As a SysAdmin I've had to write scripts for somewhat analogous purposes in the past, so I modified one to suit your objectives. It will check to see if Steam is running, and if it is it will run your custom FO4 launcher; if Steam is not running it will offer to run it for you, then try running your launcher after Steam loads. The script was tested on my Windows 10 x64 system and performs as expected.
Copy the code below, paste it into a text editor, change the two user variables at the top of the script to your full Steam path (in the script this is already set to Steam's standard location on a 64-bit machine) and the full path of the Fallout 4 launcher, and save the file with whatever name you want, making sure to add a '.bat' extension. You can then run the script either from the console or by creating a shortcut to it and double-clicking. There are additional instructions in the form of comments in the script.
Let me know how it works out for you.
But ... but ... but .... you used a goto. A GOTO! Oh nose. You are giving me code to blow up my PC. The horror. :(
Kidding of course
Windows batch isn't like other languages. Unlike most modern high-level languages, in which the use of GOTO is rightfully eschewed and usually can be completely avoided, in batch GOTO is sometimes preferable or even necessary. I always write my batch code to be as modular as possible, and in a number of cases avoiding the GOTO would lead to much code duplication. In this case GOTO is the lesser of two evils. Furthermore, since batch lacks true exception handling, GOTO is almost always used in cases of error checking, which is how it's used in my script.
If you'd like to attempt re-writing the script to eliminate the GOTO's, please be my guest.
And I like yelling at clouds and chasing kids off my lawn.
That script still works in 2025! But you have to remove the variables' check part. (The "if not exist" paragraphs.)
That helped me setup a custom Split Fiction launcher!
Kudos to you.