Skip to content

Define problem space: game raid/loot data collection pipeline #13

Description

@avandenberghe

Description

Before building a solution, fully map out the problem space for getting game raid/loot data into bbDKP.

Existing assets

  • MizusRaidTracker (WoW addon, last updated 2019/BfA 8.1) — modern boss detection, external API, EPGP, 8 export formats
  • luaRaidTracker (WoW addon, last updated 2013/MoP 5.4) — 13 export formats, wipe tracking, instance info, party/BG/arena tracking
  • Both produce EQdkp-Plus XML via copy-paste. Neither has direct bbDKP integration.

Open questions

  • Which games beyond WoW need loot/raid data tracking?
  • Who are the target users — guild officers, raid leaders, individuals?
  • What does the ideal data flow look like (in-game → bbDKP)?
  • Are there other data sources besides in-game addons (e.g. Warcraft Logs, game APIs, combat log files)?
  • What data points are essential vs nice-to-have?
  • What are the current pain points with the copy-paste XML workflow?
  • Should this support Classic, Retail, or both?
  • Is real-time data flow needed or is post-raid batch import sufficient?

Goal

Produce a clear requirements document before committing to a technical approach (addon merge, new addon, companion app, API integration, etc.)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions