Lead Engineer @ Packetware
How To Move Your Rust Server To SteamWorks Networking
How Raknet v2 Currently Queries Servers
Facepunch have forked Raknet v2 in order to maintain an unmaintained protocol and fix issues with the aging of the tech. Alongside this fork they developed a way for the game port to simultaneously be the Query port for a2s_info packets to be distributed when called.
Current SteamWorks Implementation
We lose our player favorites because we can't implement the Rust Queries on the same port that we used previosly as the game port so the server browser see's our server as a new server. We can counteract this by swapping the query port by swapping the game port and the query port so the browser see's our server as the same as previous IP:Port.
Default Ports:
| Usage | Default Port | Protocol |
|---|---|---|
| Game Port | 28015 | UDP |
| RCon Port | 28016 | TCP |
| Query Port | 28017 | UDP |
| App Port | 28082 | TCP |
Retaining Server List Data:
| Usage | Default Port | Protocol |
|---|---|---|
| Game Port | 28017 | UDP |
| RCon Port | 28016 | TCP |
| Query Port | 28015 | UDP |
| App Port | 28082 | TCP |
How to set this up.
We need to add this to our startup arguments so the networking protocol can be applied on startup. Now that we are no longer using the default ports we can specify the following.
-swnet
+server.port 28017
+rcon.port 28016
+app.port 28082
-queryport 28015
The result should be as follows and you will no longer have to use the default port selection when querying servers.
Pterodactyl Setup
If you want to go about retaining your favorites in Pterodactyl game management panel you will have to associate a different primary game port and add it to your allocation.
Modifying the startup arguments by appending those needed to swap the game and query ports.
