Loading Custom Maps in VEIN Dedicated Servers
Custom-map support is package- and build-dependent. Before advertising a custom map, confirm that the current server tool can load it, that every client can obtain the same content, and that the map does not alter the production save irreversibly.
Compatibility checklist
- Identify the map package, source, version, and dependencies.
- Confirm whether it is server-side, client-side, or both.
- Check whether the current provider template permits the files.
- Back up the vanilla world and configuration.
- Test a new world with one client before touching the main save.
Failure symptoms
| Symptom | Check |
|---|---|
| Server will not start | Package files, dependencies, branch, and log. |
| Clients cannot join | Content/version parity and client download path. |
| World is blank/wrong | Map selection and active save path. |
| Performance falls | CPU, memory, disk, and world activity compared with vanilla. |
Rollback
Stop the server, restore the vanilla package/config/save copy, and prove a clean join. Do not delete the custom files until you have captured the version and logs for the author.
Related guides
Ask about current VEIN package support on managed hosting.