Trigger an action when a pixel changes colour
Pixel trigger automation on Windows, including the tolerance settings that decide whether it works
Before you start
- Windows 10 or 11, 64-bit. Administrator rights to install.
- A flat, stable area of the UI to watch. Animated edges and glow effects are the main cause of unreliable pixel triggers.
- Hutsix installed, and a profile you can add a binding to.
Steps
- Capture the point or points. Pick pixels from a solid region of the element you care about — the middle of an icon, not its outline. Watching several points in one trigger means all of them must pass before anything fires.
- Choose Match (
=) or Not-Match (≠) per row. Match fires while the colour is present. Not-Match fires when it is gone — that is the mode for "the loading overlay disappeared" rather than "the warning icon appeared". - Pick a comparison mode and tolerance. Start with RGB at the default
24. The table below explains when the others are worth switching to. - Set a cooldown on the binding. Cooldown is the floor between fires. It is the difference between a trigger that reacts and one that spams the same action every check.
- Save, then test in Action Monitor. Confirm the binding fires when it should, and check the skipped rows — they tell you why it did not.
Comparison modes and how tolerance behaves
| Mode | What it compares | Tolerance means | Use when |
|---|---|---|---|
| RGB (default) | Each channel independently | 0–255 per channel | General colour matching |
| Luma | Brightness only, hue ignored | 0–255 brightness | Only intensity matters |
| Hue | HSV hue angle | 0–180 degrees | Hue stable, brightness varies |
| DeltaE | CIE Lab colour difference | ΔE units — start at 6 | Subtle, perceptually close colours |
In RGB mode each channel must be inside the tolerance independently: a saved red of (200, 50, 50) at tolerance 24 matches anything with R in 176–224, G in 26–74 and B in 26–74. If small shading changes cause misses, raise the tolerance. If the trigger fires on the wrong thing, lower it.
Hue mode falls back to brightness comparison for very desaturated pixels, because hue is unstable near grey. That behaviour is deliberate.
When it misbehaves
| Symptom | Usual cause and fix |
|---|---|
| Fires too often | Tolerance too loose, cooldown too low, or the pixel sits on a moving element. Tighten tolerance first. |
| Misses too often | Tolerance too strict, the point was captured from the wrong spot, or the UI scale or resolution changed since capture. Recapture from a stable area. |
| Inconsistent | The point sits on dynamic visuals. Move it to flat colour. |
| Differs on an HDR display | HDR captures are tone-mapped to sRGB internally, but very bright areas can still read differently. Pick a less extreme pixel. |
FAQ
Should I watch one point or several?
One point is easier to keep working. Several points in one trigger gives you a stronger condition — all must pass — which is how you confirm two UI states at once, at the cost of more things that can drift.
Why does my trigger fire once and then stop?
Check the cooldown and whether the condition is still being satisfied. Action Monitor shows skipped rows and the reason, which usually answers this in one look.
Can it detect text instead of colour?
Yes — that is a separate trigger type. See reading text on screen with an OCR trigger.
Is pixel automation against the rules of the software I am automating?
Possibly. Many applications prohibit automation in their terms, and enforcement can include account restrictions. That responsibility is yours.
Try it
Free 7-day trial, no card required. Build one pixel binding and watch it in Action Monitor before committing to a whole profile.