-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BF1942 fails to parse players #88
Comments
Wasn't able to replicate this, instead I get (for the same server):
|
I think #72 might be related (and/or relevant) here. |
Ah, it seems after querying for a while I was able to replicate the issue (I think maybe the players in the servers changed and the issue I was having went away). I found the problem with this one: Logging the early return shows quite a few things get ignored like:
However after fixing the playername issue I immediately run into another where player_data["face"] is expected but not found. So I will keep looking and make it into a larger patch. |
Yeah, the current GS players fields implementation doesnt really match up with the node version, as you said, the statement doesnt include Regarding the 'extra' fields, such as |
These fields seem to be missing from bf1942 queries so make them optional.
These fields seem to be missing from bf1942 queries so make them optional.
These fields seem to be missing from bf1942 queries so make them optional.
Describe the bug
BF1942 fails in
extract_players
, backtrace:{ fn: "gamedig::protocols::gamespy::protocols::one::protocol::extract_players", file: ".\src\protocols\gamespy\protocols\one\protocol.rs", line: 132 }
Steps To Reproduce
Use the
master_querant
example to query this server:51.81.48.224
.Command:
cargo r --example master_querant bf1942 51.81.48.224
Expected behavior
Clean response output.
Additional context
Printing
player_data
(the hashmap where it gets its values), it seems that it does not contain theplayername
key (also note that node also usesname
andplayer
for this, neither these are present, so this might be a parsing issue?).The text was updated successfully, but these errors were encountered: