This is an EverQuest log file parser application that can scan an Everquest log file and generate fight summaries to help players analyze their gameplay.

There are 4 projects in this repository.

The LogSync project is a windows app that is used to collect and send log parses to the www.raidloot.com/logs website for sharing with group and guild members. It has just enough of a user interface to let you see basic fight info, but it's meant to be used alongside the website.

The Sample project is a console app to demonstrate some minimalist usage of the parser.

The RetroLog is DOS-like green screen based parser app. Probably more fun than useful. It just needs some MUD elements to go full meta.

The EQLogParser project is a .NET library containing parsing code without any UI. All projects in this repository use this to do their parsing.

If you would prefer not to install the LogSync application, you can use a web based version of this parser by uploading your logs directly to www.raidloot.com/logs.

Your logs will be published to your own private channel.

e.g. This is my channel: https://www.raidloot.com/channel/x

The parser currently only handles The Burning Lands (Dec 12, 2018) and newer log formats.

Although the TBL expansion vastly improved EQ logging, additional improvements could still be made. These quirks affect logging accuracy and are difficult to correct through heuristics:

• Defenses (other than riposte) are not reported on a strikethrough.
• Mobs with the same name cannot be distinguished. An ID suffix would be useful.
• Charmed mobs are not identified. Some kind of "(Charmed)" suffix would be helpful.
• Buff names, duration and wearing off are not reported.
• Pets should either automatically "/pet leader" on spawn/unsuspend or have a suffix. Adding "/who pet" might also be helpful.

When comparing to GamParse please keep these differences in mind:

• The total of all melee hits should be the same as the GamParse total but they're broken down into sub categories a little differently.
• Any melee hit that is a riposte will be listed as "riposte" rather than it's weapon skill.
• Any melee hit that is a finishing blow will be listed as "finishing" rather than it's weapon skill.
• Any melee hit that is a headshot, assasinate, decapitate, or slay undead will be listed by it's special skill rather than it's weapon skill.
• Any spell that does both DD and DoT damage is combined into a single total. GamParse will list the two parts separately on the DD/DoT tabs.
• DPS numbers are calculated as: total damage / fight duration. I believe GamParse uses: total damage / player active duration.
• This parser groups damage into 6 second intervals. This means any charts it displays will be averaged out compared to GamParse.
• This parser treats a fight as starting as soon as a hit or miss occurs. I believe GamParse may delay the starting timestamp until a player hits the mob.

At the root of the parser is the LogParser class. This class converts log lines into structured events. This class doesn't do any sort of state tracking - it is limited to handling EQ log syntax wierdness and converting it to a more useful data structure.

First it takes a log line like this:

[Fri Dec 28 16:30:41 2018] A tree snake bites Lenantik for 470 points of damage.

And converts it to a LogRawEvent like this:

public class LogRawEvent : LogEvent
{
    public string Text = "A tree snake bites Lenantik for 470 points of damage.";
    public DateTime Timestamp = DateTime.Parse("Fri Dec 28 16:30:41 2018").ToUniversalTime();
}

LogRawEvent represents the common traits every log line has: a date and a text string. This is not very useful yet but it serves as an input for further parsing. The parser is composed of over 30 individual message parsers that each handle exactly one category of log message and emit a result if successfull. In this case, the LogHitEvent parser will recognize the above message and return a new LogHitEvent event:

public class LogHitEvent : LogEvent
{
    public string Source = "A tree snake";
    public string Target = "Lenatik";
    public int Amount = 470;
    public string Type = "bites";
    public DateTime Timestamp = rawEvent.Timestamp;
}

This is better. At this point the LogHitEvent is useful for building some kind of fight information, but it we don't want to do it in the parser. That would be mixing multiple concerns in the parser class.

Instead, we hand this LogHitEvent off to the FightTracker class. The FightTracker consumes hit and other events to build out some stateful fight information. When the FightTracker detects a mob has died it emits a fight summary -- which is what most people want when they think of a log parser. These completed fight summaries can then finally be sent to some sort of UI or console output for display.

There are a few additonal tracker classes available:

The CharTracker class keeps track of who is a friend or foe. This functionality is mostly useful to the FightTracker because EQ logs don't include context to indicate if a third party is a friend or foe.

The LootTracker class keeps track of which mobs dropped what loot. This is used to collect data that can increase the accuracy of information on the raidloot.com website.

The BuffTracker class keeps track of which buffs players and pets have received.

Copyright 2022 Rumstil / raidloot.com

This project is licensed under Apache License 2.0

I can be reached at raidloot@gmail.com