You can run a One Hour One Life server on your own VPS with ZapX. The One Hour One Life server is open source: you download the source code from the developer, build the server yourself, and run it on Linux. This guide explains what you need, how to build the server, and how your players can connect.
One Hour One Life is not included in the Game Server Installer and does not have a ready-made dedicated server available through SteamCMD. You set up the server manually, as described in this guide.
The developer builds and runs their servers on Linux. If your VPS runs Windows, install a Linux template via Settings > Reinstallation. This deletes all data on your VPS. For more information, see Server Reinstallation.
Settings are stored as individual files in the OneLife/server/settings/ directory. Each file contains exactly one value. The most important ones are:
| File | Default | Description |
|---|---|---|
port.ini | 8005 | Server port |
maxPlayers.ini | 160 | Maximum number of players |
requireClientPassword.ini | 0 | Set to 1 to require a password to connect |
clientPassword.ini | testPassword | The password, if required |
requireTicketServerCheck.ini | 1 | Checks logins against the official ticket server |
For a private server, the developer sets requireTicketServerCheck.ini to 0 in their test script. If you set a password, be sure to change clientPassword.ini—the default value is publicly known.
Players set up a custom server in the game. To do this, they edit these files in the settings directory of their game installation:
| File | Value |
|---|---|
useCustomServer.ini | 1 |
customServerAddress.ini | Your VPS IP address, shown under Overview in the ZapX dashboard |
customServerPort.ini | 8005 or the value in your port.ini |
serverPassword.ini | The password from clientPassword.ini, if you require one |
The server and game should be running the same version; otherwise, the connection may fail.
| Port | Protocol | Use |
|---|---|---|
| 8005 | TCP | Game (value from port.ini) |
If you use a system firewall, open the port there. For more information, see Firewall on Linux. If you use your VPS’s Network Firewall in the ZapX dashboard, open the port there as well.
