EarlyPull

v2.6.1-rc1 (2026-05-01)

Full Changelog Previous Releases

• Fix duplicate pull records when puller resolves early
  A user reported their 1-pulled bosses showing 3-4 records each. Root
  cause: the puller-resolution chain has three independent entry points
  • the immediate boss-target check at ENCOUNTER_START, the
    DAMAGE_METER_COMBAT_SESSION_UPDATED handler, and the polling loop -
    and each one that successfully resolved called RecordPull. So one
    pull would be recorded once at ENCOUNTER_START, again at +0.2s,
    again at +0.5s, etc.
    Added a ctx.recorded flag as the single "we're done" signal. Every
    resolution path checks it on entry and sets it after RecordPull
    runs. Pulls now record exactly once.
    Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com