Support

One person makes this extension, and one person answers this address. Write to [email protected] and you will get a reply from the person who wrote the code — usually within two working days.

What to include

Most problems are solved in the first reply when the message contains these:

• what you expected to happen, and what happened instead;
• the address of the page you were clicking on (or say "a page I cannot share" if it is private — that is fine);
• which engine is selected, Precise or Light (the setting is at the top of the panel);
• your Chrome version, from chrome://version.

Screenshots help. A screenshot of the settings panel alone answers half the questions I would otherwise have to ask.

Licence keys and billing

Situation	What to do
You paid and no key arrived	Check the spam folder for mail from [email protected], then write to the address above with the email you paid with. Keys are issued by the payment provider the moment the payment clears.
The key is rejected	Paste it whole, including the PAC- prefix if it has one. If it still fails, say which key you used and I will check what the licence server has recorded against it.
You want your money back	Ask within 14 days and you get one — see Terms and Refunds. You only have to say what did not work; no further justification is asked for.
You moved to another computer	A licence is checked on your machine, so it keeps working elsewhere as long as you enter the same key. Write in if a check has stopped working.

Things that are not bugs

These come up often enough to be worth answering here.

"Chrome is being controlled by automated test software"

That banner is Chrome's own, and it cannot be hidden or suppressed by any extension while clicking is running. It appears because the Precise engine drives Chrome's own input pipeline, which is exactly what makes the clicks count as real clicks. It goes away the moment you stop, and the Light engine never shows it.

The click rate is lower than the number I set

Chrome cannot deliver mouse input faster than roughly 4 ms per event, and each click is a round trip. A setting of 20 per second measures around 16 per second in practice. The panel shows the rate actually being achieved rather than the rate requested, so the number you see is the real one.

Nothing happens inside an embedded frame

Only the page you are on is clicked, not the iframes inside it. That is deliberate: it keeps what the extension is allowed to reach much smaller. Not all sites can work without it, and if you hit one of those, say so.

It stopped clicking after I switched tabs

A run is tied to the tab it was started on, and moving away from that tab stops it rather than clicking blind on whatever loads next. Start it again when you return.

Reporting a security problem

If you think you have found a way to bypass the licence check, or anything else that affects other people's data, write to the address above and say so in the subject line. Please do not post it publicly first — there will be a fix.

Feature requests

They are welcome and they get read. Say what you are trying to accomplish rather than only which button you want; the button is often not the thing that is missing.

Contact

[email protected]

See also: what the extension does · Privacy Policy · Terms and Refunds