Closed ghost closed 6 years ago
UltimateByte
commented
6 years ago The query string is a bit different between the two engines. https://github.com/GameServerManagers/LinuxGSM/blob/master/lgsm/functions/gsquery.py#L21-L28
You can try playing around with them and see if you come to some conclusions.
What about details command? The issue could also come from here: does it work as intended? Provide a postdetails link output to let us check.
ghost
commented
6 years ago Seems the result of what I was trying to do is okay. No side effects so far.
https://hastebin.com/raw/yazugaloju
I changed the engine in the config and things seems to be responding okay. Monitor works and there don't seem to be errors of other commands so far.
UltimateByte
commented
6 years ago Good to know. Could please you share you changes so that we can reproduce it and fix it natively inside LGSM?
ghost
commented
6 years ago I just defined the engine variable in my config to "idtech2".
engine="idtech2"
dgibbs64
commented
6 years ago The W:ET engine is idtech3 but queries on idtech2 engine...How odd. We will need to put a specific statement in for W:ET as we should not change the engine variable as it would be inaccurate.
dgibbs64
commented
6 years ago There appears to be a bug in gsquery that is nearly a year old https://github.com/GameServerManagers/LinuxGSM/blob/master/lgsm/functions/gsquery.py#L21
the querys are listed the wrong way around.
lock[bot]
commented
5 years ago This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
While attempting to monitor a Wolfenstein ET server, gsquery reports it's "unable to receive". The engine seems to be the culprit. "idtech3" (default) doesn't provide a response but "idtech2" does. In what aspects is the engine important to other functions? Any feedback on this particular setting would be helpful.