> For the complete documentation index, see [llms.txt](https://cesium.gitbook.io/cesium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cesium.gitbook.io/cesium-docs/modules/misc/auto-clicker.md).

# Auto Clicker

Clicks left or right for you, with filters for when it runs.

Clicks left or right for you, with filters for when it runs.

{% hint style="warning" %}
This module needs a key bound before it does anything. Set one in its ClickGUI panel.
{% endhint %}

## What it does

Auto Clicker sends left or right clicks at a rate you set. Filters decide when it runs, for example only while holding the button, only with a weapon in hand, or only in certain situations.

## When to use it

Use it when consistent click speed matters and your hand cannot keep up. Set a randomized rate so the pattern is not perfectly regular.

## Settings

| Setting | What it does          |
| ------- | --------------------- |
| Button  | left, right, or both. |

Also in the panel:

* Keybind
* Clicks per second (range)
* Filters (weapon only, block only, hold to run)

## Video

{% hint style="info" %}
A short clip of this module is on the way.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cesium.gitbook.io/cesium-docs/modules/misc/auto-clicker.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.