JimPowerMizer

Automatically lowers graphics settings when you don't need them (idle, AFK, flight paths) to save power, and restores yours the moment you do.
Back to Files

v0.1.5-forever

File nameJimPowerMizer-v0.1.5-forever.zip
Uploader
VampyrByteVampyrByte
Uploaded
Nov 16, 2026
Downloads
4
Size
180.1 KB
Flavors
Forever
File ID
9657067
Type
R
Release
Supported game versions
  • 1.60.1

What's new

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_<suffix>.toc it writes JimPowerMizerDev_<suffix>.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 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