Repository navigation
Releases
ArmouryDaemon 1.3.2
ArmouryDaemon 1.3.2
The windows stay put, and a slow pack step no longer replays
The dashboard comes to the front when the tray asks for it. A tray click only sent a
focus request, and Windows refuses SetForegroundWindow from a process that was not the
last to receive input, so the window stayed behind whatever you had open. The daemon now
hands the UI's process the foreground right before it sends the request, and the UI raises
itself with a 400 ms always-on-top pulse that it drops again.
Every window keeps its 5 pt frame. The width came from per-row font estimates, which
miss what egui adds around a widget: a combo box with its arrow, or a button with its
padding, could end at the frame's edge and get clipped. The estimate is a floor now. Each
window measures what its laid-out body overflows by and grows by exactly that, held inside
the work area. The first attempt at this is worth recording, because it is what you saw on
30 Oct: counting the frame's own margins as overflow made the dashboard grow ten points a
frame until it covered the screen and Windows drew a title bar on it.
A queued pack pass cannot replay behind a slow one. Wallpaper Engine's
-control stop hung past the ten-second CLI deadline, was killed, and its stop only landed
on the next pass, so the OSD fired twice and the wallpaper changed half a minute late. The
deadline is 20 s, and the pack worker drops a queued full-state job when a newer one
arrives, because the newer state makes the older one obsolete. A tagged job, a disable or a
removal, keeps its turn.
G-Helper stops warning about a switch that worked. The read-back check ran after every
apply, and for a hotkey pack it could only measure G-Helper's own save delay. It now runs
for a pack with a script, where the pack writes the JSON itself. A scripted pack waits 3 s
for the file, which covers G-Helper's measured 2.5 s.
Two helpers nothing called are gone: hotkey::apply and trust::len/source. The
cached/cached_hero/Repeat helpers stay where they are, because the console launcher
uses them from its own binary.
The counts
462 unit tests, none failing, run on the release machine. The daemon is still one
executable with no runtime to install; the console launcher, idle mode and killswitch still
come from the pack catalogue.
The end of this line
1.3.2 is the last release of ArmouryDaemon. The modular work it was built for is done: the
daemon runs resident and elevated, the three packs and the three modules install from the
catalogue, and each one owns its own window, its own switch and, for a mode, its own key.
ArmouryDaemon 1.3.1
ArmouryDaemon 1.3.1
The console launcher, idle mode and killswitch are modules now
They are no longer built into the daemon. Each one is downloaded from the packs
repository like any other module, appears in the Packs window and in the dashboard's
packs list, and has its own window behind the ‹ button:
- Console launcher — a helper module with its own executable: its window holds the
open method (on pad connect / on daemon start / never), its pinned games and the
SteamGridDB key for cover art, plus an on/off box. - Idle mode — a mode pack: a hotkey (
homeby default), the black screens and every
output muted. Any real key press ends it. - Killswitch — a mode pack: a hotkey (
endby default) that hides and mutes every
running tracked app and puts them back when pressed again.
The daemon's hotkey table is now built from the installed, enabled mode packs. Nothing is
bound until the pack that asks for the key is installed, and disabling a pack takes its key
out of the table immediately. A mode's hotkey is recorded in its own window — typed or
captured, one to four keys (a modifier set plus the key) — and the hook is suspended while
recording, so recording Home does not also toggle the mode.
A mode runs on a tracked-app transition only when its manifest says
"triggers": [{"kind": "tracked_app"}]. The hotkey modes declare a hotkey instead, so a
game starting or closing can no longer run their blocks behind your back.
The settings window lost three sections
The global hotkey editor, the console launcher's policy row and the SteamGridDB key all
moved into the modules' own windows. The settings window is timing, daemon, packs and the
logs/config buttons.
Idle mode is an overlay and a mute — nothing else
It no longer reverts the packs when it comes up, re-applies them when it goes away, or
freezes switching while it is on. A tracked app starting or closing behind the black
screens leaves idle exactly as it is; the packs keep switching underneath.
The wake check also no longer mistakes an injected key for the user arriving. The old
GetAsyncKeyState poll could not tell a real keystroke from a SendInput one, and applying
a pack injects its own keys (G-Helper's mode chords), so starting a tracked app dismissed
the overlay. The low-level hook now records real key presses only.
The chain really stands on one line
Placement was computed from the inner size the viewport was asked for; Windows adds a
border, so each window's outer bottom sat a few pixels below the dashboard's — under the
taskbar. Every chain window now measures its own outer rect and is corrected against the
dashboard's bottom edge, so Settings, Packs and every pack window share one baseline.
Smaller fixes
- The packs count included only real packs, so the console helper made six modules read as
five. The console row is listed and counted whether or not its helper is installed. - The dashboard's idle-mode button is gone: idle is toggled by its own hotkey or the pack's
Enabled box, like every other module. - A pack row only draws a dropdown for a setting that has values; a mode's hotkey no longer
renders an empty combo box. - Each module's window says what it does instead of the tracked-app sentence it inherited.
- The CRLF trap: the catalogue's manifests are now written, hashed and signed as LF, the
bytes the CDN serves, so a downloaded pack verifies. - A stale UI test that depended on a removed permission-line argument was dropped.
ArmouryDaemon 1.2.0
Helpers are catalogued now, and installed like packs. A catalogue entry may name a helper
module: an archive plus the executable inside it (entry). The catalogue window is the
Modules window, and packs, modes and helpers render in one list - a helper's state comes
off its own module.json record on disk, not off the daemon's pack folder. Its row carries a
real Download button: clicking it downloads the archive on a worker of its own, verifies it
against the manifest, and hands the daemon an InstallHelper request naming the id, the
version, the executable's path inside the archive, the SHA-256 and the size. The daemon is the
last to read the file: it must sit in temp under the download's name shape, its bytes are
re-checked against the SHA-256 they were named with, and only then is it extracted into
modules/<id>/ - the folder and its parent carry an Administrators + SYSTEM full, user read +
execute lock - the layout recorded in the folder's module.json, and the temp archive removed
whatever the answer is. A helper joins no pack or mode worker; --module-list lists every
installed pack, mode and helper from disk.
The manifest those entries come from is minisign-signed. The fetch reads index.json,
then index.json.minisig, and verifies the signature against a keyring baked into the binary
before parsing anything: an unsigned or badly signed manifest refuses by name, and nothing
is installed or listed. The manifest also reaches schema 2 - entries under modules, an
entry naming its kind - and the daemon still reads a schema-1 manifest's packs key for this
release, so an old manifest keeps loading while one that carries both keys refuses. The packs
repo has not published its signed manifest yet, so the fetch of the live catalogue refuses by
name until that flip; the shipped packs in packs/ and the local probes need no flip.
The killswitch is configurable. One field, killswitch_enabled (default on), is the
switch and the "is the module installed" flag: while it is off the End key and the tray
toggle are logged no-ops and the tray item reads "Killswitch off in config";
{"type":"set_killswitch"} carries the decision over the pipe; the state survives a restart;
and turning the switch off releases an engaged killswitch first - windows back, audio back,
tray icon back. A status from an older daemon still means on. And modes stopped holding the
queue: mode packs get a worker and channel of their own, and a mode whose steps take seconds
no longer delays the apply or the revert of a pack beside it; the running state and the
journal read as they always did, and nothing changes for a pack - kind defaults to "pack",
and a mode still arrives only through the ordinary tracked-app trigger.
The executable carries its own C runtime: the MSVC build links the CRT statically, so it
imports no VCRUNTIME140.dll and starts on a stripped image where the VC redistributable was
never installed.
What else changed
- Quitting releases an engaged killswitch. The quit path used to revert the packs and leave
idle mode while the killswitch rode past both: its hidden windows die with the process, but
its mutes live on the audio devices - the machine could stay hidden and silent until the
daemon started again. The killswitch is released between the revert and the exit now. - A failed download leaves the row offering its button. The failure line the Modules window
paints could extend wider than the list without a width cap, pushing the rows' right-aligned
buttons past the window edge, where they clipped away and came back only at restart. The
line wraps like the notes under the rows now.
The pack format is unchanged, and the three shipped packs are the bytes they were -
Wallpaper Engine 1.4.0, G-Helper 1.3.1 and Rainmeter 1.5.0.
ArmouryDaemon 1.1.6
A pack now says what it is and what starts it. Two optional fields carry it: kind is "pack" or "mode", and triggers says what starts the pack - a tracked_app, or a hotkey with a key. Both are additive: a pack that carries neither is a "pack" started by a tracked app, so the three shipped packs load, apply, revert and remove exactly as they did, and spec stays 1 or 2. A value outside the set is refused by name instead of defaulted - unknown kind 'widget' (expected 'pack' or 'mode') - a mode needs at least one trigger, a hotkey trigger needs a key, and a tracked_app trigger takes none.
The capability gate covers the declarative steps. It covered the script, where only the granted functions are registered on the engine, and not the steps, because a step is data and no engine ever sees it: a pack that declared "capabilities": ["files"], or [], could still run a program (cli), start or kill a process (process_start, process_kill), inject keystrokes (hotkey) and write the registry (registry_set). Every mechanism names its capability now. A step whose capability the pack did not declare is refused when the pack is validated, so the pack never loads, and refused again where the step would run. registry_set gets a capability of its own, registry: a registry write reaches outside the four file roots the sandbox enforces, so it is its own grant rather than part of files-write.
A change of the cooldown no longer brings an expired window back to life. The daemon drains its pipe before the 1 Hz tick that reaps an expired window, so a set_cooldown in that gap gave the dead window the new length: the dashboard ran a countdown for a cooldown that was not running, and the next game launch was held behind it. Only a window that is still running is re-timed; one that has ended is dropped, and the next start changes the machine at once.
What else changed
overlay_showandoverlay_hiderequests are coalesced: one pending request, and a request for the state the daemon is already in is skipped. A script with a thousand pairs used to cost a black window per monitor, a marker file write and delete, and a pack job for each pair.- The refusal message survives being raised inside a pack function. Rhai wraps an error from a script-defined function, so the daemon's match missed it and the pack's log got
Function not foundinstead of the line naming the missing capability. audio_mute_allleaves a crash-recovery record: the devices it muted go intoidle.ledger, the file idle mode already uses, so the next start unmutes them after a crash or a reboot.- A game that starts inside a revert's window wins. The revert is cancelled and the machine stays in Turbo, while the window keeps holding pack changes for the rest of its length.
- A hand-edited
cooldown_secondsis clamped to 5-3600 s at startup, so it cannot panic the daemon.
The pack format stays additive, and the three shipped packs are unchanged.
ArmouryDaemon 1.1.5
The pack script's host API is scoped by capability. A pack declares the capabilities it wants - "capabilities": ["files"] - and the daemon grants only those: the sandbox keeps one engine per capability set and registers only the granted functions on it, so a call to a function of a capability that was not granted fails as an unknown function. The denial is structural rather than a check a call site could forget, it names the missing capability and what the pack asked for, and it lands in the pack's log. The field is additive and defaults to every capability, so the shipped packs keep working unchanged. The host functions also report what they changed: audio_mute names every session of the process and the state it was in before the call, and it never unmutes a session the user had muted themselves.
The catalogue and the cover art are validated against the Windows certificate store. The catalogue fetch used Mozilla's bundled roots, so it failed on any machine with a corporate CA or with TLS interception, and the cover art was left with the same bug in a second place. Both go through one client now, built once, with the platform verifier: they share its root store and its connection pool, and no client is built for a request any more. The Mozilla bundle leaves the binary with it, and the client refuses the bundled roots instead of falling back to them.
A change of the cooldown re-times the window that is running. The window keeps its start and takes the new length, so it ends at start + cooldown, and the change it is holding lands at the new expiry. Before, the setting changed only the length of future windows: the window in flight ended at the old expiry, the change it was holding landed in that gap, and the game that was starting again then sat held inside the new window with the packs off.
What else changed
- The dashboard names the app the cooling-down window belongs to, and says that a change is waiting behind the window while one is.
- The release carries the executable and its hash sidecar, and nothing else. There is no zip and no scripts in it: the executable installs itself, and the scripted install lives in the deploy folder of the repository.
The pack format is unchanged, and the three shipped packs are unchanged.
ArmouryDaemon 1.1.4
The lockout now holds a change in both directions. A tracked app that closes waits for the window, and a tracked app that starts inside a window waits too: the packs stay as they are until the window is over, the change lands exactly once, and it lands only if the app is still running by then. A restart inside the window cancels the held change, so the packs stay applied. A manual action - pausing, removing a tracked app, entering or leaving idle mode - still bypasses the window and happens at once.
The old rule deferred only some changes. A tracked app that closed between two windows reverted the packs at once, and the restart that followed was stuck behind the revert's own window: the machine sat in the quiet mode while the game was running, and the logs showed the revert before the apply.
What else changed
- The release carries the executable and its hash sidecar, and nothing else. There is no zip and no scripts in it: the executable installs itself, and the scripted install lives in the deploy folder of the repository.
The pack format, the catalogue and the shipped packs are unchanged.
ArmouryDaemon 1.1.3
The published executable is built for the x86-64 v3 level: AVX2 and the rest of the third set of instructions. The build is the same on every machine, and it runs on Intel from 2013 (Haswell) and AMD from 2015 (Excavator).
What else changed
- The pack script's sandbox built a new interpreter and registered its host functions on every run. It keeps one engine now: the 432.7 µs the build used to cost is paid once, and a run spends 4.7 µs on the engine.
- The killswitch enumerated the machine's audio sessions once per tracked app. It enumerates them once for the whole press now, and restores from its ledger on release without enumerating at all: about 45 ms off the event loop on each press.
- The daemon walked the process table every tick, even with nothing tracked. The walk is skipped when no applications are tracked: it cost about 19.5 ms a second, and it now happens only when there is something to find.
- The killswitch unmuted an audio session the user had muted themselves. Only the sessions it changed are restored now.
- The console band is centred on the screen again and is allowed to cover the dashboard, because the band is used to launch a game from a controller while the user is away from the computer.
The pack format, the catalogue and the shipped packs are unchanged.
ArmouryDaemon 1.1.2
The Install packs window now opens immediately instead of after a six-second delay, the packs are listed in alphabetical order, and the console band no longer covers the dashboard.
The published executable is built for the CPU it was compiled on and needs AVX2 — Intel from 2013 (Haswell) → AMD from 2015 (Excavator) — so it will not run on older processors.
What else changed
- A pack file with a very large number of dropdowns no longer takes ten minutes to validate.
- A client on the daemon's pipe can no longer make it allocate without limit.
- The daemon looks for its packs folder in the right place.
- A downloaded pack file is deleted once it has been installed.
- The dashboard opens on the first run whatever is installed.
- A JSON error in a pack file names the field that is wrong.
The pack format, the catalogue and the shipped packs are unchanged.
ArmouryDaemon 1.1.1
ArmouryDaemon 1.1.1
The published executable is built for the CPU it was compiled on and needs AVX2 — Intel from 2013 (Haswell), AMD from 2015 (Excavator) — so it will not run on older processors.
The Install packs window had a Local pack button that sat below the bottom of
the window: dead space above the footer pushed it out of view, so a documented
feature could not be clicked. The list now shrinks to its content and the footer
always fits. A long catalogue still scrolls.
The tracked-app picker now says how many matches it did not show, instead of
stopping at eight without a word.
The headline change is in 1.1.0: the executable is now a complete installation
on its own. Run it, and the daemon creates the packs folder, registers its own
scheduled task and opens the dashboard. Settings → Install packs lists the
catalogue and needs no API key.
The pack format, the catalogue and the shipped packs are unchanged.
ArmouryDaemon 1.1.0
ArmouryDaemon 1.1.0
The executable is now an installation on its own.
Download ArmouryDaemon.exe, put it in a folder you can write to, and run it.
Windows asks once for administrator rights. The daemon then creates the packs\
folder next to itself, registers its own scheduled task - at logon and when the
machine resumes from sleep, with the highest privileges - and opens the dashboard
the first time, so you land on it.
Settings → Install packs lists the catalogue. No SteamGridDB key is needed for
that: the key is for the cover art only.
What else changed
- Leaving idle mode while the daemon was paused used to leave the packs reverted
while the dashboard claimed they were applied. The packs are now put back when
you leave idle mode, paused or not. - A pack step that does nothing used to be reported as a success. It is now
reported for what it is. - A refused key injection now names the Windows error behind it, and is retried
once. - The console band no longer opens over a game that is already running.
- The dashboard no longer walks the whole process table on the thread that draws
it.
The pack format, the catalogue and the shipped packs are unchanged.