Skip to content

v0.2.0-beta1

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 16 Nov 18:50
· 15 commits to main since this release

JimPowerMizer

v0.2.0-beta1 (2026-11-16)

Full Changelog Previous Releases

  • README: Midnight supported (beta)
    Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
  • Plan: Phase 1 done; Forever runs the midnight code as before
    Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
  • Merge branch 'main' into midnight
  • Harness: Forever also has nameplateShowFriendlyPlayers
    Seen in game on Forever 1.60.1: Hide names sets nameplateShowFriendlyPlayers,
    and there's no nameplateShowFriends. Test and comment only.
    Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
  • Plan: Midnight input and combat checks done
    Co-Authored-By: Claude Fable 5.2 noreply@anthropic.com
  • Plan: to-do for dungeons, raids and battlegrounds
    Co-Authored-By: Claude Fable 5.2 noreply@anthropic.com
  • Plan: no Midnight-only graphics settings to add
    Co-Authored-By: Claude Fable 5.2 noreply@anthropic.com
  • Plan: park ray tracing and VRS; combat writes confirmed on Midnight
    Co-Authored-By: Claude Fable 5.2 noreply@anthropic.com
  • Crafting orders windows on Midnight
    Placing orders counts as a service window; the orders filled at a crafting
    table count as the profession window (so closing it ends Crafting's grace
    period). Names are from Blizzard's API documentation and haven't been seen
    in game: the windows need the Midnight expansion.
    Co-Authored-By: Claude Fable 5.2 noreply@anthropic.com
  • Plan: Midnight fishing verified in game
    Co-Authored-By: Claude Fable 5.2 noreply@anthropic.com
  • Plan: service windows work on Midnight as they are
    Co-Authored-By: Claude Fable 5.2 noreply@anthropic.com
  • Fishing on Midnight: the Fishing channel, with a grace period
    Midnight keeps the pole in a profession slot, so the situation follows the
    Fishing channel (spell 131476, seen in game on 12.1.5; other Fishing spells
    match by name), then stays active for fishing.grace seconds (default 10) so
    looting and recasting doesn't switch back and forth. Moving ends it early.
    Forever keeps the held-pole rule; Compat:FishesByChannel() picks by interface.
    In-game test pending on both clients.
    Co-Authored-By: Claude Fable 5.2 noreply@anthropic.com
  • Plan: Midnight hide-names results
    Co-Authored-By: Claude Fable 5.2 noreply@anthropic.com
  • Merge branch 'main' into midnight
  • Hide names: friendly player nameplates on Midnight
    Midnight 12.1.5 has nameplateShowFriendlyPlayers instead of
    nameplateShowFriends (checked in game).
    Co-Authored-By: Claude Fable 5.2 noreply@anthropic.com
  • Merge branch 'main' into midnight
  • Applier: linked CVars set by the client aren't user changes
    Restoring UnitName...MinionName makes the client set the pet, guardian and
    totem name CVars too (seen on Midnight 12.1.5). Those updates were taken for
    changes by the user, so their saved originals were dropped and they stayed at
    the minion value. Updates during any of our writes are now ignored, and each
    batch sets again what a later write in it changed.
    In-game retest pending (Midnight; Forever to check).
    Co-Authored-By: Claude Fable 5.2 noreply@anthropic.com
  • Plan: record the Midnight probe results
    Co-Authored-By: Claude Fable 5.2 noreply@anthropic.com
  • TOC: load on Midnight 12.1.5 (interface 120105)
    One Mainline TOC lists both clients' interface numbers, so the same package
    loads on Forever (16001) and Midnight (120105). First step of the in-game
    Midnight probe (M5 Phase 1).
    Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
  • Harness and CI: test as both Forever and Midnight
    tests/harness.lua takes a client flavor (forever, the default, or
    midnight) that sets the mock's build, interface and project ID. Every check
    runs for both; the Forever-only ones (holding the fishing pole, the
    CharacterBanker bank type) sit in if FLAVOR == "forever" blocks. A new
    check confirms the addon sees the mocked client.
    CI runs the harness for both flavors (matrix), so the release workflow does
    too. Nothing in the addon changes yet.
    Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
  • Plan: Midnight support (M5)
    One package for Forever and Midnight, first released as 0.2.x, developed on
    the midnight branch in its own worktree. Records the rules that keep
    Forever working at every beta, and the steps from probe to v0.2.0. The
    Midnight client installed here is 12.1.5 (interface 120105).
    Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
  • Release: guard which tags may be released
    scripts/check-release-tag.sh runs before packaging:
    • stable tags (vX.Y.Z) must be on main;
    • alpha/beta tags (e.g. v0.2.0-beta1) may come from another branch, such as
      midnight, but only if all of main is merged into them, so a beta always
      carries the latest Forever fixes.
      Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
  • Release: run the CI checks before packaging
    The release workflow packaged without testing. It now runs ci.yml (lint,
    locale check, mock-API tests) first and only packages if they pass.
    Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
  • CI: run on the midnight branch, callable from other workflows
    Midnight support is developed on the midnight branch; every push there gets
    the same checks as main. workflow_call lets the release workflow run them
    before packaging.
    Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
  • link.sh: --forever / --retail
    Picks the game folder under $WOW_DIR (default: the Faugus prefix) instead
    of needing the full path, so the Midnight client's _retail_ folder can get
    its own dev copy. A path still works. Running it from another worktree
    points that game's dev copy at the worktree.
    Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
  • Dev copy next to the release install
    scripts/link.sh now links the repo as AddOns/JimPowerMizerDev and writes
    JimPowerMizerDev_Mainline.toc (git-ignored, so never packaged) from the
    release TOC with a "(dev)" title and version "dev". The game stores saved
    variables per addon folder, so the dev copy keeps its own settings. The
    release goes in AddOns/JimPowerMizer; enable one copy at a time.
    It also removes the old AddOns/JimPowerMizer link to the repo. No addon code
    changes.
    Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com