Broker: MidnightEvents

v0.6.3-beta (2026-05-23)

Full Changelog Previous Releases

• fix(toc): SavedVariables line stripped from release builds — restore correctness
  The hygiene commit (2459125) put inline #@debug@ markers into the
  SavedVariables TOC line:
  ## SavedVariables: Broker_MidnightEventsDB#@debug@ Broker_MidnightEventsHarvest Broker_MidnightEventsQuestCatalogue#@end-debug@
  That was wrong on TWO fronts:
  * Release builds via the BigWigs packager: the packager interpreted
  the inline marker as "strip this whole line." The v0.6.2-beta zip
  has NO SavedVariables directive at all. Every CurseForge/Wago
  install since the bad commit declares zero SavedVariables, so
  Broker_MidnightEventsDB cannot persist across /reload — addon
  settings, alts data, bountifulSeen, voidforge cache, liadrinChoice
  all reset on every reload.
  * Raw dev source loaded directly by WoW: WoW's TOC parser treats the
  # in #@debug@ as breaking the token. Same effect — DB isn't
  declared, isn't persisted. (Broker_MidnightEventsHarvest IS still
  declared by accident as the middle whitespace-separated token,
  which is why DevHarvest data continued to land on disk while DB
  state quietly vanished on every reload.)
  Fix: collapse back to a single clean SavedVariables line declaring all
  three names unconditionally. Release builds will have empty
  Broker_MidnightEventsHarvest / Broker_MidnightEventsQuestCatalogue
  tables in user SV files (because DevHarvest.lua is still stripped via
  the block-level #@debug@ markers around its TOC line, which DO work
  correctly when on their own lines) — that's ~50 bytes of empty SV
  pollution per install, which is the right tradeoff for the correctness
  gain.
  Block-level #@debug@ markers (the DevHarvest.lua wrapper) remain in
  place and are handled correctly by both WoW's parser (file-level
  content) and the packager.
  Severity note: this hotfix recovers persistence going forward but
  cannot recover the ~7 days of lost DB state. Affected users will see
  their addon "start fresh" after the next /reload following v0.6.3-beta;
  the Voidforge cache will repopulate after their next Decimus visit per
  character, bountifulSeen will repopulate on first delve scan after
  daily reset, and alts data will accumulate as each char logs in.