Windrose Direct Connection Tunnel Setup

Manual checklist

1. 1. Shut the server down first. Treat this as good practice. Game servers often re-sync config during shutdown or startup, so edit `ServerDescription.json` while Windrose is not running.
2. 2. Create a tunnel or proxy that exposes one public endpoint. That public endpoint must forward the chosen Windrose port over both TCP and UDP.
3. 3. Keep the tunnel port and the Windrose game port the same when possible. It is not mandatory, but it reduces confusion when you later share the Direct IP values with players.
4. 4. Enable Direct Connection in Windrose. Set `UseDirectConnection` to `true`, set `DirectConnectionServerAddress` to the public tunnel endpoint that players should use, set `DirectConnectionServerPort` to the public port you are exposing for that endpoint, and keep `DirectConnectionProxyAddress` at `0.0.0.0` unless you need a specific interface.
5. 5. Match `DirectConnectionServerAddress` to the tunnel format you actually received. If your provider gives `host:port`, put that full `host:port` value into `DirectConnectionServerAddress`. If it gives only a hostname, use that hostname in `DirectConnectionServerAddress` and keep the public port in `DirectConnectionServerPort`.
6. 6. Restart the server and test with a real external client. Do not stop at local-only testing, because the whole point of the tunnel setup is internet reachability.

Example Windrose settings

For a tunnel-backed Direct Connection setup, expose the direct connection port on both TCP and UDP.

{
  "ServerDescription_Persistent": {
    "UseDirectConnection": true,
    "DirectConnectionServerAddress": "windrose.example.com:7777",
    "DirectConnectionServerPort": 7777,
    "DirectConnectionProxyAddress": "0.0.0.0"
  }
}