08 FAQ

Windows 10 and 11, 64-bit. There is no macOS or Linux build to download today.

No. It installs into your own user folder, so there is no elevation prompt on install and none on update either. The one time to run it elevated is when the game itself is — see the macro runs, but the game ignores its keys.

That is SmartScreen reacting to how new the installer is rather than to anything in it. Choose More info → Run anyway. If you would rather not, wait — the warning fades as more people install the same build.

That depends on the program or the game, and only its own rules can answer it. Polter Click plays nothing for you and knows nothing about the game; it does not touch anyone's memory or files. It presses the keys you told it to press.

Plenty of programs and online games still forbid automated input of any kind, and some ship anti-cheat that looks for it. Read those rules first. Where automation is not allowed, don't use it — that decision, and whatever follows from it, is yours alone. What we are building is a way to make the repetitive parts comfortable, not an edge over anybody.

That it is finished enough to be useful and not finished enough to be quiet about it. Features change between builds, bugs reach you before they reach us, and a build can ask to update itself before it runs again. It also needs our servers: signing in goes through them, so while they are down you cannot sign in, and an installation that is already signed in keeps working only as long as it reaches them at least once a week. When something breaks, Reporting a bug is the fastest route to a fix.

It is free while it is in open beta, and so is the account it needs. After the beta there may be free and paid plans, and what each one includes may differ from what the beta allowed; a beta account hears about that by email before anything changes. The terms say it in full.

Your macros, objects, areas, colours and screenshots live in a local database file in your Windows user profile; screen captures are read in memory to answer a condition and are not uploaded. The app talks to our servers for two things: signing you in, and checking whether a newer version has been published. While you are signed in it also tells us, about every half hour — the server decides how often — that this installation is alive, which plan the account is on and which version it runs; nothing about what it runs. The privacy policy lists every field and who else sees it.

Press its trigger key again, or hit Stop on its row in the list. Because the trigger is a global hotkey, it works while another program has focus — which is the point of setting one. A macro can also stop itself: a Stop macro step in the flow ends the run the moment it is reached.

You can, but you will be fighting it. The presses and clicks it sends are real input, delivered to whatever window has focus — so if you alt-tab to a browser, that is where they land. Stop the macro before you do something else, or run it on a machine you are not using.

Yes, and that is deliberate. Closing the window hides Polter Click to the system tray and leaves the engine running, because a macro has to stay armed while you are in a game or another program. Quit from the tray icon when you actually want it gone.

Two causes, in the order to try them.

1. The game runs as administrator. Windows does not let an ordinary program send input to an elevated one, and many launchers and anti-cheat services run elevated. Quit Polter Click from the tray and start it again with Run as administrator; the presses get through.

2. The game reads the hardware, not Windows. Some games take input straight from the keyboard and mouse drivers and never see what the Windows input API delivers, so nothing sent from software reaches them — elevated or not. For those the answer is a device: an Arduino Nano R4 plugged in over USB is a real keyboard and mouse to the computer, and the app presses through it instead. The firmware ships with the app and installs from the settings; Output walks through it.

Yes — that is what flows are. Add a second flow to a stage and both chains run simultaneously, independently, each with its own waits. They are not threads you have to manage; they are just lanes.

Usually one of four things, in this order:

1. The mask includes background, so the search is looking for the object plus a scene that has changed. 2. The accuracy slider is too strict for something that scales or is drawn over a moving background. 3. The two survey answers are stricter than reality — if the icon does resize, say so. 4. The area is not actually over the object; open the area editor and run its Check to see what it finds.

Areas and mouse coordinates are stored as fractions of the screen, so they follow a resolution change. Objects are the exception: an object is a picture at a particular pixel size, so a large enough change in scale means the template no longer matches, and you will want to recapture it — or tell it, in the survey, that its size can change. The object editor warns you when the screenshot was taken on a screen of another size than the one the app captures now, and so does the import of a macro whose objects were.

It depends almost entirely on how much screen-watching you ask for. A macro with no screen conditions captures nothing at all. When something is watching, the engine only re-searches the parts of the frame that actually changed since the last look, so a still screen is nearly free. Max FPS and Capture resolution are the two dials if you want to spend less.

support@polter-click.com, with the log of that run and the macro attached — Reporting a bug says how to get both.

Yes. Export a macro and you get a single file that carries the objects, areas and colours it uses along with it. On import, the app shows you what is in the bundle first and lets you rename it, or point each piece at something you already have instead of creating a duplicate. Objects, areas and colours export on their own the same way.

One file, polter_data.db, in %APPDATA%\Polter Click. Quit from the tray first — the engine holds the file open while it runs — then copy it somewhere safe. To restore, put it back under the same name with the app closed. The file is encrypted, so a database tool cannot open it; the app on another machine can.

The app checks for a new version by itself, downloads it in the background — the sidebar shows the progress — and asks once whether to restart. Saying yes runs the installer, a banner with a progress bar and nothing to click, and reopens the app. No wizard, no reinstall, and your database is untouched.