Reference
docs

Quick start

1. Open the Clicker tab.
2. Choose Rate or Delay and enter the cadence.
3. Select Mouse or Key, followed by the button or key to send.
4. Optionally enable a click or time limit.
5. Press Start or use F5.
6. Press F5 again at any time to stop.

Clicker controls

Cadence

Rate expresses frequency as clicks per second, minute, hour, or day. Delay expresses the interval directly with hours, minutes, seconds, and milliseconds.

Input

Mouse mode supports left, middle, and right buttons. Key mode sends the configured keyboard key. Toggle mode starts and stops with the hotkey; Hold mode runs only while the hotkey remains held.

Behaviour

Duty controls how much of each interval the input remains held. Jitter introduces bounded timing variation. Double Click schedules a paired click when the effective cadence allows it.

Limits

A click limit stops after the configured input count. A time limit stops after the configured duration. Both are native engine stop conditions.

Sequences

A sequence replaces the current-pointer target with an ordered set of screen coordinates. Each point can carry its own click count.

1. Enable Sequence mode from the Clicker panel.
2. Switch the sequence control from Normal to Pick.
3. Right-click a point to select it.
4. Hold Shift while right-clicking to add multiple points.
5. Review the persistent point overlay and edit the list as needed.

Sequence coordinates are screen coordinates. Re-pick points after changing display scaling, monitor arrangement, or the position of the target window.

Safety observers

Safety observers sit beside the normal stop button and hotkey. When one ends a run, the bottom engine-event rail records the reason.

Corners and edges

Each corner and edge has an independent size. Enabling the observer briefly identifies the protected regions on screen.

Custom stop zone

Choose Pick and right-drag a rectangle on screen. Entering that red dashed region triggers the configured stop behaviour.

Task switching

The task-view guard reacts when the active desktop context changes through Alt+Tab or Task View.

Resume behaviour

Observers configured to pause may allow the active run to continue after the unsafe condition clears. Observers configured to stop end the run and require a new start command.

Process rules

Process rules compare the foreground application with an allow or block list:

• Allow mode permits the run only while a listed process is in front.
• Block mode pauses or stops when a listed process comes to the front.
• Rules should use the executable process name shown by the editor.

Foreground observations are evaluated locally and are not sent to a Woodpecker service.

Presets and persistence

A preset captures the complete clicker configuration, including sequence points and safety controls. Woodpecker supports up to twenty named presets.

• Create a new preset before adapting a known configuration to another task.
• Save after making changes you want the preset to retain.
• Delete obsolete presets from Manage.
• The active preset and ordinary settings are retained between launches.

Cookie mode

Cookie mode is a separate connected workspace. Woodpecker starts a small local service and displays the browser injection command in its footer.

1. Open the target browser page and its developer console.
2. Copy the current Inject command from Woodpecker.
3. Paste and run it in the browser console.
4. Wait for the Woodpecker panel to report Connected.
5. Start the bot and inspect Buildings, Saves, and Details as needed.

The smart buyer compares available purchases and continues across low-production recovery periods after ascension. Save and ascension controls remain visible for manual intervention.

The connection uses 127.0.0.1 and does not require a remote Woodpecker bot service.

Engine architecture

Woodpecker deliberately separates presentation from timing:

• GPUI renders the interface, validates configuration, and displays snapshots.
• NASM x64 owns deadlines, waits, press/hold/release cycles, double-click planning, variation, limits, and run state.
• Windows adapts planned input through the native SendInput path.

The interface can redraw without becoming the clock that schedules input.

Steam integration

The Steam edition verifies ownership and launch state through Steam. Steam Cloud synchronizes woodpecker-cloud-v1.json, while Steam Stats records aggregate runs, inputs, and engine time for achievements.

For sync problems or diagnostics guidance, continue to Woodpecker Support.