VEIN: Fixing Game.ini Settings That Are Ignored On Launch
One of the most common problems new VEIN dedicated server hosts run into is editing the config file, restarting the server, and watching nothing change. The server name stays as the default, the password does not take, and the people you added as admins still cannot run commands. This guide explains why it happens and how to make your settings actually apply.
🧟 Quick Overview
- Game: VEIN by Ramjet Studios
- Status: Steam Early Access (released 24 October 2025)
- Engine: Unreal Engine 5
- Server App ID: 2131400 (separate from the game)
- Config files:
Game.iniandEngine.ini
Why VEIN Ignores Your Settings
VEIN runs on Unreal Engine 5, and like most UE5 servers it does not read settings from an arbitrary file you create. It reads from generated config files in a specific Saved/Config folder, and it only writes those files out after the server has been launched at least once. Three things trip people up:
- The file does not exist yet. If you install through SteamCMD and immediately edit a file you created by hand, the server may generate its own copy on first launch and overwrite yours, or simply ignore a file in the wrong location.
- The setting is in the wrong section or file. VEIN splits configuration across
Game.iniandEngine.ini, and each setting belongs under a precise section header. A correct value under the wrong header does nothing. - The server was running while you edited. If the process is live when you save, it can overwrite your changes on shutdown. Always stop the server first.
Where The Config Files Actually Live
The files are not in the install root. After the first launch they appear under the platform-specific Saved/Config directory:
| Platform | Config path (relative to install) |
|---|---|
| Windows | Vein/Saved/Config/WindowsServer/ |
| Linux | Vein/Saved/Config/LinuxServer/ |
Important: If that folder is empty or missing, launch the server once and let it fully start, then stop it. The folder and the Game.ini and Engine.ini files will be generated for you to edit.
The Settings That Get Reported As Broken
On Reddit and Steam discussions the recurring complaints are that ServerName, the password, and admin access do not apply. The reason is almost always the section header. In VEIN these identity settings belong under the game session section, not a made-up [ServerSettings] block. Edit Game.ini like this:
# Game.ini
[/Script/Vein.VeinGameSession]
ServerName=My VEIN Server
Password=
AdminSteamIDs=76561198000000000
AdminSteamIDs=76561198000000001
[/Script/Engine.GameSession]
MaxPlayers=8- ServerName and Password live under
[/Script/Vein.VeinGameSession]. Leave the password empty for a public server. - AdminSteamIDs takes one SteamID64 per line. Use a converter to get the 17-digit ID, not the vanity name.
- MaxPlayers lives under
[/Script/Engine.GameSession]because it is an engine-level value, not a VEIN-specific one.
Engine.ini And The In-Game Admin Menu
Engine-level options, such as the day and night cycle speed, go in Engine.ini. A common gotcha is the day/night multiplier, which is a console variable rather than a plain key:
# Engine.ini
[ConsoleVariables]
vein.Time.TimeMultiplier=1.0Watch out: when you change settings through the in-game admin menu, VEIN writes those choices to Engine.ini automatically. If you later hand-edit Engine.ini while the game also has values stored, the two can conflict. Decide whether you manage a setting in the file or in the menu, and stick to one.
The Correct Edit Procedure
The single most reliable fix is to follow the same order every time:
- Stop the server completely. Confirm the process has exited, not just that the window closed.
- Edit and save the correct file (
Game.inifor identity and gameplay,Engine.inifor engine options) under the right section header. - Restart the server and watch the log to confirm it loaded.
Skipping the stop step is the number one cause of "my changes reverted". The server holds the config in memory and can flush its own copy back to disk on shutdown.
Linux Specific Notes
On Linux, the server is installed through SteamCMD under App ID 2131400 and launched from the binary inside Vein/Binaries/Linux/. A typical launch line looks like this:
./Vein/Binaries/Linux/VeinServer-Linux-Test Vein -log -Port=7777The config still lives under Vein/Saved/Config/LinuxServer/. File names on Linux are case sensitive, so make sure you are editing Game.ini and not a stray game.ini that the server is not reading. Check ownership too: if you run the server as a steam user, that user must own the config files, otherwise edits made as root can be ignored or fail to save.
Quick Diagnostic Checklist
| Symptom | Likely cause | Fix |
|---|---|---|
| Server name unchanged | ServerName under wrong section | Move it under [/Script/Vein.VeinGameSession] |
| Admins cannot use commands | Vanity name used instead of SteamID64 | Use the 17-digit ID, one per line |
| Changes revert on restart | Edited while server was running | Stop, edit, save, then start |
| File not found | Server never launched once | Launch once to generate config, then edit |
| Max players ignored | Set in the wrong file or section | Use [/Script/Engine.GameSession] in Game.ini |
Frequently Asked Questions
Why is there no ServerSettings.ini?
VEIN follows the Unreal Engine 5 convention of Game.ini and Engine.ini under Saved/Config. Older guides that reference a single ServerSettings.ini with a [ServerSettings] block do not match how the server actually reads configuration.
Do I need to restart for every change?
Yes. Config files are read on startup. Some options can also be changed live through the in-game admin menu, but file edits require a restart to take effect.
How do I find my SteamID64?
Use any SteamID converter and copy the 17-digit number that begins with 7656. The vanity URL name will not work in AdminSteamIDs.
Where do I put the game port?
Pass the port on the launch command with -Port=7777. Keep port-related entries consistent and avoid duplicating them across both INI files, which can cause startup issues on UE5.
My Linux edits still do not apply. What now?
Confirm the file is in Vein/Saved/Config/LinuxServer/, that the case matches exactly, and that the user running the server owns the file. Stop the server, edit, save, then start and read the log.
Related Guides
- Set up a VEIN dedicated server from scratch
- Full server configuration reference
- Admin permissions and commands
- Fix common VEIN server issues
- Hardware requirements
VEIN Server Hosting: Skip the config-file guesswork. Managed VEIN server hosting from Supercraft exposes server name, password, admins and gameplay options through a panel, applies them to the correct files, and restarts cleanly so your hardcore survival world stays online 24/7.