The Lamplighter

HouseholdWorks on its own, within what you allow

Never left on a black screen by a bad graphics driver.

Keeps the last good graphics drivers, asks after a new one whether to keep it, and puts the last good one back when nobody answers or the screen looks dark.

The lamplighter walked the lanes at dusk and lit again any lamp that had gone out.

Try it free7 days, no card See the pricesIn Household and Workshop

What's new

Every release

0.4.1

After an update, one button brings the guard up to date: no command to run.

What's new

Update the guard. The guard runs as SYSTEM from its own copy, so after the Lamplighter updates it goes on running the version before. The page now notices (it compares the guard's scripts with this release's when it starts and each time it looks) and shows The guard needs updating to this version, with an Update the guard button. Windows asks for an administrator once; each script is checked against the release's checksums before it is copied, and the drivers the guard keeps stay. Until then the old guard keeps watching.
The same notice is offered to Manor and the other agents as something that needs you (needsYou in the Lamplighter's state and ping).

What changed

Nothing the Lamplighter shows asks you to type a command any more: the page's hint about a dry run is gone, the guard's scheduled task and its messages name the page's buttons, and a graphics card the guard had to turn off is turned back on in Device Manager, or by turning the guard off on the page.
The guard never takes new scripts from the Lamplighter's own folder by itself: updating it always goes through the administrator prompt you approve.

Before you update

If the guard is on, the page shows Update the guard after this update; press it when it suits you (Windows asks for an administrator once). Until then the guard you have keeps working as before.