raidlogscan

Features

Parses raidlogs from warcraftlogs.com and generates leaderboards of who everyone played with the most.
Allows grouping multiple characters per human player, across servers too.
Can scan all raids published under a guild / raid team on Warcraftlogs.
Allows logging into a personal Warcraft Logs Account using oauth2, and then scanning personal logs as well as recent character logs.
Fully deployed as Cloud Functions to Google Cloud, making it very cheap to run.
Using Firebase/Datastore as database, and Pub/Sub for events and triggers.
Written in Go 1.16.
MIT license.

Implementation

Data model

A report entity stores the details for a single scanned raid report, including all of its players that participated.

A player entity stores the details for a player character that appeared in at least one report. It also stores all the reports it appeared in, all the other players ("coraiders") and the number of times ("count") it raided with them in those reports. Further, it also stores mappings from coraider player IDs to account names that group them.

Data flow

A list of report codes to scan is generated in one of three ways:

An input guild ID of a raid team to be scanned.
An input user ID of a Warcraftlogs account for which public personal logs should be scanned.
An input character ID for a list of recent reports to be scanned.

For each report code, the list of players in that report is fetched and stored in a report entity in the database. For each participating player, an event is emitted to update (or create) the respective player entity for this report. This will:

Insert the report into the list of reports the player participated in.
Update the coraiders and their appearance counts.
If the player is claimed by an account name, send "coraider account claim" events to all newly appeared coraiders.

A coraider account claim event then results in the targeted player entity's mapping from known coraider player IDs to account names to be updated. This denormalization allows us to fetch details for account names on a per player basis without having to store separate entities for accounts themselves.

Identifiers