[bf1942] BF2 RCON protocol

[Forrest Thiessen]

Sorry, maybe it wasn't clear from my last post:

>This website:
>    http://bfcentral.ca/serverstatus
>has a working web-based BF2 server query tool that's prepopulated with a
>list of EA test servers.  Pull up the web page and click on the
>pull-down menu in the upper-left corner of the page to see the list.
>
I got the address of one server from looking at game setup screens in
video footage that's been published on the internet; with that and some
creative Googling, I found the website referenced above, which has a
list of 6-8 test servers and tracks how many people are playing on each.

Go to http://bfcentral.ca/serverstatus and you'll be able to see the
test servers.

--Forrest
  thiessen at cyberscapearena.com



brs at vikingmind.com wrote:

>How are you finding the BF2 servers? In ASE? What did you do to rig it up?
>Or, better yet, can you provide the ip address of the servers you are testing
>against so we can implement our tools too?
>
>Quoting Forrest Thiessen <thiessen at alum.mit.edu>:
>
>  
>
>>I've been experimenting with the game status protocol, against some of
>>EA's test servers, and have been writing a Perl module to make it easy
>>to query.
>>
>>From what I've done, I can tell you that at least the EA's test BF2
>>servers are using the "new" GameSpy protocol.  As a referesher, BF1942
>>used the "old" protocol, and BFV would respond to either the "old" or
>>"new" protocols, except that it's implementation of the "old" protocol
>>was broken if you had more than a few players on the server.
>>
>>The only odd thing about the BF2 test servers' responses to status
>>queries that I've seen is that it makes use of a hither-to unused
>>(AFAIK) feature of the protocol that allows some of the server rules
>>parameters to have null values.  Some of the older query parsers, such
>>as some written for BFV, don't seem to expect this and so get screwed up
>>when they query a BF2 server.  Note that some of the descriptions of the
>>"new" GameSpy protocol don't mention this; they also have other minor
>>errors that wouldn't show up with BFV, but could possibly show up with a
>>BF2 server, so buyer beware.
>>
>>Even though the protocol is the same, you get a LOT more data back from
>>server queries: the "rules" section of the response has gobs of
>>parameters we've never seen before, and the "players" section has all
>>kinds of new fields, like a universal player ID, rank, etc.
>>
>>The best description I've found of the "new" GameSpy protocol, used for
>>status queries by BF2, is here:
>>    http://www.int64.org/docs/gamestat-protocols/gamespy2.html
>>
>>I should have an object-oriented, reusable Perl module finished in the
>>next week or so (just doing some debugging now, in my "spare" time), and
>>it will be downloadable from:
>>    http://fun-o-matic.org
>>
>>--Forrest
>>  thiessen at cyberscapearena.com
>>
>>
>>
>>Steven Hartland wrote:
>>
>>    
>>
>>>I second that and add to it the query protocol if its changed and not
>>>using standard gamespy / ase queries.
>>>
>>>   Steve / K
>>>----- Original Message ----- From: "Brigham Stevens" <brs at vikingmind.com>
>>>
>>>
>>>      
>>>
>>>>Will you be able to release any info on the RCON protocol for BF2?
>>>>Does it support the same protocol, in terms of handshake/authentication?
>>>>It would be nice if you could release some kind of specifications on it
>>>>so we don't all have to use ethereal and figure it out like last time.
>>>>        
>>>>
>>>
>>>
>>>================================================
>>>This e.mail is private and confidential between Multiplay (UK) Ltd.
>>>and the person or entity to whom it is addressed. In the event of
>>>misdirection, the recipient is prohibited from using, copying,
>>>printing or otherwise disseminating it or any information contained in
>>>it.
>>>In the event of misdirection, illegible or incomplete transmission
>>>please telephone (023) 8024 3137
>>>or return the E.mail to postmaster at multiplay.co.uk.
>>>
>>>      
>>>
>>    
>>
>
>
>
>
>----------------------------------------------------------------
>This message was sent using IMP, the Internet Messaging Program.
>
>  
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/bf1942/attachments/20050504/3a226542/attachment.htm>