Releases

Fixed

• Publishing a Bundle with many images no longer stops partway through the upload.

Changed

• When Screeker and the target application are at different privilege levels, a Routine can restart Screeker to match, leave it, or ask. The dialog has a “Remember this choice” check: Yes with it checked always restarts next time, and No with it checked never restarts. Settings → Application lists the same three choices under “When the privilege level is different”. A saved “Don't ask anymore” is kept as Never restart.

Fixed

• Creating a diagnostics report no longer quits Screeker while checking whether the Windows account is in the Administrators group.

Added

• Screeker keeps a detailed log on this computer (logs/screeker.log, five files of 5 MB). Settings still choose how much of a Routine the activity panel shows.
• Settings → Application can create a diagnostics report. You can preview it, copy it, or save a zip. A screenshot of the target window stays off until you tick it. The picture in the preview is reduced; the zip keeps the full screenshot. The copied text includes the last 300 log lines; the zip keeps the log files. The same entry is on the privilege restart prompts and on capture, click, missing-window, and elevation errors. Screeker does not upload the report; you send it yourself.
• A Go crash is recorded in logs/crash.log when the runtime can write one.
• When Screeker and the target window are not at the same privilege level, the activity log includes the facts Windows reported (process, elevation type, integrity, session, UAC).
• The window opens again at the size and place you left it. Maximised and full screen are not restored; the next launch uses the size and place from before that. If that spot is no longer on a connected display, the window moves so it sits fully on the nearest one.
• Starting a Routine now counts down 3, 2, 1 on the button you clicked, so you have time to switch to the game. The same number shows in the red Stop button in the title bar. Click either one to cancel. Settings → Execution sets the countdown from 1 to 60 seconds, or turns it off to start Routines at once as before.
• Publishing a Bundle asks which Routines and Playbooks to upload. A Playbook can be included only when every Routine it uses is included. The choice is remembered on this computer and offered again next time. A Routine or Playbook added since the last publish starts unticked. The first publish still starts with every valid Routine and every Playbook that can go with them.
• Routines can declare variables: values the Routine changes while it runs. A transition can set them after its action, and conditions, image paths, and typed text can read them as {{v:name}}. Each run starts every variable at its starting value. Open them from the new Variables button next to Params; the Transition dialog gains a Set variables section, and an arrow that sets variables shows a small badge listing the changes.
• Playbooks can declare variables too. Each step can have a condition that skips it when false and can set variables when it starts. These are saved and checked today; running Playbooks does not use them yet.
• A number variable can be set with math: {{v:count}} + 1 or {{p:width}} * 2, with + - * / % ^ and parentheses. Choose Expression in a Set variables row of a Routine transition or a Playbook step. Dividing by a constant zero is caught while you edit; if a variable turns the divisor into zero, the Routine run stops with an error.
• Your Store listings are no longer on the Bundles page. On the Store page, My Bundles replaces the catalog with the Bundles you published. Each one shows its status and version date, and you can install it or remove it from the Store there.
• A local Bundle shows whether the copy on this computer is the version in the Bundles Store (Published, Under review, Rejected) or Not published. Changing a Routine, a Playbook, an image, or the Bundle's details makes it Not published until the next publish; saving without a change does not. A Bundle published before this release shows Not published until it is published once more. The Bundle page uses the same rule. On a Bundle card the status and the version's date and time sit under the name. On the Bundle page they sit next to the author or the Pinned mark.
• Routines can ask for values before they run. An author declares Params in the Routine editor — a label, a type (yes/no, text, whole number, decimal), an optional default, an optional list of options, an optional image, and an optional group — and refers to them as {{p:name}} in anchors, when images, template clicks, and typed text (schema 0.3.0). Existing 0.1.0 and 0.2.0 Routines still run untouched.
• Start on a Routine with Params opens a form first. Grouped params show as a bordered box titled with the group name, and a group of yes/no params that all carry an image becomes a grid of pictures you can toggle independently. Options for text and number params can each carry a name and an image. The image is picked, uploaded, or captured and cropped from the game window in the editor. When every option has an image, the form shows the pictures and you pick one; otherwise you pick from a list. Either way you see the option's name, or its value when it has no name, and the Routine gets the value. An option image must be a PNG, JPEG, or WebP file in the Bundle, like any image the Routine looks for, or the Routine cannot run or be published. Remember is ticked by default, so the answers are kept on this computer and the next Start runs without asking. Untick it and that choice is kept: the box stays off the next time you open Params, and every Start asks until you tick it again. The 3-dots menu on the card closes and opens the form to change the answers. Playing from the editor asks every time and stores nothing, since the Routine may not be saved yet.
• A transition can carry a condition, so one Routine covers several choices: if: "{{p:tier}} == 't5' and {{p:count}} > 1000". An edge whose condition is false is skipped as though it were not written, and the arrow chip shows the condition.
• An image path can be built from a param (troops/{{p:tier}}/icon.png). Type the path by hand where a picker cannot help; publish uploads every file the options can name.
• Each state in a Routine has a name. The diagram, outgoing arrows, and the Activity Log show that name; the state dialog asks for it and no longer asks for an id. New states are named State, State 2, and so on. Opening an older Routine fills a missing name from its id and leaves the file unchanged until you save. Routines on schema 0.1.0, 0.2.0, and 0.3.0 still run.
• Outgoing transitions in the state dialog start with an arrow, and the summary sits in parentheses. Hovering when:visible, when:absent, or click shows the images for that word. A percent click and a path built from a param do not.

Changed

• While Screeker is signing you in, Sign In keeps its label and a highlight moves across the button. Email, password, and location stay locked until the attempt finishes. Forgot password, Register, and the language choice stay available.
• Get Pro opens the Portal subscription page.
• Pasting states in the Routine diagram puts the group under the pointer, or in the middle of the visible diagram when the pointer is elsewhere. The paste may overlap other states.
• A Bundle card in the Bundles Store has Install. After the Bundle is on this computer, that button is Open and opens the Bundle on Routines. The Bundle page stays where it is, and Install there becomes Open. Installing still pins the Bundle; you can unpin it later. Updating a Bundle does not change whether it is pinned.
• On a Bundle page the description starts at about 70px, then blurs, with a down arrow that expands it and an up arrow that collapses it. Pin, Edit, Publish, and Delete are in the menu at the top right. The page opens on Routines; Playbooks is the other tab. On a local Bundle, a dashed card at the end of the Routines list says Create a new Routine. The Playbooks list ends with the same kind of card, Create a new Playbook, whether the Bundle is local or from the Bundles Store. Each card shows that item's icon above the words.

Fixed

• A template score is compared after rounding to two decimal places, the same way the Activity Log prints it. A score that shows as 0.90 now clears a threshold of 0.9. A miss prints the threshold next to the score.
• Opening a Bundle no longer flashes its Routines as Invalid. The previous Bundle's list is dropped when you leave — from the Routine editor, or when you switch pinned Bundles — and the page stays blank until this Bundle's Routines and Playbooks have loaded.
• A Playbook stays in the Bundle where it was created, and it is still there after Screeker restarts.
• Starting a Routine keeps the window up. The list refresh after Start no longer reads a settings field Routines do not have, which had cleared the whole window down to the frame.
• When a Bundle cannot be installed or updated, Screeker says why: the signature does not match this copy, the download is damaged, the Bundle is no longer in the Bundles Store, or the download failed.
• The language list in Settings → Interface now shows the language you chose. It used to sit one choice behind: picking Russian switched the interface but left the list on English, and the next pick looked like it did nothing. Choosing a language that cannot be saved no longer moves the list either.
• Playing a Routine from the editor highlights the transition that actually fired. When a state had several arrows leaving it, the green arrow could point at the wrong one.
• Playing a Routine from the editor keeps the green highlight on the transition that ran when a condition skips an earlier one between the same states. It used to highlight the skipped transition.

Added

• Routines can show a cover on the Routines list card. In Routine details, pick a PNG, JPEG, or WebP from the Bundle's assets (icon on schema 0.2.0). Existing 0.1.0 Routines still run. A missing or unreadable file keeps the Routine valid and shows a placeholder; publish uploads the cover when that file exists.
• Settings → Interface can list Routines by usage or by name.
• Routines can click a percent of the bound window (click: [50, 50], or click: { at: [50, 50], button: right }) instead of only a template. The diagram editor has X%/Y% fields for that form.
• When several windows match a Bundle's title, Screeker can ask which one to drive (window.when-multiple: ask, the default) or bind the first on-screen match (pick-first). The choice is remembered until you quit, unlink, the window closes, or you change the title or mode. A chip next to Logs on the Bundle page and in the Routine editor shows the live window name; click an unlinked chip to pick, click a linked one to flash a green border, and X unlinks (not while a Routine is running). Esc or Cancel leaves the chip unlinked and writes a warning to the Activity Log.
• When a new Screeker build is downloaded, a bottom banner offers Install and restart on any signed-in screen. Later hides that banner for this version; you still install from Settings → About when you want.
• Ctrl/Cmd+C and Ctrl/Cmd+V copy and paste selected states in the Routine diagram. Arrows between those states, and arrows to complete and anchoring, come along. Paste sits to the right of the graph, never becomes the initial state, undoes as one step, and works across Routines.
• Invalid Routines stay on the Bundle Routines tab. A Store install shows a red card with an info tooltip and no Start, Edit, or Remove. A local Bundle keeps Edit and Remove. Publish skips those files, warns on the confirm dialog, and refuses if none remain or a Playbook still names a skipped Routine.
• The Routine editor diagnoses on a debounce: Save and Play stay off while there are issues, a selectable banner lists them, and matching diagram pieces go red — including unknown keys on a Routine or transition config.
• The Routine editor warns (Stay / Leave) before Back, the left rail, sign-out, or quitting if there are unsaved changes, including a never-saved New Routine, layout moves, and unapplied dialog drafts.
• Ctrl/Cmd+S saves in the Routine editor. A green Saved line confirms a write. A dot after the title marks unsaved work.
• The Routine editor has the same logs icon as a Bundle page. Play traces go into the shared Activity Log. The panel starts closed and does not follow the Bundle page. A red unread-error dot still appears only when no log panel is visible.
• Clicks can be offset from the matched image by integer pixels (click.shift). If the point lands outside the window, the Routine either clicks the nearest in-window pixel (outside-behavior: click) or retries the poll (outside-behavior: error).
• On Windows, the Routine image picker can capture the Bundle window, crop a rectangle, and save it as a PNG template. The crop overlay zooms toward the cursor (wheel or +/−, from fit up to 16×), pans with Space or the middle mouse, resets with Fit, and resizes an existing rectangle from its four edges. Recapture and more than one crop from the same grab stay on that screen. Exclusive fullscreen and covered windows can still yield a blank grab, as they do when a Routine runs.

Changed

• Routines in a Bundle are listed by how often they were started from the Routines grid, then by id — or A–Z by the name on the card. Choose the order in Settings → Interface (usage is the default). Counts stay on this computer and survive a restart.
• Status sits at the top-right of a Routine card. Delete, Edit, and Start stay at the bottom-right, lined up with the cover unless the description is long enough to push them down.
• Bundles that omit window.when-multiple now ask which window to use when several titles match, instead of silently taking the first.
• Save in the Routine editor writes and stays on the page. A New Routine keeps its allocated id after the first Save so later Saves update the same file.
• The Routine diagram snaps nodes to 10px. The dotted background is a 20px tile that pans and scales with the graph.

Fixed

• Playing a Routine from the grid updates the list order immediately when sorting by usage.
• Shift-drag on the Routine diagram no longer lights up every state for a moment.
• A long-running Routine no longer grows process memory on every template match.
• An after transition waits for its duration instead of counting as a failed poll. A pause longer than a few polls no longer jumps to anchoring (or fails) early.

Added

• Routines can show a cover on the Routines list card. In Routine details, pick a PNG, JPEG, or WebP from the Bundle's assets (icon on schema 0.2.0). Existing 0.1.0 Routines still run. A missing or unreadable file keeps the Routine valid and shows a placeholder; publish uploads the cover when that file exists.
• Settings → Interface can list Routines by usage or by name.

Changed

• Routines in a Bundle are listed by how often they were started from the Routines grid, then by id — or A–Z by the name on the card. Choose the order in Settings → Interface (usage is the default). Counts stay on this computer and survive a restart.
• Status sits at the top-right of a Routine card. Delete, Edit, and Start stay at the bottom-right, lined up with the cover unless the description is long enough to push them down.

Added

• Routines can click a percent of the bound window (click: [50, 50], or click: { at: [50, 50], button: right }) instead of only a template. The diagram editor has X%/Y% fields for that form.

Added

• Store Bundles on Pro (or an operator account) are checked for newer catalog snapshots when you sign in, then about every hour. Auto-update Bundles is on by default in Settings → Bundles; turn it off to install with Update on the Installed card and the Bundle page. Local Bundles are not updated this way.
• The logs icon on a Bundle page shows a red dot when an error is written to the log while the panel is closed. Opening the panel clears it.

Changed

• Auto-update now downloads a new build when Screeker starts, then again after a few hours at a time that is not shared with other Clients. Install still waits for you.
• Checking, downloading, and installing are separate in Settings: Check looks for a new version, Update downloads it even when auto-update is off, and Install and restart applies it.
• The header shows a Pro badge when you are on Pro, and nothing otherwise. The Beta chip is gone.
• The Bundles page hides empty sections. When none have items, Pro sees Download from Store and everyone else sees Create.
• After sign-in, Screeker opens Bundles when this computer already has any, otherwise the Bundles Store.
• Transition summaries on the Routine diagram (immediate, when, click, …) show when you hover an arrow, and stay visible while that arrow is selected.
• The Routine editor image picker reloads folders and files from disk every time it opens.

Fixed

• Checking for updates no longer dead-ends when auto-update is off.
• Log lines and Routine YAML validation errors can be selected and copied.
• The Routine diagram opens when an input transition types an unquoted number, such as text: 2200.

Added

• When several windows match a Bundle's title, Screeker can ask which one to drive (window.when-multiple: ask, the default) or bind the first on-screen match (pick-first). The choice is remembered until you quit, unlink, the window closes, or you change the title or mode. A chip next to Logs on the Bundle page and in the Routine editor shows the live window name; click an unlinked chip to pick, click a linked one to flash a green border, and X unlinks (not while a Routine is running). Esc or Cancel leaves the chip unlinked and writes a warning to the Activity Log.

Changed

• Bundles that omit window.when-multiple now ask which window to use when several titles match, instead of silently taking the first.

Added

• When a new Screeker build is downloaded, a bottom banner offers Install and restart on any signed-in screen. Later hides that banner for this version; you still install from Settings → About when you want.

Added

• Ctrl/Cmd+C and Ctrl/Cmd+V copy and paste selected states in the Routine diagram. Arrows between those states, and arrows to complete and anchoring, come along. Paste sits to the right of the graph, never becomes the initial state, undoes as one step, and works across Routines.
• Invalid Routines stay on the Bundle Routines tab. A Store install shows a red card with an info tooltip and no Start, Edit, or Remove. A local Bundle keeps Edit and Remove. Publish skips those files, warns on the confirm dialog, and refuses if none remain or a Playbook still names a skipped Routine.
• The Routine editor diagnoses on a debounce: Save and Play stay off while there are issues, a selectable banner lists them, and matching diagram pieces go red — including unknown keys on a Routine or transition config.
• The Routine editor warns (Stay / Leave) before Back, the left rail, sign-out, or quitting if there are unsaved changes, including a never-saved New Routine, layout moves, and unapplied dialog drafts.
• Ctrl/Cmd+S saves in the Routine editor. A green Saved line confirms a write. A dot after the title marks unsaved work.
• The Routine editor has the same logs icon as a Bundle page. Play traces go into the shared Activity Log. The panel starts closed and does not follow the Bundle page. A red unread-error dot still appears only when no log panel is visible.
• Clicks can be offset from the matched image by integer pixels (click.shift). If the point lands outside the window, the Routine either clicks the nearest in-window pixel (outside-behavior: click) or retries the poll (outside-behavior: error).
• On Windows, the Routine image picker can capture the Bundle window, crop a rectangle, and save it as a PNG template. The crop overlay zooms toward the cursor (wheel or +/−, from fit up to 16×), pans with Space or the middle mouse, resets with Fit, and resizes an existing rectangle from its four edges. Recapture and more than one crop from the same grab stay on that screen. Exclusive fullscreen and covered windows can still yield a blank grab, as they do when a Routine runs.

Changed

• Save in the Routine editor writes and stays on the page. A New Routine keeps its allocated id after the first Save so later Saves update the same file.
• The Routine diagram snaps nodes to 10px. The dotted background is a 20px tile that pans and scales with the graph.

Fixed

• Shift-drag on the Routine diagram no longer lights up every state for a moment.
• A long-running Routine no longer grows process memory on every template match.
• An after transition waits for its duration instead of counting as a failed poll. A pause longer than a few polls no longer jumps to anchoring (or fails) early.

Added

• Store Bundles on Pro (or an operator account) are checked for newer catalog snapshots when you sign in, then about every hour. Auto-update Bundles is on by default in Settings → Bundles; turn it off to install with Update on the Installed card and the Bundle page. Local Bundles are not updated this way.

Added

• The logs icon on a Bundle page shows a red dot when an error is written to the log while the panel is closed. Opening the panel clears it.

Changed

• Auto-update now downloads a new build when Screeker starts, then again after a few hours at a time that is not shared with other Clients. Install still waits for you.
• Checking, downloading, and installing are separate in Settings: Check looks for a new version, Update downloads it even when auto-update is off, and Install and restart applies it.
• The header shows a Pro badge when you are on Pro, and nothing otherwise. The Beta chip is gone.
• The Bundles page hides empty sections. When none have items, Pro sees Download from Store and everyone else sees Create.
• After sign-in, Screeker opens Bundles when this computer already has any, otherwise the Bundles Store.
• Transition summaries on the Routine diagram (immediate, when, click, …) show when you hover an arrow, and stay visible while that arrow is selected.
• The Routine editor image picker reloads folders and files from disk every time it opens.

Fixed

• Checking for updates no longer dead-ends when auto-update is off.
• Log lines and Routine YAML validation errors can be selected and copied.
• The Routine diagram opens when an input transition types an unquoted number, such as text: 2200.

0.6.0 did not ship. This build is the first with the Routine diagram editor.

Added

• Routines can be authored on a diagram: states as nodes, transitions as arrows, with a toggle back to YAML. Saving an unedited diagram keeps comments and formatting in the original YAML.
• Play in the Routine editor runs the unsaved YAML and highlights the current state and last transition on the diagram. That run is not written to disk. The diagram is frozen while it runs.
• Ctrl+Z and Ctrl+Y undo and redo diagram and dialog edits in the Routine editor. Typing in YAML still uses the usual text undo. Switching between Diagram and YAML clears that history.

Changed

• Transition arrows can attach to any side of a state. Either end can be dragged to another connection point.
• Image fields in state and transition settings show the current selection and open a picker, instead of a large grid inside the dialog. The picker browses folders, uploads into the folder you are viewing, and can create or delete folders (and everything inside them). YAML still lists nested paths and uploads to the assets root. The diagram no longer has an assets column.
• The dotted background on the Routine diagram uses a 20px tile, moves when you pan, and does not change size when you zoom.
• Nodes on the Routine diagram snap to a 9px grid.
• A selected transition is purple.
• complete and anchoring on the Routine diagram are gray with no border until selected.
• Node positions and arrow attachments on the Routine diagram are remembered on this machine. They are not uploaded with the Bundle.

Fixed

• Panning and zooming the Routine diagram on Windows stay in step with the pointer.
• The Shift-drag box on the Routine diagram disappears when you release the mouse.
• Transition arrows meet connection points straight-on and turn a little farther from the node, so the last stretch is easier to follow.
• Several self-loop transitions on the same connection points are drawn as nested loops instead of stacking on one path.
• Selecting a transition brings it to the front; dragging either end then moves that arrow even when several share a connection point.

Removed

• The Routine editor no longer has a Delete button. Delete a Routine from the Bundle Routines tab.
• The Routine editor no longer has a Validate button. Save still checks the Routine before writing.

Added

• When a Routine finds the game running as administrator and Screeker is not, Screeker asks whether to restart elevated so capture and clicks can work. You can decline, or choose not to be asked again; the prompt can be turned back on in Settings.

Added

• A build for ARM64 Windows. Every release now offers an installer for each architecture, so Screeker installs on ARM64 machines and inside Windows ARM virtual machines instead of refusing with "can't be installed on the current Windows architecture".

Fixed

• Updates now follow the architecture the installed build was made for, so an ARM64 install is offered ARM64 builds rather than ones it cannot run.

Added

• Release channel picker in Settings, so a Client can opt into beta builds.
• Automatic application updates: the Client checks a signed update feed, and installs the new build in the background when auto-update is on.
• The About section in Settings now shows the version this build was made from instead of a fixed string.

Changed

• Screeker installs for the current user under %LOCALAPPDATA%\Programs rather than into Program Files. An existing installation has to be reinstalled once by hand; after that, updates apply without an administrator prompt.