Dedicated server (U4)
This is an official guide. | ||
This page is officially maintained by Smartly Dressed Games, and serves as documentation to walk you through a specific task or feature. |
Unturned II supports listing servers through the Steam platform. Due to the in-development state there are a variety of quirks compared to hosting Steam servers in the original game. This article aims to cover them.
- Downloading the dedicated server from the tools tab requires a login during the private beta, but will be available anonymously once the game is marked as released on Steam.
- Running a client on the same machine as dedicated server(s) requires specifying the -DisableSteamServerInit launch option. Running a listen server does not require this however.
- Specifying a dedicated server name is currently done with the -SteamServerName="My Server" launch option. In the future this will be exposed in a more user-friendly manner.
RCON
The remote console (RCON) tools exist to help administrate servers without needing to connect as a player. There are two ways to invoke RCON: HTTP requests, and the RCON protocol. The setup process is not finalized yet, as SDG would like for server administrators to be able to assign RCON keys permissions and configure the port in the server config.
HTTP requests
This invocation method is intended for web-based control panels to run commands on the server. Requests can be sent to {Server}/rcon/{Command}?key={Key}&arg1=value1&arg2=value2
.
Key | Value |
---|---|
Command | ID of a command as it would be used in chat, such as teleport or tp
|
Key | An authorized RCON key you have assigned permissions to run this command. |
Arg | Key = Value pairs of arguments to the command. |
Responses are returned in JSON. If a command was found and executed the response looks like:
{ "Success": true, "Output": "{Logs}" }
Whereas a failed response which did not execute a command will contain an error explanation:
{ "Success": false, "Error": "{Explanation}" }
RCON protocol
Using the RCON protocol is more complex than the HTTP requests, but has the advantage of streaming log data from the server. To keep the method simple, the protocol is implemented as null-terminated UTF8 messages over a TCP socket connection. All RCON messages start with "RCON" followed by the version number, the type of message and then any parameters.
RCON | Version | Type | Parameters |
---|
Client-to-server messages
Authentication
Should be the first packet you send. Wait for an AUTH reply from the server as notification that you were approved for login, or ERR if you were rejected.
Key | Value |
---|---|
RCON | RCON |
Version | 1 |
Type | AUTH |
Parameters | Authorized RCON key. |
Example:
RCON 1 AUTH MySecretKey
Execute Command
Can be sent once you have authenticated to execute a command.
Key | Value |
---|---|
RCON | RCON |
Version | 1 |
Type | CMD |
Parameters | Command as would be used in chat. |
Example:
RCON 1 CMD teleport -from=player1 -to=player2
Ping
Request a PONG from the server.
Key | Value |
---|---|
RCON | RCON |
Version | 1 |
Type | PING |
Parameters | None. |
Example:
RCON 1 PING
Pong
Should be sent in reply to a PING from the server.
Key | Value |
---|---|
RCON | RCON |
Version | 1 |
Type | PONG |
Parameters | None. |
Example:
RCON 1 PONG
Server-to-client messages
Welcome
Sent after your AUTH packet is verified and approved for login.
Key | Value |
---|---|
RCON | RCON |
Version | 1 |
Type | AUTH |
Parameters | None. |
Example:
RCON 1 AUTH
Error
Sent if your AUTH packet was denied, or a packet you sent was malformed.
Key | Value |
---|---|
RCON | RCON |
Version | 1 |
Type | ERR |
Parameters | Explanation of error. |
Example:
RCON 1 ERR Bad Key
Log Relay
Sent to mirror log messages that were printed on the server.
Key | Value |
---|---|
RCON | RCON |
Version | 1 |
Type | LOG |
Parameters | Line(s) of output relayed from the log. |
Example:
RCON 1 LOG LogAIModule: Creating AISystem for world Devtest
Ping
Sent by the server to check that you are still alive. You should send back a PONG or you will be disconnected.
Key | Value |
---|---|
RCON | RCON |
Version | 1 |
Type | PING |
Parameters | None. |
Example:
RCON 1 PING
Pong
Received in response to a PING you sent the server. The time difference between when you sent your PING and got this PONG is the travel time to the server plus the processing time on the server plus the travel time back.
Key | Value |
---|---|
RCON | RCON |
Version | 1 |
Type | PONG |
Parameters | None. |
Example:
RCON 1 PONG