If you want the same events as in hlsw here's how I parse the received 
data in my C# application.
http://pastebin.com/m5a37b88

You can also just output the Text in the AnalysePacket function

Hope it's useful ;)

-Chris

On 01/02/2010 5:43 AM, Robin Beismann wrote:
> [email protected] schrieb:
>    
>> Send hlds_apps mailing list submissions to
>>      [email protected]
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>      http://list.valvesoftware.com/mailman/listinfo/hlds_apps
>> or, via email, send a message with subject or body 'help' to
>>      [email protected]
>>
>> You can reach the person managing the list at
>>      [email protected]
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of hlds_apps digest..."
>>
>>
>> Today's Topics:
>>
>>     1. logaddress_add packet format (Kyle Rush)
>>     2. Re: logaddress_add packet format (Andrew Collins)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Sun, 31 Jan 2010 12:46:53 -0500
>> From: Kyle Rush<[email protected]>
>> Subject: [hlds_apps] logaddress_add packet format
>> To: [email protected]
>> Message-ID:
>>      <[email protected]>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> Hi all,
>> I'm not sure if this is the proper place to pose this question, so I
>> apologize if I'm wrong. I'm trying to develop a tool in Java with similar
>> functionality to that of HLSW, with a goal of stripping out some of the
>> features my admin community and I do not use. I've established an RCON
>> connection with the server, and sending commands and receiving the responses
>> works as per the RCON packet info on the Valve developer wiki. That works
>> perfectly fine as I would like it to.
>>
>> What I'm having difficulty with is understanding what goes on after the
>> "logaddress_add IP:PORT" command is run via RCON on the server. I've tried
>> to run a packet capture/scanner tool to see what kind of information HLSW is
>> receiving during normal operation, but I saw nothing that could be
>> understood as the console and chat log. Perhaps the log is sent in a
>> non-ascii format? I did find massive packets containing the state of all the
>> CVARs, so perhaps I didn't look thoroughly enough, but I don't think its in
>> there. I've tried looking through the Valve wiki but I didn't find anything
>> that seemed to be related to the interpretation of the remote log packets,
>> or even how to identify which packets contain that data. I'd really
>> appreciate if anyone has any input on how to work this out, this console log
>> reading is fairly key to my application's functionality. I've managed to
>> work around this for now by using FTP to download the logs in the
>> background, but its rather inefficient having to download the whole log file
>> to get just the most recent few lines.
>>
>> Any help on this issue is sincerely appreciated.
>>
>> Kyle Rush
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Sun, 31 Jan 2010 18:00:11 +0000
>> From: Andrew Collins<[email protected]>
>> Subject: Re: [hlds_apps] logaddress_add packet format
>> To: Half-Life dedicated server applications mailing list
>>      <[email protected]>
>> Message-ID:<[email protected]>
>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>
>> Creating a clone because the original has too much functionality...
>> interesting... :o
>>
>> IIRC, once you send the logaddress command, the server will simply send
>> data to the given PORT via UDP and just expect you will catch it. So you
>> will need to setup a listen process to grab that data.
>>
>> On 31/01/2010 17:46, Kyle Rush wrote:
>>
>>      
>>> Hi all,
>>> I'm not sure if this is the proper place to pose this question, so I
>>> apologize if I'm wrong. I'm trying to develop a tool in Java with similar
>>> functionality to that of HLSW, with a goal of stripping out some of the
>>> features my admin community and I do not use. I've established an RCON
>>> connection with the server, and sending commands and receiving the responses
>>> works as per the RCON packet info on the Valve developer wiki. That works
>>> perfectly fine as I would like it to.
>>>
>>> What I'm having difficulty with is understanding what goes on after the
>>> "logaddress_add IP:PORT" command is run via RCON on the server. I've tried
>>> to run a packet capture/scanner tool to see what kind of information HLSW is
>>> receiving during normal operation, but I saw nothing that could be
>>> understood as the console and chat log. Perhaps the log is sent in a
>>> non-ascii format? I did find massive packets containing the state of all the
>>> CVARs, so perhaps I didn't look thoroughly enough, but I don't think its in
>>> there. I've tried looking through the Valve wiki but I didn't find anything
>>> that seemed to be related to the interpretation of the remote log packets,
>>> or even how to identify which packets contain that data. I'd really
>>> appreciate if anyone has any input on how to work this out, this console log
>>> reading is fairly key to my application's functionality. I've managed to
>>> work around this for now by using FTP to download the logs in the
>>> background, but its rather inefficient having to download the whole log file
>>> to get just the most recent few lines.
>>>
>>> Any help on this issue is sincerely appreciated.
>>>
>>> Kyle Rush
>>> _______________________________________________
>>> hlds_apps mailing list
>>> [email protected]
>>> http://list.valvesoftware.com/mailman/listinfo/hlds_apps
>>>
>>>
>>>        
>>
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> hlds_apps mailing list
>> [email protected]
>> http://list.valvesoftware.com/mailman/listinfo/hlds_apps
>>
>>
>> End of hlds_apps Digest, Vol 7, Issue 1
>> ***************************************
>>
>>      
> It's not just sending 'Data' to the address,
> it sends the Log which also appears in the server's console.
> - Robin
>
>
> _______________________________________________
> hlds_apps mailing list
> [email protected]
> http://list.valvesoftware.com/mailman/listinfo/hlds_apps
>    

_______________________________________________
hlds_apps mailing list
[email protected]
http://list.valvesoftware.com/mailman/listinfo/hlds_apps

Reply via email to