Hosting a server
Server on Windows
Download
Section titled “Download”On the release page,
download two files: Node-Server-1.12.0-windows-x64.zip and
Node-Server-1.12.0-windows-x64.zip.sha256.
To check that the archive arrived whole, run this in PowerShell in your downloads folder:
$zip = "Node-Server-1.12.0-windows-x64.zip"(Get-FileHash $zip).Hash.ToLower()(Get-Content "$zip.sha256").Split(" ")[0]The two lines must be the same. If they aren’t, download the archive again.
Unpack and start
Section titled “Unpack and start”Unpack the archive into a folder of its own, such as C:\NodeMP, and double-click
Node-Server.exe. The same from PowerShell:
cd C:\NodeMP.\Node-Server.exeThe server’s window is also its console: it shows the log and the chat, and takes commands (Console, kicks and bans). Keep it open while you need the server. Closing it stops the server cleanly first.
What’s in the folder:
| What | Why |
|---|---|
Node-Server.exe |
The server. |
tools/ |
The client-script obfuscator and the Lua 5.1 it runs on. Nothing to set up on Windows. |
modules/ |
The database module for plugins. |
examples/ |
Ready-made example resources (Resources). |
cacert.pem |
Root certificates for machines that have none. Keep it. |
Open the port
Section titled “Open the port”Open PowerShell as administrator and allow incoming connections on the server’s port:
$port = 30814New-NetFirewallRule -DisplayName "NodeMP TCP" -Direction Inbound ` -Protocol TCP -LocalPort $port -Action AllowNew-NetFirewallRule -DisplayName "NodeMP UDP" -Direction Inbound ` -Protocol UDP -LocalPort $port -Action AllowIf the computer is behind a router, forward the same port to it, TCP and UDP. Test from outside: a connection from your own network says nothing about the router.
Start with Windows
Section titled “Start with Windows”To have the server come back after a reboot, create a task in Task Scheduler:
- Action → Create Task.
- On General, choose Run whether user is logged on or not.
- On Triggers, add a trigger At startup.
- On Actions, add Start a program: program
C:\NodeMP\Node-Server.exe, start inC:\NodeMP.
The start folder matters: the server looks for server.toml, resources/ and content/ there.
A server started this way has no window, and so no console.