-
Notifications
You must be signed in to change notification settings - Fork 1
Description
Copy-paste from the dev-tracker thread that is applicable here too I guess:
QUOTE (me)
Yar, QStat has issues with NS2's own query-responder for not adhering strictly to the query-protocol (which is surprising), it has to do with QStat demanding a challenge for the rule\player-reply, which NS2 does not give, rather you're supposed to just directly request the data. GameOvermind's QR did both the challenge- and the direct-approach.
Enough of the jibber jabber, what you need to do is query all the servers directly (no need to look a port above or under anymore), and lift the tickrate- and ns2build-information from the gametags-field. It is part of the general-reply (the one that contains the server-name\maxslots et cetera), and looks like: build|gamemode|tickrate %. The uptime-information isn't exposed through it, so that won't be available anymore for the moment, though you don't have to remove the code associated with getting that data from the rules-reply, as when the rewrite of GM is done (in 2020), it'll work again with QStat.
Upside to all this for the moment, is that you can fetch the tickrate-data of all servers that run GM per definition (gives an insight into how many servers actually run it at this point).
CODE
result['tag']
Would be the code in question here.