Skip to content

Interacting with the Blizzard API

DonnieDice edited this page Apr 10, 2026 · 1 revision

Interacting with the Blizzard API

This page explains the practical boundary between BLU and Blizzard's WoW API.


What BLU Uses The API For

BLU uses Blizzard's API to:

  • detect gameplay events
  • read addon metadata
  • load and unload addon modules
  • play sound files and sound kits
  • interact with the WoW settings and addon environment

BLU does not ship its own external framework for these basics. It relies on the game's API and its own internal systems.


Common API Areas BLU Touches

Event Handling

BLU listens for WoW events tied to supported gameplay moments, such as:

  • level changes
  • quest events
  • achievement updates
  • reputation gains
  • Retail-specific system events

Sound Playback

BLU uses WoW sound playback functions to:

  • play Blizzard sound kits
  • play addon file paths under Interface\AddOns\
  • test custom and external sound files

Addon Metadata

BLU reads addon metadata to:

  • get version information
  • detect addon names and compatibility data
  • help identify some external sound pack sources

Practical Guidance For Addon Authors

If your addon wants to work with BLU:

  • keep your sound files under Interface\AddOns\YourAddon\...
  • use valid WoW-readable addon file paths
  • register simple packs with BLU:RegisterExternalSoundPack(...)
  • register full BLU-compatible 3-variant packs with BLU:RegisterSoundPack(...)

See BLU Sound Pack Guide for concrete examples.


Keep In Mind

  • WoW API behavior can change between major patches.
  • Retail-only systems should not be assumed to exist in Classic.
  • Some BLU integrations are intentionally defensive so unsupported or missing addons do not break the UI.