DirtSand does actually have a "commdebug" feature (type "commdebug on" in the DS console), however, that only gives the actual bytes being sent and received with no further interpretation. It's not the prettiest thing, but it could probably help in debugging server-side issues (for which I have used it before -- hence its existence). However, for the most part, I think the client-side network debugging is probably enough, simply because it will still log the same data as the server (assuming no catastrophic low-level communication issues, which I think have all been worked out now). The only catch is that you will only get the messages from one client, but then you could connect multiple clients running plNetLog at the same time and look at their logs separately too
. The tool currently dumps everything it reads into a log file, and eventually I want plNetLog to be able to re-analyze those files too, so you can look at data that you have already captured without having to reproduce the sequence of events that created it.
Meh, thick block of text...
diafero wrote:If I run the plClient in wine, can I connect to that pipe with a native Linux application?
Not currently... Windows (named) pipes and Unix pipes are completely different creatures, and neither format crosses the platform boundary. You might, however, be able to run a Windows plNetLog.exe in wine against your wine plClient.exe