Capture and action settings

Setup

Show Image Detection in the sidebar through Manage plugins, then open it.

  1. Choose the Monitor containing your game. If the desktop uses a system screen-sharing picker, use Choose screen instead.
  2. On Windows, leave Backend on Auto (recommended) to start. The UI also offers Windows Graphics Capture and Legacy GDI; GDI may produce black frames in hardware-accelerated games.
  3. Click + New Module, give it a name, then open Configure. A module groups the targets for a game or screen layout.
  4. Add an image template, health bar, or text/number target. Configure its region and use Test now before starting continuous detection.
  5. Enable the target and click Start Detection on the plugin page. Use Stop Detection when you want capture to stop.

Delay is the time between captures in milliseconds. Lower values react sooner but do more capture work. Process every Nth frame lets an individual target run less often. Settings in the target editor save as you change them.

Direct actions

Each target has Action Settings. Select Shockers, Target mode, Action type, Intensity, and Duration (seconds). Selected uses the selected targets; Random from Selected chooses a random subset within Random count.

Direct actions can run alongside flow triggers. Leave Shockers empty when a flow should handle the device command itself. The target still needs to be enabled and detection running. See Image Detection flow nodes.

Meter targets offer an Intensity mode. The health-bar guide explains its scaling. Text targets have their own number-delta scaling controls.

Cooldowns

Under Cooldown, configure Duration (seconds) and Type:

  • Standard waits for the cooldown to expire before another activation.
  • Reset on Detection extends the cooldown when the target is detected again.
  • Wait for Reset Image uses another target as its reset condition. Select that target under Reset trigger target; add another target to the module first if the list is empty.

Meter and OCR targets also have Event Cooldown (ms) controls in their detection settings. Check both settings when changes are detected but actions seem less frequent.

Modules and startup

Use the dashboard's Import and module export controls to transfer modules. After importing, review the monitor, region, resolution, and selected shockers. Under Manage plugins, the Image Detection configuration also offers Auto-start background detection and the region-picker hotkey.

Names in filters

Flow filters match these values without case sensitivity:

  • Module ID: the module name in lowercase, with spaces and underscores changed to hyphens. Boss Fight becomes boss-fight.
  • Image: the uploaded filename, such as boss-icon.png, or its name without the extension.
  • Target: a meter or OCR target's name or ID.

Troubleshooting

  • If capture is blank, confirm the monitor or shared screen and, on Windows, the capture backend. Check any display-scaling warning shown on the dashboard.
  • If a target never fires, use Test now, inspect its region and enabled state, and check focus restrictions before lowering detection thresholds.
  • If a flow fires but no direct action runs, confirm the target's shocker selection. If actions repeat, review cooldowns and whether both a flow and direct action are handling the same event.

Contributors

Thank you to everyone who has helped improve this documentation.

bwmpbwmp