Repository navigation
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