search

johnnyguitarFP / deadmatterdedisetup

11 stars 6 forks source link

Query Port (not Port) is hard set to 27016 #5

Closed humangenome closed 4 years ago

humangenome commented 4 years ago

Both issues were just closed but the issue is not resolved.

The Steam Query Port cannot be changed. It's hard locked to 27016.

Game port can be changed as the examples show. The problem is the query port (what server list and connecting clients use) is hard coded to 27016. This means you can't create more than one game server on a single machine (problem for GSPs or people with high performance nodes)

humangenome commented 4 years ago

You can see by checking resource monitor open ports. -QueryPort appears to work in launch param but it is still also opening 27016 every time.

johnnyguitarFP commented 4 years ago

The Query port is not hard locked to 27016, you can check the examples to see how to change the Query port. This is the same method I use for the official servers and should allow you to host multiple servers on the same box.

humangenome commented 4 years ago

Right. It may show in the server list but it is not queryable (cannot fetch information about the server)

They overlap 27016. You can check two or more game servers that are running on the same box and see 27016 in the list of open ports.

To fetch server information via Steam query it would need to be adjustable off of 27016. I am sure there are other unmentioned things dependent on a unique Steam Query Port.

Ryan Pennington

On Sun, Aug 23, 2020 at 8:07 PM Johnny Guitar (Nikolas Zorko) < notifications@github.com> wrote:

Closed #5 https://github.com/johnnyguitarFP/deadmatterdedisetup/issues/5 .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/johnnyguitarFP/deadmatterdedisetup/issues/5#event-3683500698, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAR62DQ5FQNFC3WLT2DLZBDSCHKPBANCNFSM4QJAX6IA .