Hosting a Server
From Vector Strike Wiki
More actions
See also: Public Servers
Windows
This method uses SteamCMD and expects basic knowledge of the command line.
- Install SteamCMD
- Open the SteamCMD executable file and let it initialize itself
- Run
force_install_dirfollowed by the install path you'd like to install the server to. For this example the server will be installed to C:\VectorStrikeServer. This path is NOT recommended and is for example purposes only. Please locate a memorable, organized place to put the server. Full command would beforce_install_dir "C:\VectorStrikeServer" - Log in to Steam Public with
login anonymous, this game has no restriction on hosting. - Run
app_update 3675450. This should install all the files to the previously set install dir. - Locate the now installed server, right click MercuryServer.exe and click Create shortcut. Change the properties of the shortcut so the target has
-log[1] at the end. The target field should now look something like thisC:\VectorStrikeServer\MercuryServer.exe -log. Please note that the path will differ depending on where the server was installed. - This shortcut can now be moved anywhere, renamed, and ran. This will open the server.
Linux
The SteamCMD depot does not contain any Linux server files at this point. Basic Linux CLI knowledge is expected. Installation has to be done manually.
- Install the files from this link
- Extract the ZIP somewhere memorable, and cd into the LinuxServer folder.
- Congratulations, you can now run the server in the terminal by running
sh MercuryServer.shorbash MercuryServer.sh. Pretty simple.
More complex setup can be done to dockerize or run the server in systemctl but this will not be covered here.
Extra
Depending on the method of hosting, such as a home computer, the UDP port 7777 will likely need to be opened. This will allow external users to connect to the server. Your IP is what other players will connect to.
Footnotes
- ↑ This ensures that the server is VISIBLE when opened instead of running in the background. Running in the background is heavily discouraged as it can lead to multiple instances being opened without knowing.