VEIN Dedicated Server Update Guide
VEIN has main and experimental branches. Treat an update as a package and save migration: record what you had, back it up, update the same instance, and prove the world works before the group returns.
Before updating
- Read the official announcement feed.
- Record app
2131400, branch, build, OS, launch command, and current ports. - Tell players the maintenance window.
- Stop cleanly and copy the active save and configuration.
Update and test
- Update the same server package; do not silently switch branch.
- Start privately and read the log.
- Join with one client on the matching build.
- Check world identity, base, player access, a harmless save, restart, and reconnect.
- Only then reopen the server.
Rollback
Stop the new process, preserve its logs and save, restore the dated pre-update copy, and start a test instance. Never delete the failed copy until the original world and build are confirmed healthy. Use save management.
Related guides
Run updates through managed VEIN hosting with a panel workflow.