Luigi Auriemma

I also figured that out now by myself. Its really simple. Old style was:

now because there are still servers which usese old 3.0.4 protocol so you have to do this

remember that if you use the new query with the 3.0.4 servers they crash (http://aluigi.org/adv/aa3blah-adv.txt), so use the old one first :)

Thanks so much, and yeah I already figured everything out. I spend too much hours yesterday with all those bits and bytes and didn't get it to work. Then after sleeping some hours and trying it again today, it worked after a few minutes :) Guess I was simply to tired yesterday and my brain was overloaded.

Anyway ... everything seems to work now on my end. Thanks sooo much for your help!



OOOPPS ... good that you remember me ... guess I crashed a few empty servers then a few times :-(

They should upgrade anyway to the new version then because player clients update automaticly anyway. But yeah ... we should not crash them ;)

Have they fixed this bug in 3.0.5 already?

Last but not least ... do you now from where I could grab a serverlist (IP / QueryPort) only with the latest version, that use the *new* query protocol? That stuff on https://api.getgsc.com is giving me a full list I guess? Can I filter it? Then I would use that list every few hours to keep my list up to date ... until I found out a better solution ...

yeah that bug has been fixed in 3.0.5 but remain other 7 vulnerabilities open.

about getgsc, I'm not aware of server side parameters for retrieving the info or filtering the servers, indeed the gsc2.0 tool queries each single server (aa3 is not in the gsc2.0 list although supported by api.getgsc.com) and filters them in this way, so client side.

The only, not so nice solution, which i figured out, is, to make first an old style 3.0.4 query, if you get 27 Bytes back then you know it's one of the new servers.
Btw, the same here, i probably crashed some of the old version server, but not for purpose.
And last, but not least, i wanna say thank you for the support.