Altitude Chat Parser

Aki1024 · #1 10-29-2011, 10:26 PM

This is a simple app that can read the log file for Altitude into a quicker to read format that separates out convos into separate channels. As I wanted a convo from my chat logs, and knew that the server's all and team chat would be in the log file as well, I decided to create a parser to quickly grab just the text I wanted to see.

App link v1.1
App link v1.2
Source link (to version 1.1)

version 1.2
-Interal parsed storage of logs rewritten to be more maluable.
-Via server parsing, Unknown players get identified by both their server leave messages in addition to the already grabbed entry message. If the log identifies them at any time, they will be identified in the parser now (woot!)
-Via ctrl clicking, multiple channels can be selected. This will be valueable on the server parser when teams are added to the logs, as you will then be able to select which set of information you want to see (all of the server, pov of a player via their team+all chat, etc)
--When multi selecting, the front of the line is the channel. This is the port number followed by the team number (27303:3)
--Team selection is defaulting to zero. I will update the app on the next Altitude patch to take advantage of newly available info
(Thank you Lamster!)
-Ctrl+a now works to select all from either channels or the channel's text
-Selecting a file via browse now also activates a parse run. 33.3% less clicking!
Known Bug: Attempting to parse a local file while in game will lock up the app, requiring it to be restarted. I could potentially spot this error, copy the file, then access the new temp file. Not sure yet if I want to go on this path.

Version 1.1
-Parser now parses both Client side logs and Server side logs for convos.
-Attached "Unexpected Lines.txt" is what appears to be an odd bug related to people talking that results in the ": " getting replaced by a odd string. The parser parses these lines correctly regardless, but marks them under "Debug: Error".

(thank you to the mod that got rid of my fail post ^.^ )

Boko · #2 10-30-2011, 02:27 AM

Is this for the server logs or for your own chatlog?

Aki1024 · #3 10-30-2011, 07:59 AM

By "server's chat" I mean what is said by players to a room. This is a chat log viewer that can only see what you saw in game via chat_log.txt.

Edit: Also my 100th post. I'm now a Senior Member. ^.^

GGQ · #4 10-31-2011, 12:19 AM

If you guys want to get infractions for insulting other members and posting stupid meme pics, at least don't trash a thread with such a nice OP.

Aki1024 · #5 11-20-2011, 10:08 AM

Parser update to handle both client side and server side logs. If sessionStart is not found, it displays time since the server started. Otherwise it displays time of message.

Quote:

This log didn't have a sessionStart. Displaying time since server start.
4d 18h 27m UKNPLR# 12: aww
4d 18h 27m UKNPLR# 3: lol
4d 18h 27m UKNPLR# 12: why mnot
4d 18h 27m UKNPLR# 12: xD

UKNPLR# occurs if the log didn't see that player join the server.

Quote:

4d 22h 57m Player Joins (3): ZomPlayer (10:60) 127.0.0.1:27272 00000000-0000-0000-0000-000000000000
4d 22h 58m Player Leaves (7): DiffPlayer 127.0.0.1:27272 00000000-0000-0000-0000-000000000000 Reason: Client left., Message: left
4d 23h 6m Map Change: ball_darkwar

A player by the name of ZomPlayer joined the server and was assigned the playerID of 3. They are ace 10, level 60 at the given ip and having the given vaporID. When a player leaves the server, their ID is also used. This can be used to track down who an UKNPLR is above.

Quote:

Server started 11/19/2011 9:53:37 AM
11/19/2011 9:57:21 Zeus: aww
11/19/2011 9:57:21 Tidus: lol
11/19/2011 9:57:21 Link: why mnot
11/19/2011 9:57:21 Link: xD

Example of when sessionStart is seen.

Aki1024 · #6 05-26-2012, 10:48 AM

Updated in preparation of having team chat information available from server logs. Many improvements.

version 1.2
-Interal parsed storage of logs rewritten to be more maluable.
-Via server parsing, Unknown players get identified by both their server leave messages in addition to the already grabbed entry message. If the log identifies them at any time, they will be identified in the parser now (woot!)
-Via ctrl clicking, multiple channels can be selected. This will be valueable on the server parser when teams are added to the logs, as you will then be able to select which set of information you want to see (all of the server, pov of a player via their team+all chat, etc)
--When multi selecting, the front of the line is the channel. This is the port number followed by the team number (27303:3)
--Team selection is defaulting to zero. I will update the app on the next Altitude patch to take advantage of newly available info
(Thank you Lamster!)
-Ctrl+a now works to select all from either channels or the channel's text
-Selecting a file via browse now also activates a parse run. 33.3% less clicking!

RedLight · #7 05-26-2012, 05:41 PM

Peeked at the source, and realized it's on BitBucket. Ever thought of using GitHub instead? Maybe if I get the time I could write a quick Mac implementation of this app, and we could merge repos.

On a second thought, I doubt I would have enough time to make it, seeing that I'm trying to manage the creation of three apps at the same time right now.

Aki1024 · #8 05-28-2012, 06:06 AM

I was asked by someone in a pm when I first released it why I didn't develop on a multi OS language. I figured the number of users this would have didn't justify me trying to use a language that I couldn't develop within quickly. I get paid in C#, and as such I know it the best.

As for BB vs GH, I started on GH and found that I prefer the way BB handles both its pulls/gets and bug tracker. If you are interested in making this app available for more users, excellent. If you find you are working on too many projects already, no worries.