Repository navigation
Releases
Releases · Vampyrbyte/JimPowerMizer
v0.2.0-beta2
JimPowerMizer
v0.2.0-beta2 (2026-11-16)
Full Changelog Previous Releases
- Merge branch 'main' into midnight
- Plan: energy savings tested; v0.1.5 and v0.2.0-beta2
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Merge branch 'main' into midnight
Conflicts:
.luacheckrc
- Plan, README: energy savings built; in-game test next
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Energy savings: time per graphics profile, energy from the watts you enter
Records how long each graphics profile is applied (account-wide). With
your PC's watts at your own settings and per profile entered on the new
Savings tab, /jpm stats and the switch message show the energy saved,
plus cost and CO2 if a price and factor are entered. Nothing is shown
for figures that aren't entered. Deleted profiles count in the totals
but a new profile with the same name starts from zero.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Plan: background FPS limit noted in the help text, not detected
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Plan: deleted profiles' savings; background detection question
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Plan: energy savings per profile (next 0.1.x)
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Merge branch 'main' into midnight
- Plan: M6 Phase 0 progress
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Merge branch 'main' into midnight
- Release: label uploads only with the packaged TOCs' game versions
The packager labels an upload with the game versions of every TOC in the
repo, even one .pkgmeta leaves out. scripts/package-args.sh passes -g with
the packaged TOCs' versions when a TOC is left out (the classic branch,
until 0.2.0 is stable); otherwise nothing, so main and midnight releases are
unchanged. Dry runs: classic -> 1.15.9 only; midnight -> 12.1.5, 1.60.1.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Merge branch 'main' into midnight
- Release: tag guard rules for the 0.3 betas
A 0.3 pre-release must include all of main and midnight, and while 0.2 isn't
stable its .pkgmeta must leave out the Mainline TOC (Classic clients only).
The release workflow fetches every branch for the check. Tested in a scratch
clone: stable, 0.2 and 0.3 cases, missing merges, deleted midnight.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - CI: test the client flavors each branch lists in tests/flavors
Each branch lists the clients it supports, so ci.yml stays the same on
every branch (no merge conflicts) while classic adds its own flavors. The
harness loads the TOC each flavor's client reads. CI also runs on classic.
Tests and CI only; not packaged.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - link.sh: a dev TOC per release TOC; --classic-era
For each JimPowerMizer_.toc it writes JimPowerMizerDev_.toc
(the Classic TOC comes with M6), and removes dev TOCs whose release TOC is
gone. Dev tooling only; not packaged.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Merge branch 'main' into midnight
- Plan: run the 0.2 and 0.3 betas side by side
Each beta line gets its own clients until 0.2.0 is stable: 0.3 packages
leave out the Mainline TOC, so they're labelled for Classic only.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Merge branch 'main' into midnight
- Docs: kept on main only; Classic clients to support
Brings the Midnight progress notes and README from midnight, so main holds
the complete docs from now on. M6: every Classic client Blizzard runs (Era
incl. SoD and Hardcore, TBC Anniversary, Mists Classic).
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Merge branch 'main' into midnight
Conflicts:
docs/PLAN.md
- Plan: Classic support (M6, 0.3.x)
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Plan: v0.2.0-beta1 released
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
v0.2.0-beta1
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 inif 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
v0.1.5
JimPowerMizer
v0.1.5 (2026-11-16)
Full Changelog Previous Releases
- Plan: energy savings tested; v0.1.5 and v0.2.0-beta2
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Plan, README: energy savings built; in-game test next
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Energy savings: time per graphics profile, energy from the watts you enter
Records how long each graphics profile is applied (account-wide). With
your PC's watts at your own settings and per profile entered on the new
Savings tab, /jpm stats and the switch message show the energy saved,
plus cost and CO2 if a price and factor are entered. Nothing is shown
for figures that aren't entered. Deleted profiles count in the totals
but a new profile with the same name starts from zero.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Plan: background FPS limit noted in the help text, not detected
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Plan: deleted profiles' savings; background detection question
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Plan: energy savings per profile (next 0.1.x)
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Plan: M6 Phase 0 progress
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Release: label uploads only with the packaged TOCs' game versions
The packager labels an upload with the game versions of every TOC in the
repo, even one .pkgmeta leaves out. scripts/package-args.sh passes -g with
the packaged TOCs' versions when a TOC is left out (the classic branch,
until 0.2.0 is stable); otherwise nothing, so main and midnight releases are
unchanged. Dry runs: classic -> 1.15.9 only; midnight -> 12.1.5, 1.60.1.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Release: tag guard rules for the 0.3 betas
A 0.3 pre-release must include all of main and midnight, and while 0.2 isn't
stable its .pkgmeta must leave out the Mainline TOC (Classic clients only).
The release workflow fetches every branch for the check. Tested in a scratch
clone: stable, 0.2 and 0.3 cases, missing merges, deleted midnight.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - CI: test the client flavors each branch lists in tests/flavors
Each branch lists the clients it supports, so ci.yml stays the same on
every branch (no merge conflicts) while classic adds its own flavors. The
harness loads the TOC each flavor's client reads. CI also runs on classic.
Tests and CI only; not packaged.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - link.sh: a dev TOC per release TOC; --classic-era
For each JimPowerMizer_.toc it writes JimPowerMizerDev_.toc
(the Classic TOC comes with M6), and removes dev TOCs whose release TOC is
gone. Dev tooling only; not packaged.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Plan: run the 0.2 and 0.3 betas side by side
Each beta line gets its own clients until 0.2.0 is stable: 0.3 packages
leave out the Mainline TOC, so they're labelled for Classic only.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Docs: kept on main only; Classic clients to support
Brings the Midnight progress notes and README from midnight, so main holds
the complete docs from now on. M6: every Classic client Blizzard runs (Era
incl. SoD and Hardcore, TBC Anniversary, Mists Classic).
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Plan: Classic support (M6, 0.3.x)
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - 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 hide-names results
Co-Authored-By: Claude Fable 5.2 noreply@anthropic.com - 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 - 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 - 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 inif 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
v0.1.4
JimPowerMizer
v0.1.4 (2026-11-15)
Full Changelog Previous Releases
- Tests: clamped CVar value reported after the write
Covers the Applier branch that remembers the value the client kept when
CVAR_UPDATE arrives later than the write (the mock used to fire it only
during the write).
Co-Authored-By: Claude Fable 5.2 noreply@anthropic.com - Idle: typing, interface clicks and opening windows count as input
With the mouse option off (the default), chatting or browsing the auction
house while standing still used to trigger Idle. Input now also includes:- typing: a text box gaining the keyboard focus or its text changing (polled;
losing the focus isn't input, since hiding the interface takes it away) - a mouse click on the interface (GLOBAL_MOUSE_DOWN, not over the world, so
panning the camera still follows the mouse option) - opening a service or profession window, or the flight map
The Compat layer reports the last two as the trigger USER_INPUT.
Co-Authored-By: Claude Fable 5.2 noreply@anthropic.com
- typing: a text box gaining the keyboard focus or its text changing (polled;
- Flight path: any input after landing ends it
After landing, the saver used to end only on moving, casting or combat, so
clicking the flight master again, looting or targeting left Max saver on.
It now also ends on any input by Idle's rules (shared input clock), once the
landing has settled for 2 s so the landing's own polled changes don't count.
Co-Authored-By: Claude Fable 5.2 noreply@anthropic.com - Fixes from code review
Applier:- Don't rewrite a CVar already at the wanted value (a preset would reset the
settings under it again). - Remember the value the client keeps when it clamps ours, so it isn't taken
for a change made by the user. - Ignore CVAR_UPDATE for our own write in progress.
- A new switch drops changes still queued from combat.
- Lower-level settings the restore couldn't write in combat are put back once
combat ends; details saved in a period are restored even if the option was
turned off meanwhile.
Idle: - Running that starts in the settle window after a loading screen counts as
input once the window ends. - A loading screen that never reports its end stops being honoured after 5 min.
- Only our own PLAYER_FLAGS_CHANGED counts (engine-wide filter too).
- Combat state is re-read on enable and after a loading screen.
Other: - /jpm force while switched off is refused instead of remembered.
- /jpm probe skips its write test while a profile owns maxFPSBk.
- Switching settings profile applies that profile's on/off switch.
- Fishing pole check caches the last main-hand item.
- OnEnable errors are reported in debug.
Harness session 9 covers these. In-game tests still pending.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
- Don't rewrite a CVar already at the wanted value (a preset would reset the
- Idle across loading screens, Flight path until you move, Long idle
- Idle: a loading screen (e.g. a ship crossing zones) isn't input. Events and
polled changes during one and for 5 s after are ignored, and an AFK flag set
before it still counts if the game drops it while zoning. - Flight path: stays active after landing until you move, cast or enter combat,
so an unattended flight keeps saving until you're back. - Long idle: a second idle situation with its own timeout (default 15 min) and
profile, sharing Idle's input tracking. /jpm longidle ; /jpm
enable/disable take situation names in any case. - Flight path priority 80 -> 91 (between Idle and Long idle), so a long flight
keeps its own profile instead of Idle taking over.
Verified in game.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
- Idle: a loading screen (e.g. a ship crossing zones) isn't input. Events and
- Ignore personal notes folder
notes/ holds a personal in-game test log that isn't published.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
v0.1.3
JimPowerMizer
v0.1.3 (2026-11-14)
Full Changelog Previous Releases
- Fishing and Crafting situations
- Fishing: a fishing pole in the main hand (on Forever you hold the pole). Light saver,
priority 55, 1 s delay. - Crafting: a profession cast (isTradeSkill), then a grace period (default 10 s; option and
/jpm crafting ) ended early by moving or by closing the profession window if it
was open during the craft. The profession window alone doesn't count. Light saver, priority 50. - Both enabled by default. Crafting orders window parked for Midnight (M5).
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
- Fishing: a fishing pole in the main hand (on Forever you hold the pole). Light saver,
v0.1.2
JimPowerMizer
v0.1.2 (2026-11-14)
Full Changelog Previous Releases
- Plan: v0.1.2 features verified in game
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Rename the Cinematic situation to Cutscenes
Avoids confusion with the new Cinematic graphics profile. The saved key stays "cinematic";
commands accept "cutscenes" and /jpm list shows it.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Built-in Cinematic profile: screensaver feel
- Hides the UI, names and nameplates and caps FPS at 30, leaving graphics at your settings.
- BUILTIN_UPDATES entries are now { change = ..., add = ... }; update 3 adds Cinematic to
existing settings unless a profile with that name exists. A deleted Cinematic stays deleted.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
- Graphics profiles: optional hide names and nameplates
- New profile option "Hide names and nameplates" sets the UnitName*/nameplateShow* CVars the
client has to 0 through the Applier, so they're saved, restored and crash-safe like the rest. - Not listed in the profile editor; /jpm probe reports how many exist on the client.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
- New profile option "Hide names and nameplates" sets the UnitName*/nameplateShow* CVars the
- Dimming: use the game's Brightness setting instead of an overlay
- The black overlay conflicted with hiding the UI. Brightness (0-100) is now a normal profile
setting in the registry, saved and restored like the other CVars. - Screen.lua keeps only "Hide the user interface"; leftover dim keys are removed from profiles.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
- The black overlay conflicted with hiding the UI. Brightness (0-100) is now a normal profile
- Max saver: lower Secondary Lighting and PBR Liquid Detail
- Registry: graphicsLightMode (Secondary Lighting, 0-3) and graphicsPBRLiquidDetail (0-2),
names and ranges found in game with /jpm watch. Both 0 in Max saver. - Their lower-level CVars (giQuality, RenderFormat, pbrLiquidDetail) join the known detail list,
so custom values are put back after a switch. - Built-in update 2 adds both to existing Max saver profiles that don't set them yet.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
- Registry: graphicsLightMode (Secondary Lighting, 0-3) and graphicsPBRLiquidDetail (0-2),
- Max saver: particle density Low; /jpm watch to find CVar names
- Built-in Max saver now sets particle density to 0 (Low) instead of 1 (Fair). Existing settings
get it through a one-time update that only changes the value if it's still the old built-in one. - /jpm watch prints every CVAR_UPDATE, to find the CVar names behind graphics menu options
(Secondary Lighting, PBR Liquid Detail) before adding them to the registry.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
- Built-in Max saver now sets particle density to 0 (Low) instead of 1 (Fair). Existing settings
- Graphics profiles: optional hide UI and dim screen
- New per-profile "Screen" options: "Hide the user interface" (like Alt+Z) and "Dim the screen"
(black overlay, 0-90 %, fades in over 1 s). Stored as profile keys hideUI/dim, not CVars. - The UI is never hidden/shown in combat lockdown or during a cinematic; it waits until they end.
Combat switches to your settings just before lockdown, so the UI comes back in time. - Showing the UI yourself (Alt+Z) keeps it shown until the next profile switch.
- Capture current keeps a profile's screen options. Nothing is saved, so a reload clears both.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
- New per-profile "Screen" options: "Hide the user interface" (like Alt+Z) and "Dim the screen"
- Plan: idle-on-transport fix verified on the Deeprun Tram
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Idle: mouse/camera movement and riding transports no longer end idle
- Movement now comes from PLAYER_STARTED/STOPPED_MOVING (your own movement) instead of polled
speed/facing, which also change when a ship or zeppelin carries you. - Cursor movement, facing changes, mouselook and turning only count if the new idle option
"Mouse and camera movement count as activity" is on (default off). - Continuous running keeps you active; a missed STOPPED_MOVING is cleared by the poll.
- Debug line names the input that ended an idle period, e.g. "Idle: input (moving) after 412s".
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
- Movement now comes from PLAYER_STARTED/STOPPED_MOVING (your own movement) instead of polled
- Plan: M3 live slider verified; M3 complete
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Plan: v0.1.1 published to CurseForge and Wago
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
v0.1.1
JimPowerMizer
v0.1.1 (2026-11-14)
Full Changelog Previous Releases
- Release workflow: check the CurseForge token before packaging
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - TOC: Wago project ID aND9V26o
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - TOC: CurseForge project ID 1803739
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Release workflow: CurseForge/Wago tokens, current env names; store listing draft
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Plan: v0.1.0 released
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
v0.1.0
JimPowerMizer
v0.1.0 (2026-11-13)
Full Changelog Previous Releases
- Rename TOC to JimPowerMizer_Mainline.toc
The BigWigs packager recognizes _Mainline (and _Camelot) but not _Forever, so the release
failed with 'Could not find an addon TOC file'. _Mainline is the client family that includes
Forever, and lets a later Midnight version share the TOC via a second Interface value.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Bump checkout action to v5; plan and README for M4
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - M4: level names, localization, CI
- Graded settings (shadows, SSAO, particles, liquid, spell density, compute, depth) get
dropdowns like "3 - High", using the game's localized VIDEO_OPTIONS_* strings. - AceLocale with English text as keys; Locales/enUS.lua generated by scripts/gen-locale.py
(--check mode for CI). User-facing UI, chat and help text localized; debug/probe stay English. - CI workflow: luacheck, locale check, mock-API tests on every push and PR.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
- Graded settings (shadows, SSAO, particles, liquid, spell density, compute, depth) get
- Plan: /console tweak protection verified on Forever
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Detect which lower-level settings preset changes overwrite
Forever files groundEffectDensity under the Default console category, not Graphics, so a
Graphics-only list missed it. Instead of restoring a whole category, detect what each batch
of preset writes actually changed:- Graphics category + known list: checked right after the writes and again 0.5 s later.
- Default category (mixed with unrelated CVars): only counted if changed during our writes.
- Originals come from a snapshot at the start of the saver period (the delayed list is
saved to SavedVariables for crash recovery); unknown originals are left alone. - Harness mirrors Forever (ConsoleGetAllCommands, Default category) and checks that
unrelated Default-category changes aren't reverted.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
- Console list: try ConsoleGetAllCommands too; probe explains why the list is empty
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Keep /console tweaks to lower-level graphics settings
Setting a graphics preset (graphicsGroundClutter, ...) makes the client overwrite the CVars
under it (groundEffectDensity, ...), so restoring the preset lost custom /console values.- Before the first change, snapshot every Graphics-category CVar (C_Console.GetAllCommands
plus a known fallback list), excluding display (gx*), MSAA and preset CVars. - After everything is restored, write back any that differ: at once and again 0.5 s later.
- Snapshot is in SavedVariables, so logout and crash recovery restore them too.
- Option "Keep custom console settings" (default on); /jpm probe reports the watched count.
- Harness simulates immediate and delayed preset cascades.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
- Before the first change, snapshot every Graphics-category CVar (C_Console.GetAllCommands
- Plan: M3 options UI verified in game
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - M3: options UI
- AceConfig options: standalone window (/jpm, minimap addon menu) and a Settings > AddOns page.
- Tabs: General (status, on/off, notifications, background cap, debug, restore), Situations
(enable, profile, priority, delay, idle timeout), Graphics profiles (new from your settings,
rename, copy, delete, capture, per-setting Change + value), Settings profiles (AceDBOptions). - Built-in graphics profiles are seeded once so they can be edited or deleted for good.
- Editing the active profile or the active situation's settings applies at once.
- Addon compartment tooltip with status; left-click options, right-click on/off.
- Harness validates the options table and exercises its handlers.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
- Track Forever's bank interaction type (CharacterBanker); M2 complete
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Handle secret values: idle crashed in combat comparing GetUnitSpeed
- Compat (Mainline) passes every player-state read through issecretvalue, so secrets become
"unknown" instead of erroring. - Idle counts combat as activity and skips the snapshot while in combat.
- Engine rate-limits repeated situation errors in debug output.
- Harness simulates secret values in combat (verified it fails on the old code).
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
- Compat (Mainline) passes every player-state read through issecretvalue, so secrets become
- Service windows: legacy window events as fallback, debug-log interaction types
The bank in Ratchet on Forever didn't trigger the service-window situation. Also listen to
BANKFRAME_OPENED/CLOSED, MAIL_, AUCTION_HOUSE_, MERCHANT_, GUILDBANKFRAME_, mapped to the
same window names as the interaction-manager types so either source can close a window.
Debug mode logs every interaction window with its type name and number.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - M2: idle, combat, cinematic, resting, dead and service-window situations
- Combat and cinematics use your own settings at the highest priorities.
- Idle: AFK flag (after 5 s) or no input for a timeout (default 180 s); input = moving,
casting, cursor movement, turning, or activity events. Ends within 1 s of input. - Resting, dead/ghost and service windows (AH, mail, bank, vendor) default off, Light saver.
- Engine: situations can have OnEvent/OnEnable hooks; profile false = your settings.
- Compat: new player-state queries and a service-window tracker.
- /jpm list, enable/disable , idle .
- Test harness covers the new situations and fails on swallowed situation errors.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
- Plan: CVar writes verified in combat on Forever
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Delay combat probe until lockdown is active
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Add /jpm probe combat: run the probe when the next combat starts
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Record Forever probe results; Max saver also lowers view distance, environment, clutter, compute
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Plan: M1 verified in game
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Cap background FPS with foreground cap; skip enter delay at login
- When a profile caps foreground FPS, cap background FPS no higher (option capBackground),
so alt-tabbing while idle doesn't raise the frame rate. - Situations already active within 5 s of login/reload apply immediately, and leftover
settings from the last session wait for that window, avoiding a restore/re-apply bounce. - Status line says "development build" instead of "vdev".
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
- When a profile caps foreground FPS, cap background FPS no higher (option capBackground),
- M1: core addon, Forever compat layer, applier, engine and flight-path situation
- Applier saves the user's CVars before changing them, restores them on exit/logout,
recovers after a crash, defers secure CVars during combat, and keeps user edits. - Engine picks the highest-priority active situation, with enter delay and poll fallback.
- Taxi situation with built-in Max saver / Light saver profiles.
- /jpm status|on|off|restore|force|probe|debug; addon compartment entry.
- Dev scripts (fetch-libs, link), luacheck config, mock-API test harness.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
- Applier saves the user's CVars before changing them, restores them on exit/logout,
- Add BigWigs packager release workflow
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Add BSD 3-Clause licence and third-party notices; drop LibDataBroker/LibDBIcon
LibDataBroker-1.1 is listed as All Rights Reserved, so it (and LibDBIcon,
which depends on it) is replaced by Blizzard's addon compartment.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com - Initial plan and repo skeleton
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com