Jump to content

Recommended Posts

Hello,

 

Since the last update It seems that Arma broke the current standard implementation of Source query. Query for Rules of the servers aren't reported correctly anymore :

 

https://developer.valvesoftware.com/wiki/Server_queries#A2S_RULES

 

87e02694-e3ad-11e5-8426-4495d1f49f58.JPG

 

We can't process mod launched or signatures installed.

 

If you can do something about that, would be great.

 

this is incorrectly reported in rpt too :

2016/03/07, 5:01:12 encodedStream: ꯊaÊšµ¹œZGâË@
CUP Weapons 1.5õ
>CUP Vehicles - 1.2^øsCUP Units 1.2.2?‘¡ºCUP Terrains - Full 1.0.1k^È(Community Base Addons v2.3.0a3asdg_jointrailscba_2.3.0.160217-c478cf23cup_terrains_core-1.0.1cup_terrains_maps-1.0.1cup_units-1.2.2cup_vehicles-1.2.0cup_weapons-1.5.0DragonFyre25dragonfyreeden1ROJ    shay_gmanteam_trankilou    [TF]Nkey8
2016/03/07, 5:01:12 parts size:4)
2016/03/07, 5:01:12 part(127): ꯊaÊšµ¹œZGâË@
CUP Weapons 1.5õ
>CUP Vehicles - 1.2^øsCUP Units 1.2.2?‘¡ºCUP Terrains - Full
2016/03/07, 5:01:12 part(127): 1.0.1k^È(Community Base Addons v2.3.0a3asdg_jointrailscba_2.3.0.160217-c478cf23cup_terrains_core-1.0.1cup_terrains_m
2016/03/07, 5:01:12 part(127): aps-1.0.1cup_units-1.2.2cup_vehicles-1.2.0cup_weapons-1.5.0DragonFyre25dragonfyreeden1ROJ    shay_gmanteam_trankilou    [TF]N
2016/03/07, 5:01:12 part(4): key8
2016/03/07, 5:01:13 Connected to Steam servers

Share this post


Link to post
Share on other sites

BIS changed how server query works, so they could include extra info like steam workshop id.
There is no documentation for this.
If we are luckly BIS might document for Eden, but there is no offical plans etc  :(

---------------

https://forums.bistudio.com/topic/188304-has-anyone-got-a-working-arma3-server-query/

This is also prob the reason why PlayWithSix released there server deamon tool i.e 

https://forums.bistudio.com/topic/188490-withsix-gsd-game-server-daemon-released/

Share this post


Link to post
Share on other sites

I am confused as to why they didn't just append the extra rules they needed to the output.  The protocol is built to handle a lot of response data coming back from the server.  It can even do split packets if the response is getting too large.  Regardless they have strayed away from the A2S (Source) protocol which is unfortunate.  OP has an issue open here https://github.com/Austinb/GameQ/issues/299 in case anyone wants to come and update if/when they fix the issue or publish some kind of reference.  Until then I will be unable to update the library to support rules response from Arma3. I am the main maintainer for the project.

Share this post


Link to post
Share on other sites

BIS changed how server query works, so they could include extra info like steam workshop id.

 

 

How do you even know that if it's not documented ? If someone from BIS can simply explain what's happening here...

Share this post


Link to post
Share on other sites

Capture the response packets and attempt to reverse engineer it.
You will see the workshop id & shorthash for each mod is in the server response (reverse checksums).

 

The real issue is the the shorthash seems to vary in number of bytes.
Its slightly confusing and i am not sure exactly what BIS is doing here.
Realistic need to know this, so you can parse the server response correctly.

This info was added so the arma3 launcher could link the server mods to steamworkshop id.
Otherwise the launcher would be able to automatically download steamshop mods when joining a server.

If you want to query BIS, you bestoff to ask Dwarden via Skype/Discord.
But you won't get anymore info.

Share this post


Link to post
Share on other sites

The pointed issue here is the response does not comply anymore with ServerQuery standard, not that they added some data to it, we cannot read the data as it should be according to SourceQuery rules.

Share this post


Link to post
Share on other sites

The pointed issue here is the response does not comply anymore with ServerQuery standard, not that they added some data to it, we cannot read the data as it should be according to SourceQuery rules.

You asked me how i knew if it was documented so i answered :)

I already told you they changed the server query response, so it no longer follows SourceQuery rules 100%.

I also mentioned you how you can try to bug Dwarden for more info via Skype/Discord.

But he was already bugged this week or last week and there are no plans yet to document it yet.

So we are stuck till whenever/if BIS decides to document the changes

Unless you manage to reverse engineer the query response & figure out how the shorthash+steamID is encoded.

anyway gl

.

 

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×