Closed a-sync closed 10 months ago
Apparently Post Scriptum
got its protocol changed multiple times from squad
to valve
and reversed over the years, on the last change the squad protocol was removed (had only some custom cleanups, the rest is already in valve protocol) and ps was left on the squad
protocol.
The easy fix here is to change the protocol to valve
(I will make a release in the upcoming days), you can query it like this gamedig --type protocol-valve 92.118.18.92:24001
.
But if i define the query port it works with the exception of player numbers.
Apparently the game responds with 0x00
on the players query, not sure if there is any other way to get them, will do separately.
Solved in the soon-to-be-released 4.3.0
When can we expect this to be released?
As of writing, it is released! Link to 4.3.0 here.
Thank you! When will the player querying be fixed?
Not sure of it, as I mentioned in my first comment the game doesn't seem to send any data for the players query, there could be other methods to get current online players but currently, we don't know of others.
Describe the bug Attempting to query a post scriptum server return unexpected errors. (gamedig version 4.2.0)
Steps To Reproduce Example server: battlemetrics.com/servers/postscriptum/24677356 Host + port is
92.118.18.92:24000
. Query port is 24001Expected behavior Returning the server details and the player list.
Screenshots or Data expected to work like this:
$ gamedig --type ps --port 24000 --host 92.118.18.92 --debug
Additional context If i switch the type to
squad
(which has the same query protocol) it sort of works.$ gamedig --type squad --port 24000 --host 92.118.18.92 --debug
Notice it only attempted to check the defined port and not port+1, even without --givenPortOnly flag. But if i define the query port it works with the exception of player numbers. (always returns 0)
$ gamedig --type squad --port 24001 --host 92.118.18.92 --debug