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.2.0-beta2

File nameJimPowerMizer-v0.2.0-beta2.zip
Uploader
VampyrByteVampyrByte
Uploaded
Nov 16, 2026
Downloads
5
Size
180.3 KB
Flavors
RetailForever
File ID
9657074
Type
B
Beta
Supported game versions
  • 12.1.5
  • 1.60.1

What's new

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_<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
  • 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

This mod has no additional files