KeyUI

v4.3.1 (2026-10-21)

Full Changelog Previous Releases

• feat: support WoW Forever
  Forever (1.60.1, interface 16001) plays in classic Azeroth but runs the
  Mainline client: the 12.1.5 API with secret values, the Mainline templates
  and atlases, and none of the legacy spell globals. Its build number fell in
  the isVanilla range, so KeyUI would have taken the Classic Era paths there:
  bundled BLPs instead of atlases, no ActionButtonSpellFXTemplate, no combat
  lock on action changes and no BINDINGS_LOADED.
  VersionCompat gains isForever and isModern (Retail or Forever). Everything
  that follows the client rather than the game now checks isModern, and
  USE_ATLAS follows it. Retail and the Classic clients keep their flags. The
  combat-lock message no longer says "on Retail".
  Checked against the 1.60.1.70450 dump; no Forever client was available to
  test in-game. COMPATIBILITY.md documents the new snapshot layout and re-runs
  the API audit against all five clients.
  Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
• chore: pull API snapshots from wow-ui-source and watch for new builds
  API/ held hand-made client exports named after their build, so every bump
  meant re-exporting four clients and rewriting the paths in COMPATIBILITY.md.
  tools/update-api.sh now fetches the Interface/AddOns tree of the matching
  Gethe/wow-ui-source branch into API/<flavor>/, plus the atlas, global API
  and template lists from Ketho/BlizzardInterfaceResources, which stand in for
  the Helix folder wow-ui-source does not carry. Before it replaces a snapshot
  it lists which API documentation files changed.
  check compares each branch's version.txt with the Interface line of
  KeyUI.toc. The API Watch workflow runs it every Monday and opens one issue
  per interface version the TOC does not list yet.
  Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com