Parser please.

[LinktheDeme]

Love you long time :D

[divisortheory]

Hey divisortheory or anybody writing parsers, I am writing my own just for myself right now, and I pretty much guessed what all the fields in each line are for except for the one right after the line number basically, my guess is that it is the time since the previous line since there isn't any other "time" info field. Is that correct?

Now that I figured out how to read the chat log in real time on my own without the help of LogMon, I think I can answer this. Chat Log header is a string that looks like this (example):

c8,00,00,ff5020ff,00000000,00000000,001d,00,01,00, 00,....

Field 1 (c8) - Chat Code
Field 2 (00) - Don't know
Field 3 (00) - Don't know
Field 4 (ff5020ff) - RGB color of text
Field 5 (00000000) - Line Number
Field 6 (00000000) - Conversation Thread
Field 7 (001d) - Length of message
Field 8 (00) - Don't know
Field 9 (00) - Dont' know
Field 10 (00) - Not quite sure. It's always 01 for LS chat though.
Field 11 (00) - Something related to multiline messages.

Seems the field you were asking about was Field 7. It's not very useful though, and it isn't consistent either. For single line messages, it seems to always contain the number of bytes starting after the 4th period above, and ending one byte after the null terminator for the string. For multi-line messages though, I can't really figure it out. I just ignore this field.

[genome]

Hey divisortheory or anybody writing parsers, I am writing my own just for myself right now, and I pretty much guessed what all the fields in each line are for except for the one right after the line number basically, my guess is that it is the time since the previous line since there isn't any other "time" info field. Is that correct?

Now that I figured out how to read the chat log in real time on my own without the help of LogMon, I think I can answer this. Chat Log header is a string that looks like this (example):

c8,00,00,ff5020ff,00000000,00000000,001d,00,01,00, 00,....

Field 1 (c8) - Chat Code
Field 2 (00) - Don't know
Field 3 (00) - Don't know
Field 4 (ff5020ff) - RGB color of text
Field 5 (00000000) - Line Number
Field 6 (00000000) - Conversation Thread
Field 7 (001d) - Length of message
Field 8 (00) - Don't know
Field 9 (00) - Dont' know
Field 10 (00) - Not quite sure. It's always 01 for LS chat though.
Field 11 (00) - Something related to multiline messages.

Seems the field you were asking about was Field 7. It's not very useful though, and it isn't consistent either. For single line messages, it seems to always contain the number of bytes starting after the 4th period above, and ending one byte after the null terminator for the string. For multi-line messages though, I can't really figure it out. I just ignore this field.

Thanks, yeah basically I got just a few more figured out since then, they are pretty easy to guess. Did you look into the initial binary bytes at the start of each file? I just filter them out but there's quite a bit there and they might be useful too. And there's a few more binary bytes at the start and end of each line that also seem to be related to the line type, I ignore most of them, except the ones in the middle that color items and key items, and I don't need the other ones, but they could still be useful if we knew what they were for.

[divisortheory]

No idea what a log file looks like at all, I'm only looking dierctly at the memory of the pol process. That being said, there's some interesting stuff like total number of bytes in the chat log, total number of lines, etc in the memory. Haven't figured out much of anything else though. There are 4 bytes between the end of the string header (i.e. the string of number fields separated by commas), and the first character of the actual message. Those have me really curious, but I haven't figured out what they're for yet.

[genome]

No idea what a log file looks like at all, I'm only looking dierctly at the memory of the pol process. That being said, there's some interesting stuff like total number of bytes in the chat log, total number of lines, etc in the memory. Haven't figured out much of anything else though. There are 4 bytes between the end of the string header (i.e. the string of number fields separated by commas), and the first character of the actual message. Those have me really curious, but I haven't figured out what they're for yet.

Yeah I noticed those, and they are variable lenght too, not always four, sometimes 5-6 too. It's usually 1E-01-1E-01 but sometimes it changes. One of the times it's 5 bits is when a line continues from the previous one.

If you are reading everything in real time from memory instead of from the temp files like I am, you have no problem adding your own timestamps then, which is pretty nice.

[Moggy]

is it possible to run a parser from another computer? can i set path directory through network?

[TsingTao]

From page 3...

The parser that Taz has posted doesn't even need to run on the same computer that you're running ffxi on. It just needs to know where the files are. E.g. you mount the disk that the log files are on remotely, and you can run the parser from a 2nd computer.

[Sonomaa]

mentioned this earlier in the thread but I think people are still looking for it

if your looking for a chat parser, Yarnball covers that base http://ragnhild.sonomaa.com/yarnball/

yes its safe, Im hosting it and use it myself

[TB]

Newest version of FFXIP doesn't even start for me when i wanna run the .exe. Do I need to have any Windows bonus stuff installed or so?

Running german WIN XP Pro with SP2.

[Khamsin]

The only person who knows how to actually timestamp the logs you see on your screen is Cliff from Windower, and it's never been released.

It was released, briefly, then was recalled. Though that doesn't mean people actually deleted it, if they had it.

[TsingTao]

Newest version of FFXIP doesn't even start for me when i wanna run the .exe. Do I need to have any Windows bonus stuff installed or so?

Running german WIN XP Pro with SP2.

Check the Windower forum thread for help.