EarlyPull

v2.8.2-rc1 (2026-05-13)

Full Changelog Previous Releases

• Clear pullContext on ENCOUNTER_END so quick re-pulls record
  A user reported lots of [Unknown] entries during wipe-fest sessions.
  Root cause: the v2.7.1 phase-event guard in ENCOUNTER_START matched
  against the previous pull's encounterID and pullTime, so any new
  pull on the same boss within 60 seconds of the last pull start was
  silently treated as a duplicate phase event and dropped — no banner,
  no record.
  That's correct mid-encounter (Blizzard does re-fire ENCOUNTER_START
  for phase bars) but wrong for the wipe → repull cycle. Quick wipes
  under 60 seconds were causing every subsequent pull to vanish.
  Fix: register ENCOUNTER_END and clear pullContext on it. Both wipes
  and kills fire it, so the next ENCOUNTER_START sees a clean slate
  and goes through normal resolution. Phase-event dedup still works
  inside an active encounter because ENCOUNTER_END hasn't fired yet.
  Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com