u/Wobblucy

Can find the release here:

https://github.com/Wobblucy/AwowlabOverlay/releases/tag/v0.1.0

How it works:

1. first pass over your logs looks for encounter or challenge mode "segments" and simply takes the offset into the combat log.
2. Once you select the a segment it actually parses the data down.

Basically trading a little bit of responsiveness for consuming less memory.

Full disclosure on the limitations:

1. the combat log is only written to at the end of boss combat so you cant get mid pull statistics from this tool. m+ logs are written ~every 2 minutes during trash.
2. You have to be advanced logging locally for it to work.
3. the thread priority is set intentionally low to prevent any possible performance interference with the game, parsing is fast (sub 1s generally) but it will take a backseat to your other processes.
4. Window only currently. This is a breakout of a much larger project relying on build targets so it isn't a separate project. It might run on linux (awowlab does on proton apparently) but it is not something I plan on supporting currently.
5. I'm not paying 200$ a year for code signing, if you are not comfortable with "run anyways" feel free to build from source.
6. IMGUI + GLFW as the current front end for Awowlab means making it pretty is hard. Maybe one day I swap that for something more appealing, but it would be substantial work, and today is not that day.

Some bonus features I missed from Details:

1. Boss phases - you have to set these manually but the list builds from enemy spell casts, emotes, or you can use raw time to split.
2. Mob weighting - lets you remove the "garbage" mobs from the meters so you can see who is padding vs who is actually moving your dungeon forward.

https://imgur.com/a/WFV0ZU4

PS: To the devs out there:

Happy to take issue and pull requests under consideration, but this is also a side module of a hobby project that is generally worked on like 2 hours a week, don't expect fast responses :)

Open to any feedback, can just dump it here.