VEIN Server Configuration Guide
VEIN configuration advice is easy to get wrong because Early Access builds and hosting templates may expose different files. The public dedicated-server reference documents the app and launch path, but it does not establish a complete supported gameplay-key catalogue. Use this page to make a change safely and to distinguish a real setting from a copied example.
ServerSettings.ini, ZombieSettings.ini, section headers, and multipliers as unverified unless the current package, panel, or build documentation shows them.Find the active instance
- Stop the server and note the instance name, install directory, branch, and build.
- Inspect the panel's file manager or the package's generated configuration directory.
- Launch once if the current server needs to create defaults, then stop it cleanly.
- Compare timestamps after a known panel change so you know which file is authoritative.
- Back up the files and save before editing.
Change one setting at a time
| Area | Check first | Proof after restart |
|---|---|---|
| Identity | Server name, password, visibility control shown by the current panel or file. | Reconnect and verify the listing or access behavior. |
| Ports | Launch flag, provider mapping, firewall, and query/game distinction. | Test listing and an actual join separately. |
| World rules | Exact key and section in the current build. | Use a harmless test change in a copy of the world. |
| Admin | Current panel or documented identity format. | Test a second account with the smallest privilege. |
| Performance | Whether the control exists in the current branch. | Compare CPU, memory, logs, and player experience. |
Why edits appear to be ignored
- The panel regenerates a file at startup.
- The edit was made in a template or inactive instance.
- The key is under the wrong section or is not supported by this build.
- The server was running and wrote its in-memory state back on shutdown.
- The file owner or permissions prevent the server user from reading the edit.
- The client and server are on different branches or builds.
Safe rollback
Stop the process, restore the dated copy of the configuration, start once, and inspect the log. If the world itself is affected, restore a separate save copy and verify it before replacing the live world. Use the ignored-settings checklist and save management.
Reference and update boundary
Use the dedicated-server reference for the app, launch example, and ports. Check the official announcement feed for branch changes before treating an old setting as current.
Related guides
Use managed VEIN hosting if you want panel-backed configuration and backups rather than maintaining files by hand.