BazBars

057 (2026-05-08)

Full Changelog Previous Releases

• v057: per-character button payloads
  Bar STRUCTURE (count, size, position, scale, keybind shape, chrome
  settings) stays in the profile. Bar PAYLOADS (the spell/macro/item
  slotted into each button) move to a per-character / per-profile
  bucket so sharing a profile across characters of different classes
  doesn't drag the first character's abilities onto the second's bars.
  Storage moves from
  profile.bars[id].buttons["r:c"] -- shared, the bug
  to
  BazBarsDB.charButtons[charKey][profileName][id]["r:c"]
  Button.lua's SaveButton/LoadButton route reads + writes through
  addon:GetButtonPayload / SetButtonPayload. ExportBar bakes in the
  current character's payloads; ImportBar applies imported payloads
  to the current character only. DuplicateBar mirrors source-bar
  payloads onto the new bar's per-char bucket. DeleteBar wipes the
  current character's payload for the deleted bar.
  Migration is one-shot per profile (sentinel: profile._bbCharButtons-
  Migrated). The first character to log in after the update copies
  profile.bars[*].buttons -> charButtons[ck][pn][id] and clears the
  shared field. Other characters then start with empty bars and slot
  independently - which is the desired behavior.